From: Hugh Dickins <hughd@google.com>
To: Roland Dreier <roland@purestorage.com>
Cc: Dave Jones <davej@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel-team@fedoraproject.org
Subject: Re: exit_mmap() BUG_ON triggering since 3.1
Date: Wed, 15 Feb 2012 18:48:42 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.00.1202151841400.19722@eggly.anvils> (raw)
In-Reply-To: <CAL1RGDVQDr-h5Makto-FXHeHUkK4sJooszciiNvVR66WonQ=6w@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1220 bytes --]
On Wed, 15 Feb 2012, Roland Dreier wrote:
> On Wed, Feb 15, 2012 at 6:14 PM, Hugh Dickins <hughd@google.com> wrote:
> > My suspicion was that it would be related to Transparent HugePages:
> > they do complicate the pagetable story. And I think I have found a
> > potential culprit. I don't know if nr_ptes is the only loser from
> > these two split_huge_pages calls, but assuming it is...
>
> Do you have an idea when this bug might have been introduced?
> Presumably it's been there since THP came in?
That's right, since THP came in (2.6.38 on mainline,
but IIRC Red Hat had THP applied to an earlier kernel).
>
> The reason I ask is that I have one of these exit_mm BUG_ONs
> in my pile of one-off unreproducible crashes, but in my case it
> happened with 2.6.39 (with THP enabled). So I'm wondering if
> I can cross it off my list and blame this bug, or if it remains one
> of those inexplicable mysteries...
If you think that system could have been using swap, yes, cross it
off (unless someone points out that I'm totally wrong, because....).
But if you know that system used no swap (and didn't get involved
in any memory-failure hwpoison business), then keep on worrying!
Hugh
next prev parent reply other threads:[~2012-02-16 2:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 18:33 Dave Jones
2012-02-16 2:14 ` Hugh Dickins
2012-02-16 2:22 ` Roland Dreier
2012-02-16 2:48 ` Hugh Dickins [this message]
2012-02-16 7:07 ` Andrea Arcangeli
2012-02-16 9:53 ` Hugh Dickins
2012-02-16 21:42 ` Andrea Arcangeli
2012-03-02 22:53 ` Hugh Dickins
2012-03-02 22:58 ` Andrew Morton
2012-03-02 23:09 ` Hugh Dickins
2012-03-05 19:59 ` Josh Boyer
2012-03-05 20:07 ` Andrew Morton
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=alpine.LSU.2.00.1202151841400.19722@eggly.anvils \
--to=hughd@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roland@purestorage.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