linux-kernel - Re: fs: Inode cache scalability V3

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: <20101013145102.GA12155@infradead.org>
Date:	Wed, 13 Oct 2010 10:51:02 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Dave Chinner <david@...morbit.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: fs: Inode cache scalability V3

I've got an interesting oops running xfsqa 030 on this series.  Not
sure it's a new one, though:

Entering kdb (current=0xf6ff7270, pid 2274) on processor 0 Oops: (null)
due to oops @ 0xc022de60
<d>Modules linked in:
<c>
<d>Pid: 2274, comm: flush-252:16 Not tainted 2.6.36-rc7+ #399 /Bochs
<d>EIP: 0060:[<c022de60>] EFLAGS: 00010246 CPU: 0 EIP is at redirty_tail+0x90/0xa0
<d>EAX: c0d6cda0 EBX: f54b67fc ECX: 00000000 EDX: 00000000
<d>ESI: f7808c88 EDI: f685a308 EBP: f4109e78 ESP: f4109e70
<d> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
<0>Process flush-252:16 (pid: 2274, ti=f4108000 task=f6ff7270 task.ti=f4108000)
<0>Stack: f685a2a4 f54b67fc f4109ea4 c022e7df f4109e90 f685a310 f685a318 f4109ed8
<0> 014b6804 f5d29260 f5d29260 f685a2a4 00000000 f4109f18 c022ef78 00000001
<0> f4109ed8 00000000 00000000 c018bb4d f6ff7270 f685a310 f6ff7714 f685a308
<0>Call Trace:
<0> [<c022e7df>] ? writeback_sb_inodes+0x6f/0x1a0
<0> [<c022ef78>] ? wb_writeback+0x118/0x320
<0> [<c018bb4d>] ? local_clock+0x6d/0x70
<0> [<c016f0bc>] ? local_bh_enable_ip+0x6c/0xd0
<0> [<c022f1f5>] ? wb_do_writeback+0x75/0x190
<0> [<c0175d44>] ? del_timer+0x74/0xc0
--
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/