From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrei Vagin <avagin@gmail.com>
Cc: linux-mm@kvack.org, Cyrill Gorcunov <gorcunov@openvz.org>
Subject: Re: linux-next: kernel BUG at mm/vmalloc.c:463!
Date: Tue, 13 Dec 2016 08:11:38 +1300 [thread overview]
Message-ID: <87wpf5c68l.fsf@xmission.com> (raw)
In-Reply-To: <CANaxB-xGO9-tNBasB2G_5qxavja6h0RB9npsh4Uu9=YbJtwgHQ@mail.gmail.com> (Andrei Vagin's message of "Mon, 12 Dec 2016 10:55:04 -0800")
Andrei Vagin <avagin@gmail.com> writes:
> On Sun, Dec 11, 2016 at 10:51 PM, Eric W. Biederman
> <ebiederm@xmission.com> wrote:
>> Andrei Vagin <avagin@gmail.com> writes:
>>
>>> On Sun, Dec 11, 2016 at 6:55 PM, Andrei Vagin <avagin@gmail.com> 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@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-12-12 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 2:55 linux-next: kernel BUG at mm/vmalloc.c:463! Andrei Vagin
2016-12-12 6:04 ` Andrei Vagin
2016-12-12 6:51 ` Eric W. Biederman
2016-12-12 18:55 ` Andrei Vagin
2016-12-12 19:11 ` Eric W. Biederman [this message]
2016-12-13 19:49 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpf5c68l.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=avagin@gmail.com \
--cc=gorcunov@openvz.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).