linux-kernel - Re: BUG: Bad page map in process udevd (anon

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: <m1zkpue9vo.fsf@fess.ebiederm.org>
Date:	Thu, 17 Feb 2011 11:31:07 -0800
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Michal Hocko <mhocko@...e.cz>,
	linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: BUG: Bad page map in process udevd (anon_vma: (null)) in 2.6.38-rc4

Linus Torvalds <torvalds@...ux-foundation.org> writes:

> On Thu, Feb 17, 2011 at 10:57 AM, Eric W. Biederman
> <ebiederm@...ssion.com> wrote:
>>
>> fedora 14
>> ext4 on all filesystems
>
> Your dmesg snippets had ext3 mentioned, though:
>
>   <6>EXT3-fs (sda1): recovery required on readonly filesystem
>   <6>EXT3-fs (sda1): write access will be enabled during recovery
>   <6>EXT3-fs: barriers not enabled
>   ..
>   <6>EXT3-fs (sda1): recovery complete
>   <6>EXT3-fs (sda1): mounted filesystem with ordered data mode
>   <6>dracut: Mounted root filesystem /dev/sda1
>
> not that I see that it should matter, but there's been some bigger
> ext3 changes too (like the batched discard).
>
> I don't really think ext3 is the issue, though.

Oh right.  I changed the configuration but I haven't upgraded this
machine off of ext3 root yet.   The partition where all of the data is
going is ext4.  Creating a chrooted build environment on the fly is
great but it can momentarily swamp the disk.

>> I was about to say this happens with DEBUG_PAGEALLOC enabled but it
>> appears that options keeps eluding my fingers when I have a few minutes
>> to play with it.  Perhaps this time will be the charm.
>
> Please do. You seem to be much better at triggering it than anybody
> else. And do the DEBUG_LIST and DEBUG_SLUB_ON things too (even if the
> DEBUG_LIST thing won't catch list_move())

DEBUG_LIST I did manage to get enabled and it didn't catch anything,
despite some bad PMD's showing up.  The other two should be enabled in
the kernel version I am building right now.

It does look like this can go quiet for a days at a time.  The 17th is
the first my logs show of it since the 14th.

messages:Feb 14 17:55:12 bs38 kernel: BUG: Bad page map in process [manager]  pte:ffff88028c45f748 pmd:28c45f067
messages:Feb 14 17:55:12 bs38 kernel: BUG: Bad page map in process [manager]  pte:ffff88028c45f748 pmd:28c45f067
messages:Feb 17 00:49:53 bs38 kernel: BUG: Bad page map in process Sysdb  pte:ffff8802742b3758 pmd:2742b3067
messages:Feb 17 00:49:53 bs38 kernel: BUG: Bad page map in process Sysdb  pte:ffff8802742b3758 pmd:2742b3067
messages:Feb 17 10:00:43 bs38 kernel: BUG: Bad page map in process cc1plus  pte:ffff880190f73758 pmd:190f73067
messages:Feb 17 10:00:43 bs38 kernel: BUG: Bad page map in process cc1plus  pte:ffff88025efed758 pmd:25efed067
messages:Feb 17 10:00:43 bs38 kernel: BUG: Bad page map in process cc1plus  pte:ffff88025efed758 pmd:25efed067
messages:Feb 17 10:00:43 bs38 kernel: BUG: Bad page map in process cc1plus  pte:ffff880190f73758 pmd:190f73067

Eric
--
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/