On 04/17/2016 06:17 PM, Thomas D. wrote: > Hi, > > Sasha, can you please revert commit > f857638dd72680e2a8faafef7eebb4534cb39fd1 like Greg did with linux-3.10.101 > >> commit 1f2493fcd87bd810c608aa7976388157852eadb2 >> Author: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> >> Date: Sat Mar 12 21:30:16 2016 -0800 >> >> Revert: "crypto: af_alg - Disallow bind/setkey/... after accept(2)" >> >> This reverts commit 5a707f0972e1c9d8a4a921ddae79d0f9dc36a341 which is >> commit c840ac6af3f8713a71b4d2363419145760bd6044 upstream. >> >> It's been widely reported that this patch breaks existing userspace >> applications when backported to the stable kernel releases. As no fix >> seems to be forthcoming, just revert it to let systems work again. > > and linux-3.14.65 > >> commit c4eb62da6f34bfa9bbcbd005210a90fdfca7e367 >> Author: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> >> Date: Sat Mar 12 21:30:16 2016 -0800 >> >> Revert: "crypto: af_alg - Disallow bind/setkey/... after accept(2)" >> >> This reverts commit 06b4194533ff92ed5888840e3a6beaf29a8fe5d4 which is >> commit c840ac6af3f8713a71b4d2363419145760bd6044 upstream. >> >> It's been widely reported that this patch breaks existing userspace >> applications when backported to the stable kernel releases. As no fix >> seems to be forthcoming, just revert it to let systems work again. > > > Linux-3.18.x is the only LTS kernel left with this problem. If nobody > cares we should at least revert back to a working kernel... So I mixed stuff up here, I've received a backport that would fix this problem on 4.1, and applied it. However, I forgot about 3.18. Would Milan's backport work on 3.18 as well (https://www.mail-archive.com/linux-crypto@xxxxxxxxxxxxxxx/msg17949.html)? Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
