On Sat, 2016-04-30 at 21:57 +0100, Al Viro wrote: > On Sat, Apr 30, 2016 at 04:39:25PM -0400, Jeff Layton wrote: > > > > > Attached. Also I ran the same test on a 4.6.0-rc1 kernel and it > > worked > > fine, so it does seem to be a regression introduced somewhere in > > your > > patch pile. Also, FWIW the machine is a KVM guest. > OK... Could you try #work.lookups on your setup? That doesn't > contain the > last commit; the deadlock ought to be dealt with, though. I'm trying > to > reproduce the corruption with KASAN enabled, will try your config > once that's > finished... I'll do the same (re: KASAN). Also FWIW, a few months ago I hit some oopses in the same inline function (get_freepointer). It turned out to be a double-free due to my own misuse of the fsnotify API. I wonder though if this might also be a double free somewhere? -- Jeff Layton <jlayton@xxxxxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
