From: Andrea Arcangeli <aarcange@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Trevor Kramer <tkramer@hampshire.edu>, linux-numa@vger.kernel.org
Subject: Re: kernel crash when using libnuma
Date: Mon, 6 Feb 2012 23:43:41 +0100 [thread overview]
Message-ID: <20120206224341.GX31064@redhat.com> (raw)
In-Reply-To: <20120206222318.GR11715@one.firstfloor.org>
On Mon, Feb 06, 2012 at 11:23:18PM +0100, Andi Kleen wrote:
> On Mon, Feb 06, 2012 at 03:57:52AM -0500, Trevor Kramer wrote:
> > I have a program which can use libnuma to allocate memory using
> > numa_alloc_onnode() or using malloc. When running in malloc mode
> > everything works fine but when running under libnuma mode I get
> > consistent kernel panics with the following traces. This only occurs
> > when multiple threads are running. Has anyone seen this before or have
> > any recommendations on how to debug further?
>
>
> Looks like a THP problem.
>
> For RHEL issues you normally need to talk to RedHat, these lists
> are more for mainline.
Well at this point we don't know yet if this affects mainline too or
not.
To be sure, you can file a bugzilla.redhat.com and we'll fix it ASAP
and submit the fix upstream if it happens there too.
Best of all is if you can send the source of the program that trigger
this attached to the bugzilla (or by email). Or create a small source
testcase that can reproduce it.
A BUG_ON is triggering, probably the rmap mapcount vs page->mapcount
one. I'm unsure why this is related to libnuma only, and a wild guess
could be that the vma policy does something wrong over the vmas to the
point rmap won't find the pmds (like wrong vma splitting or
something). But thanks to the BUG_ON there is close to zero risk of
data or memory corruption, just an annoyance we need to fix (plus the
program I assume requires root to use libnuma).
The last time (more than one year ago) I've seen this it was a bug in
the vma splitting. So again guessing wild, it could be a missing
vma_adjust_trans_huge in mempolicy.c or some other place splitting
vmas to create a partial vma policy on an existing vma.
Thanks,
Andrea
prev parent reply other threads:[~2012-02-06 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 8:57 kernel crash when using libnuma Trevor Kramer
2012-02-06 22:23 ` Andi Kleen
2012-02-06 22:43 ` Andrea Arcangeli [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=20120206224341.GX31064@redhat.com \
--to=aarcange@redhat.com \
--cc=andi@firstfloor.org \
--cc=linux-numa@vger.kernel.org \
--cc=tkramer@hampshire.edu \
/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).