On 02/24/2016 06:12 PM, Greg KH wrote: > On Wed, Feb 24, 2016 at 09:54:48AM +0100, Milan Broz wrote: >> On 02/24/2016 09:32 AM, Jiri Slaby wrote: >>>> + af_alg_release_parent(sk); >>> >>> and this occurs to me like a double release? >> >> yes, my copy&paste mistake. > > Which is why I want the real patches backported please. Whenever we do > a "just this smaller patch" for a stable kernel, it is ALWAYS wrong.
I think that it was clear that I do not want you to directly include this patch, just it points to the direction where is the problem. Anyway, seems the problem is only in 4.1.18. > Please backport the patches in a correct way so that we can apply > them... Not sure if it is still needed, but I'll reply to this thread with my git version of backported patches for 4.1.18. (Resp. only the first need changes, other then applied cleanly from upstream). Thanks, Milan -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
