linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: linux-mm@kvack.org
Subject: SIGBUS accessing MAP_HUGETLB space w/ nr_overcommit == 0
Date: Tue, 28 May 2013 18:42:28 -0700	[thread overview]
Message-ID: <CALCETrV-6_Uk=OMc6XZv61tFCKgAM77TzNs21FeOXExavUoSiw@mail.gmail.com> (raw)

I switched a system from Linux 3.5 to 3.9.4, and I have some crashes
that I didn't have before.  The cause is a SIGBUS w/ code BUS_ADRERR
on what I presume is the first access to a MAP_HUGETLB | MAP_PRIVATE
page.  I have nr_overcommit_hugepages == 0, so this shouldn't happen.
There are no kernel log messages at all.

Is there possibly a regression here?  Nothing seems to be asserting
any invariants with respect to the freelist size and the number of
accounted free hugepages.

I do not have CONFIG_CGROUP_HUGETLB set.

Thanks,
Andy

--
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:[~2013-05-29  1:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CALCETrV-6_Uk=OMc6XZv61tFCKgAM77TzNs21FeOXExavUoSiw@mail.gmail.com' \
    --to=luto@amacapital.net \
    --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