From: Sasha Levin <sasha.levin@oracle.com>
To: Hugh Dickins <hughd@google.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: BUG: Bad page state in process ksmd
Date: Thu, 27 Mar 2014 11:31:30 -0400 [thread overview]
Message-ID: <53344452.7090107@oracle.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1403270806340.4269@eggly.anvils>
On 03/27/2014 11:21 AM, Hugh Dickins wrote:
> I've thought about this some, and slept on it, but don't yet see
> how it comes about. I'll have to come back to it later.
>
> Was it a one-off, or do you find it fairly easy to reproduce?
>
> If the latter, it would be interesting to know if it comes from
> recent changes or not. mm/mlock.c does appear to have been under
> continuous revision for several releases (but barely changed in next).
I can't say it's easy to reproduce but it did happen 5-6 times at this point.
As far as I can tell there were no big changes in trinity for the last week
or so while we were in lsf/mm, and this issue being reproducible makes me
believe it has something to do with recent changes to mm code.
Thanks,
Sasha
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sasha.levin@oracle.com>
To: Hugh Dickins <hughd@google.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: BUG: Bad page state in process ksmd
Date: Thu, 27 Mar 2014 11:31:30 -0400 [thread overview]
Message-ID: <53344452.7090107@oracle.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1403270806340.4269@eggly.anvils>
On 03/27/2014 11:21 AM, Hugh Dickins wrote:
> I've thought about this some, and slept on it, but don't yet see
> how it comes about. I'll have to come back to it later.
>
> Was it a one-off, or do you find it fairly easy to reproduce?
>
> If the latter, it would be interesting to know if it comes from
> recent changes or not. mm/mlock.c does appear to have been under
> continuous revision for several releases (but barely changed in next).
I can't say it's easy to reproduce but it did happen 5-6 times at this point.
As far as I can tell there were no big changes in trinity for the last week
or so while we were in lsf/mm, and this issue being reproducible makes me
believe it has something to do with recent changes to mm code.
Thanks,
Sasha
next prev parent reply other threads:[~2014-03-27 15:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 15:13 mm: BUG: Bad page state in process ksmd Sasha Levin
2014-03-26 15:13 ` Sasha Levin
2014-03-26 19:55 ` Andrew Morton
2014-03-26 19:55 ` Andrew Morton
2014-03-26 21:39 ` Sasha Levin
2014-03-26 21:39 ` Sasha Levin
2014-03-27 15:36 ` Hugh Dickins
2014-03-27 15:36 ` Hugh Dickins
2014-03-27 15:21 ` Hugh Dickins
2014-03-27 15:21 ` Hugh Dickins
2014-03-27 15:31 ` Sasha Levin [this message]
2014-03-27 15:31 ` Sasha Levin
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=53344452.7090107@oracle.com \
--to=sasha.levin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.