From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: linux-mm@kvack.org, Fedora Kernel Team <kernel-team@fedoraproject.org>
Subject: exit_mmap() BUG_ON triggering since 3.1
Date: Wed, 15 Feb 2012 13:33:18 -0500 [thread overview]
Message-ID: <20120215183317.GA26977@redhat.com> (raw)
We've had three reports against the Fedora kernel recently where
a process exits, and we're tripping up the
BUG_ON(mm->nr_ptes > (FIRST_USER_ADDRESS+PMD_SIZE-1)>>PMD_SHIFT);
in exit_mmap()
It started happening with 3.1, but still occurs on 3.2
(no 3.3rc reports yet, but it's not getting much testing).
https://bugzilla.redhat.com/show_bug.cgi?id=786632
https://bugzilla.redhat.com/show_bug.cgi?id=787527
https://bugzilla.redhat.com/show_bug.cgi?id=790546
I don't see anything special in common between the loaded modules.
anyone?
Dave
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: linux-mm@kvack.org, Fedora Kernel Team <kernel-team@fedoraproject.org>
Subject: exit_mmap() BUG_ON triggering since 3.1
Date: Wed, 15 Feb 2012 13:33:18 -0500 [thread overview]
Message-ID: <20120215183317.GA26977@redhat.com> (raw)
We've had three reports against the Fedora kernel recently where
a process exits, and we're tripping up the
BUG_ON(mm->nr_ptes > (FIRST_USER_ADDRESS+PMD_SIZE-1)>>PMD_SHIFT);
in exit_mmap()
It started happening with 3.1, but still occurs on 3.2
(no 3.3rc reports yet, but it's not getting much testing).
https://bugzilla.redhat.com/show_bug.cgi?id=786632
https://bugzilla.redhat.com/show_bug.cgi?id=787527
https://bugzilla.redhat.com/show_bug.cgi?id=790546
I don't see anything special in common between the loaded modules.
anyone?
Dave
next reply other threads:[~2012-02-15 18:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 18:33 Dave Jones [this message]
2012-02-15 18:33 ` exit_mmap() BUG_ON triggering since 3.1 Dave Jones
2012-02-16 2:14 ` Hugh Dickins
2012-02-16 2:14 ` Hugh Dickins
2012-02-16 2:22 ` Roland Dreier
2012-02-16 2:22 ` Roland Dreier
2012-02-16 2:48 ` Hugh Dickins
2012-02-16 7:07 ` Andrea Arcangeli
2012-02-16 7:07 ` Andrea Arcangeli
2012-02-16 9:53 ` Hugh Dickins
2012-02-16 9:53 ` Hugh Dickins
2012-02-16 21:42 ` Andrea Arcangeli
2012-02-16 21:42 ` Andrea Arcangeli
2012-03-02 22:53 ` Hugh Dickins
2012-03-02 22:53 ` Hugh Dickins
2012-03-02 22:58 ` Andrew Morton
2012-03-02 22:58 ` Andrew Morton
2012-03-02 23:09 ` Hugh Dickins
2012-03-02 23:09 ` Hugh Dickins
2012-03-05 19:59 ` Josh Boyer
2012-03-05 19:59 ` Josh Boyer
2012-03-05 20:07 ` Andrew Morton
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=20120215183317.GA26977@redhat.com \
--to=davej@redhat.com \
--cc=kernel-team@fedoraproject.org \
--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.