linux-kernel - Re: [GIT PULL] Core block IO bits for 2.6.39

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]

Date:	Fri, 25 Mar 2011 09:01:40 -0400
From:	Chris Mason <chris.mason@...cle.com>
To:	Dave Chinner <david@...morbit.com>
Cc:	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Jens Axboe <jaxboe@...ionio.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Core block IO bits for 2.6.39 - early Oops

Excerpts from Dave Chinner's message of 2011-03-25 00:41:28 -0400:
> On Thu, Mar 24, 2011 at 08:34:41PM +0100, Markus Trippelsdorf wrote:

[ oopsen and fs corruptions in linus master ]

> 
> So the patchset is causing repeatable filesystem corruption? Sounds
> to me like this series is not yet ready for mainline merging. Last
> thing I want to spend the .39 cycle helping people recover busted
> filesystems as a result of undercooked block layer changes...
> 

I tried to reproduce this, but didn't get farther than make
modules_install.  My setup works like this:

build new kernel
start virtual machine off new kernel
make modules_install over NFS to get new modules (just the filesystems)

make modules_install instantly did this:
BUG: spinlock recursion on CPU#0, as/2014
 lock: ffff88006e939d08, .magic: dead4ead, .owner: as/2014, .owner_cpu: 0
Pid: 2014, comm: as Tainted: G        W   2.6.38-josef+ #228
Call Trace:
 [<ffffffff812712e5>] spin_bug+0x9c/0xa3
 [<ffffffff81271333>] do_raw_spin_lock+0x47/0x13c
 [<ffffffff81068329>] ? get_parent_ip+0x11/0x41
 [<ffffffff815dd796>] _raw_spin_lock+0x23/0x27
 [<ffffffff811258f9>] igrab+0x1b/0x48
 [<ffffffff811b2249>] nfs_updatepage+0x2ac/0x469
 [<ffffffff811a4eff>] nfs_write_end+0x26d/0x298
 [<ffffffff81068329>] ? get_parent_ip+0x11/0x41
 [<ffffffff810d43b7>] generic_file_buffered_write+0x189/0x26a
 [<ffffffff810db611>] ? __alloc_pages_nodemask+0x14d/0x7a8
 [<ffffffff810d5b2e>] __generic_file_aio_write+0x32b/0x35b
 [<ffffffff810d5bbf>] generic_file_aio_write+0x61/0xba
 [<ffffffff811a5ab7>] nfs_file_write+0xde/0x161
 [<ffffffff8110f3ba>] do_sync_write+0xcb/0x108
 [<ffffffff810f78d4>] ? do_mmap_pgoff+0x29a/0x2f4
 [<ffffffff8110f9f7>] vfs_write+0xb5/0x131
 [<ffffffff8110fc5c>] sys_write+0x4a/0x71
 [<ffffffff815e34ab>] system_call_fastpath+0x16/0x1b

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