On 02/23/2016 04:02 PM, Milan Broz wrote: > On 02/21/2016 05:40 PM, Milan Broz wrote: >> > On 02/20/2016 03:33 PM, Thomas D. wrote: >>> >> Hi, >>> >> >>> >> FYI: v3.10.97, v3.14.61 and 3.18.27 are also affected. >>> >> >>> >> v4.3.6 works. Looks like the patch set is only compatible with >=linux-4.3. >>> >> >>> >> v3.12.54 works because it doesn't contain the patch in question. >> > >> > Hi, >> > >> > indeed, because whoever backported this patchset skipped two patches >> > from series (because of skcipher interface file was introduced later). > Ping? > > I always thought that breaking userspace is not the way mainline kernel > operates and here we break even stable tree... > > Anyone planning to release new kernel version with properly backported patches? > There is already a lot of downstream distro bugs reported. Hi Milan, I'd really like to see an ack on your patch by one of the crypto/ maintainers before putting it into a -stable release. Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html