linux-kernel - Re: BUG: Bad page state in process (current git)

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: <20101115123846.GA30047@arch.trippelsdorf.de>
Date:	Mon, 15 Nov 2010 13:38:46 +0100
From:	Markus Trippelsdorf <markus@...ppelsdorf.de>
To:	Christoph Lameter <cl@...ux.com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: BUG: Bad page state in process (current git)

On 2010.11.12 at 13:20 +0100, Markus Trippelsdorf wrote:
> On 2010.11.10 at 15:46 -0600, Christoph Lameter wrote:
> > On Wed, 10 Nov 2010, Markus Trippelsdorf wrote:
> > 
> > > I found this in my dmesg:
> > > ACPI: Local APIC address 0xfee00000
> > >  [ffffea0000000000-ffffea0003ffffff] PMD -> [ffff8800d0000000-ffff8800d39fffff] on node 0
> > 
> > That only shows you how the memmap was virtually mapped.
> 
> Yes. Fortunately the BUG is gone since I pulled the upcoming drm fixes

No. I happend again today (with those fixes already applied):

BUG: Bad page state in process knode  pfn:7f0a8
page:ffffea0001bca4c0 count:0 mapcount:0 mapping:          (null) index:0x0
page flags: 0x4000000000000008(uptodate)
Pid: 18310, comm: knode Not tainted 2.6.37-rc1-00549-gae712bf-dirty #16
Call Trace:
 [<ffffffff810a9022>] ? bad_page+0x92/0xe0
 [<ffffffff810aa240>] ? get_page_from_freelist+0x4b0/0x570
 [<ffffffff8102e50e>] ? apic_timer_interrupt+0xe/0x20
 [<ffffffff810aa413>] ? __alloc_pages_nodemask+0x113/0x6b0
 [<ffffffff810a2dd4>] ? file_read_actor+0xc4/0x190
 [<ffffffff810a4a70>] ? generic_file_aio_read+0x560/0x6b0
 [<ffffffff810bdf8d>] ? handle_mm_fault+0x6bd/0x970
 [<ffffffff8104b1d0>] ? do_page_fault+0x120/0x410
 [<ffffffff810c3d85>] ? do_brk+0x275/0x360
 [<ffffffff81452d8f>] ? page_fault+0x1f/0x30
Disabling lock debugging due to kernel taint
-- 
Markus
--
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/