Andrei Vagin <avagin@xxxxxxxxx> writes: > On Sun, Dec 11, 2016 at 10:51 PM, Eric W. Biederman > <ebiederm@xxxxxxxxxxxx> wrote: >> Andrei Vagin <avagin@xxxxxxxxx> writes: >> >>> On Sun, Dec 11, 2016 at 6:55 PM, Andrei Vagin <avagin@xxxxxxxxx> wrote: >>>> Hi, >>>> >>>> CRIU tests triggered a kernel bug: >>> >>> I''ve booted this kernel with slub_debug=FZ and now I see these >>> messages: >> >> I think I have dropped the cause of this corruption from my linux-next >> tree, and hopefully from linux-next. >> >> I believe this was: "inotify: Convert to using per-namespace limits" >> If you could verify dropping/reverting that patch from linux-next causes >> this failure to go away I would appreciate. >> >> I am quite puzzled why that patch causes heap corruption but it seems clear >> it does. >> >> If you can trigger this problem without that patch I would really >> appreciate knowing. > > It works without this patch. All tests passed on next-20161212. Thanks! Thank you for verifying that. Eric -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>