linux-kernel - Re: Regression: Bad page map in process xyz

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120226202010.GA7353@redhat.com>
Date:	Sun, 26 Feb 2012 15:20:10 -0500
From:	Dave Jones <davej@...hat.com>
To:	Hugh Dickins <hughd@...gle.com>
Cc:	Maciej Rutecki <maciej.rutecki@...il.com>,
	Jiri Slaby <jslaby@...e.cz>, n-horiguchi@...jp.nec.com,
	kamezawa.hiroyu@...fujitsu.com,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Jiri Slaby <jirislaby@...il.com>, linux-mm@...ck.org
Subject: Re: Regression: Bad page map in process xyz

On Sun, Feb 26, 2012 at 05:10:31AM -0800, Hugh Dickins wrote:
 > 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@...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.

FWIW, we've been getting a bunch of these since 3.0 in Fedora.
I've been trying to come up with some way of trying to reproduce them
myself, without any luck. Some of our users seem to hit them surprisingly easily.

At first I started wondering if it was just bad hardware, but the frequency
that we've been getting reports seems to suggest something more screwed up.

https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&bug_status=POST&classification=Fedora&component=kernel&product=Fedora&query_format=advanced&short_desc=bug+page+map&short_desc_type=allwordssubstr&version=15&version=16&version=rawhide&order=bug_id&query_based_on=

Until last week, we only had reports up until 3.2, but now that the F17 alpha
is getting tested, people are starting to hit it on 3.3rc too

I'll try a test build with that commit backed out for our users to try out
next week.

	Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/