From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail144.messagelabs.com (mail144.messagelabs.com [216.82.254.51]) by kanga.kvack.org (Postfix) with ESMTP id 804AB8D0017 for ; Mon, 15 Nov 2010 14:54:47 -0500 (EST) Date: Mon, 15 Nov 2010 20:54:39 +0100 From: Markus Trippelsdorf Subject: Re: BUG: Bad page state in process (current git) Message-ID: <20101115195439.GA1569@arch.trippelsdorf.de> References: <20101110152519.GA1626@arch.trippelsdorf.de> <20101110154057.GA2191@arch.trippelsdorf.de> <20101112122003.GA1572@arch.trippelsdorf.de> <20101115123846.GA30047@arch.trippelsdorf.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101115123846.GA30047@arch.trippelsdorf.de> Sender: owner-linux-mm@kvack.org To: Christoph Lameter Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Theodore Ts'o , linux-ext4@vger.kernel.org List-ID: On 2010.11.15 at 13:38 +0100, Markus Trippelsdorf wrote: > On 2010.11.12 at 13:20 +0100, Markus Trippelsdorf wrote: > > > > 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: > [] ? bad_page+0x92/0xe0 > [] ? get_page_from_freelist+0x4b0/0x570 > [] ? apic_timer_interrupt+0xe/0x20 > [] ? __alloc_pages_nodemask+0x113/0x6b0 > [] ? file_read_actor+0xc4/0x190 > [] ? generic_file_aio_read+0x560/0x6b0 > [] ? handle_mm_fault+0x6bd/0x970 > [] ? do_page_fault+0x120/0x410 > [] ? do_brk+0x275/0x360 > [] ? page_fault+0x1f/0x30 > Disabling lock debugging due to kernel taint And another one. But this time it seems to point to ext4: BUG: Bad page state in process rm pfn:52e54 page:ffffea0001222260 count:0 mapcount:0 mapping: (null) index:0x0 page flags: 0x4000000000000008(uptodate) Pid: 2084, comm: rm Not tainted 2.6.37-rc1-00549-gae712bf-dirty #23 Call Trace: [] ? bad_page+0x92/0xe0 [] ? get_page_from_freelist+0x4b0/0x570 [] ? ext4_ext_put_in_cache+0x46/0x90 [] ? __alloc_pages_nodemask+0x113/0x6b0 [] ? number.clone.2+0x2b7/0x2f0 [] ? find_get_page+0x75/0xb0 [] ? find_or_create_page+0x51/0xb0 [] ? __getblk+0xd7/0x260 [] ? ext4_getblk+0x8f/0x1e0 [] ? ext4_bread+0xd/0x70 [] ? htree_dirblock_to_tree+0x34/0x190 [] ? ext4_htree_fill_tree+0x9f/0x250 [] ? do_filp_open+0x12d/0x5e0 [] ? ext4_readdir+0x14d/0x5a0 [] ? filldir+0x0/0xd0 [] ? vfs_readdir+0xa8/0xd0 [] ? filldir+0x0/0xd0 [] ? sys_getdents+0x81/0xf0 [] ? system_call_fastpath+0x16/0x1b Disabling lock debugging due to kernel taint I don't know. Could a possible bug in linux/fs/ext4/page-io.c be responsible for something like this? -- Markus -- 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 policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: email@kvack.org