linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrei Vagin <avagin@gmail.com>
Cc: linux-mm@kvack.org, Cyrill Gorcunov <gorcunov@openvz.org>,
	Nikolay Borisov <n.borisov.lkml@gmail.com>
Subject: Re: linux-next: kernel BUG at mm/vmalloc.c:463!
Date: Wed, 14 Dec 2016 08:49:32 +1300	[thread overview]
Message-ID: <877f73hann.fsf@xmission.com> (raw)
In-Reply-To: <87wpf5c68l.fsf@xmission.com> (Eric W. Biederman's message of "Tue, 13 Dec 2016 08:11:38 +1300")

ebiederm@xmission.com (Eric W. Biederman) writes:

> 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:

Andrei, are the CRIU tests that failed part of the normal regression
tests for CRIU that Nikolay Borisov can run so he can reproduce this
failure and figure out what is wrong with his code?

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>

      reply	other threads:[~2016-12-13 19:52 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
2016-12-13 19:49         ` Eric W. Biederman [this message]

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=877f73hann.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=avagin@gmail.com \
    --cc=gorcunov@openvz.org \
    --cc=linux-mm@kvack.org \
    --cc=n.borisov.lkml@gmail.com \
    /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).