From: Hugh Dickins <hughd@google.com>
To: Maciej Rutecki <maciej.rutecki@gmail.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
n-horiguchi@ah.jp.nec.com, kamezawa.hiroyu@jp.fujitsu.com,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Jiri Slaby <jirislaby@gmail.com>,
linux-mm@kvack.org
Subject: Re: Regression: Bad page map in process xyz
Date: Sun, 26 Feb 2012 05:10:31 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.00.1202260502450.5648@eggly.anvils> (raw)
In-Reply-To: <201202261027.48029.maciej.rutecki@gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1096 bytes --]
On Sun, 26 Feb 2012, Maciej Rutecki wrote:
> On poniedziałek, 20 lutego 2012 o 11:02:17 Jiri Slaby wrote:
> > Hi,
> >
> > I'm getting a ton of
> > BUG: Bad page map in process zypper pte:676b700029736c6f pmd:44967067
> > when trying to upgrade the system by:
> > zypper dup
> >
> > I bisected that to:
> > commit afb1c03746aa940374b73a7d5750ee05a2376077
> > Author: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> > Date: Fri Feb 17 10:57:58 2012 +1100
> >
> > thp: optimize away unnecessary page table locking
> >
> > thanks,
>
> I created a Bugzilla entry at
> https://bugzilla.kernel.org/show_bug.cgi?id=42820
> for your bug/regression report, please add your address to the CC list in
> there, thanks!
No, thanks for spotting it, but please remove from the regressions
report: it's not a regression in 3.3-rc but in linux-next - don't take
my word for it, check the commit and you'll not find it in 3.3-rc.
We do still need to get the fix into linux-next: Horiguchi-san, has
akpm put your fix in mm-commits yet? Please send it again if not.
Hugh
next prev parent reply other threads:[~2012-02-26 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 10:02 Regression: Bad page map in process xyz Jiri Slaby
2012-02-26 9:27 ` Maciej Rutecki
2012-02-26 13:10 ` Hugh Dickins [this message]
2012-02-26 17:04 ` Maciej Rutecki
2012-02-26 20:20 ` Dave Jones
2012-02-27 4:45 ` Naoya Horiguchi
2012-02-27 8:51 ` Jiri Slaby
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.1202260502450.5648@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maciej.rutecki@gmail.com \
--cc=n-horiguchi@ah.jp.nec.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;
as well as URLs for NNTP newsgroup(s).