On 12 Mar 2016 at 19:02:46, Greg KH arranged the bits on my disk to say: > On Sat, Mar 12, 2016 at 05:10:53PM -0800, J. Paul Reed wrote: > > > > On 12 Mar 2016 at 16:45:10, Greg KH arranged the bits on my disk to say: > > > > > So, what patch should I revert from 3.10.y and 3.14.y to "fix" this? I > > > thought only 4.1.y was affected. Or better yet, I asked for backports to > > > resolve this, if someone could come up with them, that would be even > > > better. > > > > The following message in that thread has assumed-bad commit (and the > > associated bisect log): > > > > http://marc.info/?l=linux-crypto-vger&m=145575300630247&w=2 > > > > As for backports, I'm merely a lowly kernel user. > > I don't see how that breaks anything in userspace, can you please bring > this up with the developers of that patch and the crypto mailing list? I already did: http://marc.info/?l=linux-crypto-vger&m=145620828015563&w=2 The thread I pointed you to was what I was told by the crypto list: http://marc.info/?l=linux-crypto-vger&m=145620853015626&w=2 In that thread, the developer was also apparently made aware: http://www.spinics.net/lists/linux-crypto/msg17931.html I think bringing it up to the developer and the crypto mailing list again is unlikely to get this issue addressed, as they are both aware of it. later, preed -- J. Paul Reed PGP: 0xDF8708F8 -- http://www.soberbuildengineer.com ========================================================================= I've never seen an airplane yet that can read the type ratings on your pilot's license. -- Chuck Boedecker -- 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