linux-kernel - Re: [REPORT] BUG: spinlock recursion on CPU#0, init/1

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: <1294673609.12715.1.camel@laptop>
Date:	Mon, 10 Jan 2011 16:33:29 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Santosh Shilimkar <santosh.shilimkar@...com>
Cc:	linux-kernel@...r.kernel.org, Nick Piggin <npiggin@...nel.dk>,
	Trond Myklebust <trond.myklebust@....uio.no>
Subject: Re: [REPORT] BUG: spinlock recursion on CPU#0, init/1

On Mon, 2011-01-10 at 20:51 +0530, Santosh Shilimkar wrote:
> On latest mainline commit I seeing a regression when rootfs
> is mounted on NFS. Not sure if it's already known regression.
> 
> Anybody is aware of this one ?
> 
> --------------------------------------
> Uncompressing Linux... done, booting the kernel.
> Linux version 2.6.37-03766-g0390214 (a0393909@...93909-desktop) (gcc
> version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #44 SMP Mon Jan 10 20:41:27
> IST 2011
> 
> [....]
> 
> VFS: Mounted root (nfs filesystem) on device 0:13.
> Freeing init memory: 296K
> BUG: spinlock recursion on CPU#0, init/1
>  lock: ef5a1e0c, .magic: dead4ead, .owner: init/1, .owner_cpu: 0
> [<c0063290>] (unwind_backtrace+0x0/0xe4) from [<c024ce90>]
> (do_raw_spin_lock+0x48/0x158)
> [<c024ce90>] (do_raw_spin_lock+0x48/0x158) from [<c012f4e0>]
> (nameidata_dentry_drop_rcu+0x84/0x17c)
> [<c012f4e0>] (nameidata_dentry_drop_rcu+0x84/0x17c) from [<c012f608>]
> (d_revalidate+0x30/0x58)
> [<c012f608>] (d_revalidate+0x30/0x58) from [<c0132120>]
> (link_path_walk+0xb44/0xb64)
> [<c0132120>] (link_path_walk+0xb44/0xb64) from [<c0132338>]
> (do_path_lookup+0x44/0xcc)
> [<c0132338>] (do_path_lookup+0x44/0xcc) from [<c0132f08>]
> (do_filp_open+0xc8/0x56c)
> [<c0132f08>] (do_filp_open+0xc8/0x56c) from [<c0124828>]
> (do_sys_open+0x58/0xe4)
> [<c0124828>] (do_sys_open+0x58/0xe4) from [<c005c240>]
> (ret_fast_syscall+0x0/0x3c)
> BUG: spinlock lockup on CPU#0, init/1, ef5a1e0c
> [<c0063290>] (unwind_backtrace+0x0/0xe4) from [<c024cf84>]
> (do_raw_spin_lock+0x13c/0x158)
> [<c024cf84>] (do_raw_spin_lock+0x13c/0x158) from [<c012f4e0>]
> (nameidata_dentry_drop_rcu+0x84/0x17c)
> [<c012f4e0>] (nameidata_dentry_drop_rcu+0x84/0x17c) from [<c012f608>]
> (d_revalidate+0x30/0x58)
> [<c012f608>] (d_revalidate+0x30/0x58) from [<c0132120>]
> (link_path_walk+0xb44/0xb64)
> [<c0132120>] (link_path_walk+0xb44/0xb64) from [<c0132338>]
> (do_path_lookup+0x44/0xcc)
> [<c0132338>] (do_path_lookup+0x44/0xcc) from [<c0132f08>]
> (do_filp_open+0xc8/0x56c)
> [<c0132f08>] (do_filp_open+0xc8/0x56c) from [<c0124828>]
> (do_sys_open+0x58/0xe4)
> [<c0124828>] (do_sys_open+0x58/0xe4) from [<c005c240>]
> (ret_fast_syscall+0x0/0x3c)
> BUG: spinlock lockup on CPU#1, kworker/u:2/499, c05d3c80
> [<c0063290>] (unwind_backtrace+0x0/0xe4) from [<c024cf84>]
> (do_raw_spin_lock+0x13c/0x158)
> [<c024cf84>] (do_raw_spin_lock+0x13c/0x158) from [<c014afac>]
> (exit_fs+0x2c/0x84)
> [<c014afac>] (exit_fs+0x2c/0x84) from [<c0098274>] (do_exit+0x254/0x674)
> [<c0098274>] (do_exit+0x254/0x674) from [<c00b0944>] (kthread+0x88/0x8c)
> [<c00b0944>] (kthread+0x88/0x8c) from [<c005d490>]
> (kernel_thread_exit+0x0/0x8)

Smells like the stuff Nick touched.
--
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/