Re: Git bisected regression for ipsec/aead

2016-08-27 Thread Sowmini Varadhan
On (08/25/16 16:49), Herbert Xu wrote: > > On Fri, Aug 19, 2016 at 03:21:24PM -0400, Sowmini Varadhan wrote: > >7271b33cb87e80f3a416fb031ad3ca87f0bea80a is the first bad commit > This bisection doesn't make much sense as this patch just causes > cryptd to be used a little more more frequently

Re: Git bisected regression for ipsec/aead

2016-08-25 Thread Sowmini Varadhan
On (08/25/16 16:49), Herbert Xu wrote: > This bisection doesn't make much sense as this patch just causes > cryptd to be used a little more more frequently. But it does > point the finger at cryptd. : > So we have list corruption here, possibly caused by use-after-free. > I did spot one bug in

Re: Git bisected regression for ipsec/aead

2016-08-25 Thread Herbert Xu
On Fri, Aug 19, 2016 at 03:21:24PM -0400, Sowmini Varadhan wrote: > > Hi Herbert, > > In the process of testing ipsec I ran into panics (details below) > with the algorithm > "aead rfc4106(gcm(aes)) 0x1234567890123456789012345678901234567890 64" > > git-bisect analyzed this down to > >7271

Git bisected regression for ipsec/aead

2016-08-19 Thread Sowmini Varadhan
Hi Herbert, In the process of testing ipsec I ran into panics (details below) with the algorithm "aead rfc4106(gcm(aes)) 0x1234567890123456789012345678901234567890 64" git-bisect analyzed this down to 7271b33cb87e80f3a416fb031ad3ca87f0bea80a is the first bad commit commit 7271b33cb87e80f