From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>,
Nick Piggin <npiggin@kernel.dk>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: NFS root lockups with -next 20110113
Date: Thu, 13 Jan 2011 12:06:27 +0000 [thread overview]
Message-ID: <20110113120626.GB30351@opensource.wolfsonmicro.com> (raw)
With -next 20110113 I'm experiencing lockups shortly after userspace
starts when booting with my root filesystem on NFS, log below. I can
boot into /bin/sh but running real userspace triggers this very easily.
This was introduced sometime this week.
I've not bisected or otherwise investigated much yet, but I do notice
code added recently by Nick in "fs: rcu-walk for path lookup" showing up
in the backtrace so including him in the CCs.
Tail of the console log:
INIT: version 2.86 booting
[ 15.250000] BUG: spinlock recursion on CPU#0, rc/1151
[ 15.250000] lock: c74ad678, .magic: dead4ead, .owner: rc/1151, .owner_cpu: 0
[ 15.260000] [<c0035118>] (unwind_backtrace+0x0/0xe4) from [<c0190454>] (do_raw_spin_lock+0x48/0x148)
[ 15.260000] [<c0190454>] (do_raw_spin_lock+0x48/0x148) from [<c00c89f0>] (nameidata_dentry_drop_rcu+0x84/0x180)
[ 15.270000] [<c00c89f0>] (nameidata_dentry_drop_rcu+0x84/0x180) from [<c00c8b1c>] (d_revalidate+0x30/0x58)
[ 15.280000] [<c00c8b1c>] (d_revalidate+0x30/0x58) from [<c00cb82c>] (link_path_walk+0xad8/0xb00)
[ 15.290000] [<c00cb82c>] (link_path_walk+0xad8/0xb00) from [<c00cba4c>] (do_path_lookup+0x44/0xcc)
[ 15.300000] [<c00cba4c>] (do_path_lookup+0x44/0xcc) from [<c00cc3f4>] (user_path_at+0x58/0x90)
[ 15.310000] [<c00cc3f4>] (user_path_at+0x58/0x90) from [<c00c4210>] (vfs_fstatat+0x28/0x54)
[ 15.320000] [<c00c4210>] (vfs_fstatat+0x28/0x54) from [<c00c431c>] (sys_stat64+0x14/0x34)
[ 15.330000] [<c00c431c>] (sys_stat64+0x14/0x34) from [<c002f4e0>] (ret_fast_syscall+0x0/0x30)
[ 25.830000] BUG: spinlock lockup on CPU#0, rc/1151, c74ad678
[ 25.830000] [<c0035118>] (unwind_backtrace+0x0/0xe4) from [<c0190518>] (do_raw_spin_lock+0x10c/0x148)
[ 25.840000] [<c0190518>] (do_raw_spin_lock+0x10c/0x148) from [<c00c89f0>] (nameidata_dentry_drop_rcu+0x84/0x180)
[ 25.850000] [<c00c89f0>] (nameidata_dentry_drop_rcu+0x84/0x180) from [<c00c8b1c>] (d_revalidate+0x30/0x58)
[ 25.860000] [<c00c8b1c>] (d_revalidate+0x30/0x58) from [<c00cb82c>] (link_path_walk+0xad8/0xb00)
[ 25.870000] [<c00cb82c>] (link_path_walk+0xad8/0xb00) from [<c00cba4c>] (do_path_lookup+0x44/0xcc)
[ 25.870000] [<c00cba4c>] (do_path_lookup+0x44/0xcc) from [<c00cc3f4>] (user_path_at+0x58/0x90)
[ 25.880000] [<c00cc3f4>] (user_path_at+0x58/0x90) from [<c00c4210>] (vfs_fstatat+0x28/0x54)
[ 25.890000] [<c00c4210>] (vfs_fstatat+0x28/0x54) from [<c00c431c>] (sys_stat64+0x14/0x34)
[ 25.900000] [<c00c431c>] (sys_stat64+0x14/0x34) from [<c002f4e0>] (ret_fast_syscall+0x0/0x30)
next reply other threads:[~2011-01-13 12:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 12:06 Mark Brown [this message]
2011-01-13 13:22 ` NFS root lockups with -next 20110113 J. R. Okajima
2011-01-13 13:28 ` Santosh Shilimkar
2011-01-13 13:28 ` Santosh Shilimkar
2011-01-13 13:45 ` J. R. Okajima
2011-01-13 13:45 ` J. R. Okajima
2011-01-14 3:59 ` Nick Piggin
2011-01-14 3:59 ` Nick Piggin
2011-01-14 4:41 ` J. R. Okajima
2011-01-14 4:41 ` J. R. Okajima
2011-01-19 6:43 ` vfs-scale, general questions (Re: NFS root lockups with -next 20110113) J. R. Okajima
2011-01-19 6:43 ` J. R. Okajima
2011-01-19 7:21 ` Nick Piggin
2011-01-19 7:21 ` Nick Piggin
2011-01-20 9:05 ` vfs-scale, general questions J. R. Okajima
2011-01-20 11:15 ` Miklos Szeredi
2011-01-21 6:38 ` J. R. Okajima
2011-02-11 3:49 ` vfs-scale, general questions (Re: NFS root lockups with -next 20110113) Ian Kent
2011-02-11 3:49 ` Ian Kent
2011-02-13 2:19 ` J. R. Okajima
2011-01-13 13:35 ` NFS root lockups with -next 20110113 Mark Brown
2011-01-13 13:35 ` Mark Brown
2011-01-13 13:35 ` Mark Brown
2011-01-13 13:41 ` Santosh Shilimkar
2011-01-13 13:41 ` Santosh Shilimkar
2011-01-13 13:41 ` Santosh Shilimkar
2011-01-13 13:41 ` Santosh Shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110113120626.GB30351@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=npiggin@kernel.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.