From: Tilman Schmidt <tilman@imap.cc>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [2.6.20-rc3] INFO: possible recursive locking detected (was: Happy New Year (and v2.6.20-rc3 released))
Date: Wed, 3 Jan 2007 20:06:12 +0100 [thread overview]
Message-ID: <200701031906.l03J6Csc005559@lx1.pxnet.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612311710430.4473@woody.osdl.org>
On Sun, 31 Dec 2006 17:19:44 -0800 (PST), Linus Torvalds wrote:
> In order to not get in trouble with MADR ("Mothers Against Drunk
> Releases") I decided to cut the 2.6.20-rc3 release early rather than wait
[...]
> At which point the first thing on any self-respecting geek's mind should
> obviously be: "is there a new kernel release for me to try?"
2.6.20-rc3 produces the following lockdep warning when hald is
started during system startup:
=============================================
[ INFO: possible recursive locking detected ]
2.6.20-rc3-noinitrd #0
---------------------------------------------
hald-subfs-moun/4608 is trying to acquire lock:
(&inode->i_mutex){--..}, at: [<c035bb02>] mutex_lock+0x1c/0x1f
but task is already holding lock:
(&inode->i_mutex){--..}, at: [<c035bb02>] mutex_lock+0x1c/0x1f
other info that might help us debug this:
3 locks held by hald-subfs-moun/4608:
#0: (&inode->i_mutex){--..}, at: [<c035bb02>] mutex_lock+0x1c/0x1f
#1: (&REISERFS_I(inode)->xattr_sem){----}, at: [<c01c0098>] reiserfs_setxattr+0x51/0xe9
#2: (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<c01c00be>] reiserfs_setxattr+0x77/0xe9
stack backtrace:
[<c0103c72>] show_trace_log_lvl+0x19/0x2e
[<c0103d6b>] show_trace+0x12/0x14
[<c0103d81>] dump_stack+0x14/0x16
[<c01303b3>] __lock_acquire+0x116/0xa5c
[<c0130fe6>] lock_acquire+0x56/0x70
[<c035b95c>] __mutex_lock_slowpath+0xdc/0x266
[<c035bb02>] mutex_lock+0x1c/0x1f
[<c01c07d0>] reiserfs_xattr_set+0xe4/0x2c0
[<c01c0c21>] trusted_set+0x74/0x80
[<c01c00e9>] reiserfs_setxattr+0xa2/0xe9
[<c0177b45>] vfs_setxattr+0xa6/0x1ff
[<c0177d57>] setxattr+0xb9/0xd1
[<c0177e14>] sys_lsetxattr+0x3e/0x50
[<c0102d9a>] sysenter_past_esp+0x5f/0x99
=======================
I guess it's really the same ReiserFS issue I already reported for
the previous releases, just triggered at an earlier point in the
system's life.
Other than that, everything seems fine and dandy on this plain old P3.
HTH, and Happy New Year everyone
Tilman
next prev parent reply other threads:[~2007-01-03 19:06 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 1:19 Happy New Year (and v2.6.20-rc3 released) Linus Torvalds
2007-01-01 1:39 ` Gene Heskett
2007-01-01 2:40 ` Alexey Dobriyan
2007-01-01 7:22 ` Cyrill V. Gorcnov
[not found] ` <4598BC0F.6070003@vc.cvut.cz>
2007-01-01 9:41 ` Cyrill V. Gorcnov
2007-01-02 2:19 ` H. Peter Anvin
2007-01-01 11:29 ` Arkadiusz Miskiewicz
2007-01-01 13:28 ` Alessandro Suardi
2007-01-01 20:13 ` Linus Torvalds
2007-01-01 20:49 ` Jeff Garzik
2007-01-01 21:31 ` Alan
2007-01-01 23:34 ` Linus Torvalds
2007-01-02 2:32 ` Theodore Tso
2007-01-02 11:58 ` [PATCH] libata: fix combined mode (was Re: Happy New Year (and v2.6.20-rc3 released)) Alan
2007-01-02 12:07 ` Alessandro Suardi
2007-01-02 14:00 ` Alan
2007-01-02 16:12 ` Theodore Tso
2007-01-02 21:00 ` Jeff Garzik
2007-01-02 21:27 ` Alan
2007-01-02 21:29 ` Jeff Garzik
2007-01-02 21:32 ` Jeff Garzik
2007-01-02 22:48 ` Alan
2007-01-02 22:45 ` Alan
2007-01-02 23:01 ` Jeff Garzik
2007-01-02 23:27 ` Alan
2007-01-02 23:43 ` Jeff Garzik
2007-01-03 0:36 ` Alan
2007-01-03 1:02 ` Jeff Garzik
2007-01-02 23:54 ` Jeff Garzik
2007-01-03 0:39 ` Alan
2007-01-02 23:04 ` Jeff Garzik
2007-01-03 19:59 ` Steve Wise
2007-01-01 21:26 ` Happy New Year (and v2.6.20-rc3 released) Alan
2007-01-02 16:09 ` Linus Torvalds
2007-01-01 15:52 ` Olaf Hering
2007-01-02 19:16 ` 2.6.20-rc3: known unfixed regressions Adrian Bunk
2007-01-03 18:15 ` Steve Youngs
2007-01-03 20:03 ` Adrian Bunk
2007-01-02 19:24 ` 2.6.20-rc3: known regressions with patches available (part 1) Adrian Bunk
2007-01-02 19:26 ` Jens Axboe
2007-01-02 19:34 ` Adrian Bunk
2007-01-02 20:45 ` Rene Herman
2007-01-02 20:51 ` Jens Axboe
2007-01-02 19:30 ` 2.6.20-rc3: known regressions with patches available (part 2) Adrian Bunk
2007-01-03 19:06 ` Tilman Schmidt [this message]
2007-01-03 20:59 ` 2.6.20-rc3: known unfixed regressions (v2) Adrian Bunk
2007-01-04 13:23 ` Horst H. von Brand
2007-01-03 21:04 ` 2.6.20-rc3: known regressions with patches (v2) Adrian Bunk
2007-01-03 21:30 ` Jiri Kosina
2007-01-03 21:32 ` Jiri Kosina
2007-01-04 17:46 ` 2.6.20-rc3: known unfixed regressions (v3) Adrian Bunk
2007-01-04 18:13 ` Matthew Wilcox
2007-01-05 0:25 ` Horst H. von Brand
2007-01-06 21:04 ` 2.6.20-rc3: known unfixed regressions (v4) Adrian Bunk
2007-01-06 22:06 ` Brice Goglin
2007-01-07 23:49 ` Adrian Bunk
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=200701031906.l03J6Csc005559@lx1.pxnet.com \
--to=tilman@imap.cc \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®