From: Nick Bowler <nbowler@elliptictech.com>
To: linux-kernel@vger.kernel.org, autofs@linux.kernel.org
Cc: Ian Kent <raven@themaw.net>
Subject: Lockdep splat in autofs with 2.6.39-rc2
Date: Thu, 7 Apr 2011 15:44:03 -0400 [thread overview]
Message-ID: <20110407194403.GA29404@elliptictech.com> (raw)
Just saw this on 2.6.39-rc2 after half a day or so of uptime. I've
never seen it before today so it may be a regression from 2.6.38.
Nothing seems have failed as a result. Please let me know if you
need any more info.
=============================================
[ INFO: possible recursive locking detected ]
2.6.39-rc2 #177
---------------------------------------------
automount/23324 is trying to acquire lock:
(&(&dentry->d_lock)->rlock/1){+.+...}, at: [<ffffffffa034ea28>] autofs4_expire_indirect+0x307/0x484 [autofs4]
but task is already holding lock:
(&(&dentry->d_lock)->rlock/1){+.+...}, at: [<ffffffffa034ea28>] autofs4_expire_indirect+0x307/0x484 [autofs4]
other info that might help us debug this:
2 locks held by automount/23324:
#0: (&(&sbi->lookup_lock)->rlock){+.+...}, at: [<ffffffffa034e9aa>] autofs4_expire_indirect+0x289/0x484 [autofs4]
#1: (&(&dentry->d_lock)->rlock/1){+.+...}, at: [<ffffffffa034ea28>] autofs4_expire_indirect+0x307/0x484 [autofs4]
stack backtrace:
Pid: 23324, comm: automount Not tainted 2.6.39-rc2 #177
Call Trace:
[<ffffffff81061dc7>] __lock_acquire+0xc83/0xcfa
[<ffffffff8105f200>] ? static_obj+0x3d/0x4d
[<ffffffff81062073>] ? lock_release_non_nested+0x1c8/0x227
[<ffffffffa034ea28>] ? autofs4_expire_indirect+0x307/0x484 [autofs4]
[<ffffffffa034ea28>] ? autofs4_expire_indirect+0x307/0x484 [autofs4]
[<ffffffff81061e95>] lock_acquire+0x57/0x6d
[<ffffffffa034ea28>] ? autofs4_expire_indirect+0x307/0x484 [autofs4]
[<ffffffff8131f4e3>] _raw_spin_lock_nested+0x39/0x48
[<ffffffffa034ea28>] ? autofs4_expire_indirect+0x307/0x484 [autofs4]
[<ffffffff8131fb10>] ? _raw_spin_unlock+0x3e/0x4b
[<ffffffffa034ea28>] autofs4_expire_indirect+0x307/0x484 [autofs4]
[<ffffffffa034f184>] ? autofs_dev_ioctl_askumount+0x2d/0x2d [autofs4]
[<ffffffffa034edbd>] autofs4_do_expire_multi+0x30/0xe9 [autofs4]
[<ffffffffa034f184>] ? autofs_dev_ioctl_askumount+0x2d/0x2d [autofs4]
[<ffffffffa034f184>] ? autofs_dev_ioctl_askumount+0x2d/0x2d [autofs4]
[<ffffffffa034f19e>] autofs_dev_ioctl_expire+0x1a/0x1c [autofs4]
[<ffffffffa034f738>] _autofs_dev_ioctl+0x2a3/0x348 [autofs4]
[<ffffffffa034f7eb>] autofs_dev_ioctl+0xe/0x12 [autofs4]
[<ffffffff810c750d>] do_vfs_ioctl+0x45f/0x4ae
[<ffffffff810bab4e>] ? rcu_read_unlock+0x21/0x23
[<ffffffff810c759e>] sys_ioctl+0x42/0x65
[<ffffffff8132463b>] system_call_fastpath+0x16/0x1b
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next reply other threads:[~2011-04-07 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 19:44 Nick Bowler [this message]
2011-04-13 19:26 ` Lockdep splat in autofs with 2.6.39-rc2 Maciej Rutecki
2011-04-13 19:43 ` Nick Bowler
2011-04-14 19:38 ` Maciej Rutecki
2011-04-14 19:38 ` Maciej Rutecki
2011-04-21 21:25 ` Steven Rostedt
2011-04-27 13:22 ` Nick Bowler
2011-05-11 19:13 ` Nick Bowler
2011-06-14 0:43 ` Steven Rostedt
2011-06-20 14:48 ` Nick Bowler
2011-07-25 2:46 ` [autofs] " Ian Kent
2011-07-25 12:33 ` Steven Rostedt
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=20110407194403.GA29404@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=autofs@linux.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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.