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. But it does > point the finger at cryptd. On additional testing, I think this might be related to some subtle race/timing issue so that git-bisect may not necessarily be able to pin-point the correct bad-commit: if I add a few printks in other parts of the IPsec stack (and change the timing), the problem does not reproduce. Let me try to collect more data on this. Meanwhile, if you can see some bug in the commit above, then it probably makes sense to fix it upstream anyway. --Sowmini -- 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
