From: Frederic Weisbecker <fweisbec@gmail.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: linux-next <linux-next@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: 20090529: sysfs/reiserfs: possible circular locking dependency
Date: Sat, 30 May 2009 21:45:04 +0200 [thread overview]
Message-ID: <20090530194502.GB8739@nowhere> (raw)
In-Reply-To: <a4423d670905300833v7ed43bd1p22de438bbc4e69ac@mail.gmail.com>
On Sat, May 30, 2009 at 07:33:03PM +0400, Alexander Beregalov wrote:
> Hi
>
> Here is a boot process.
>
> udev: starting version 141
> [ INFO: possible circular locking dependency detected ]
> 2.6.30-rc7-next-20090529-06589-g7701864 #6
> -------------------------------------------------------
> udevadm/708 is trying to acquire lock:
> (&mm->mmap_sem){++++++}, at: [<c0175962>] might_fault+0x52/0xa0
>
> but task is already holding lock:
> (sysfs_mutex){+.+.+.}, at: [<c01d05e6>] sysfs_readdir+0x56/0x200
>
> which lock already depends on the new lock.
>
>
> the existing dependency chain (in reverse order) is:
>
> -> #3 (sysfs_mutex){+.+.+.}:
>
> -> #2 (&bdev->bd_mutex){+.+.+.}:
>
> -> #1 (&REISERFS_SB(s)->lock){+.+.+.}:
>
> -> #0 (&mm->mmap_sem){++++++}:
I don't understand how it is possible to get the sysfs_mutex
from reiserfs code...
And lockdep backtraces are not very clear...
> other info that might help us debug this:
>
> 2 locks held by udevadm/708:
> #0: (&type->i_mutex_dir_key){+.+.+.}, at: [<c0199c7f>] vfs_readdir+0x4f/0xa0
> #1: (sysfs_mutex){+.+.+.}, at: [<c01d05e6>] sysfs_readdir+0x56/0x200
>
> stack backtrace:
> Pid: 708, comm: udevadm Not tainted 2.6.30-rc7-next-20090529-06589-g7701864 #6
> Call Trace:
> [<c044e812>] ? printk+0x18/0x1e
> [<c014e53c>] print_circular_bug_tail+0x8c/0xe0
> [<c014ce8b>] ? print_circular_bug_entry+0x4b/0x50
> [<c015048e>] __lock_acquire+0xd7e/0x10b0
> [<c0175962>] ? might_fault+0x52/0xa0
> [<c0150834>] lock_acquire+0x74/0x90
> [<c0175962>] ? might_fault+0x52/0xa0
> [<c0175993>] might_fault+0x83/0xa0
> [<c0175962>] ? might_fault+0x52/0xa0
> [<c02cef26>] copy_to_user+0x36/0x130
> [<c0199a34>] filldir64+0xa4/0xf0
> [<c01d06a6>] sysfs_readdir+0x116/0x200
> [<c0199990>] ? filldir64+0x0/0xf0
> [<c0199cae>] vfs_readdir+0x7e/0xa0
> [<c0199990>] ? filldir64+0x0/0xf0
> [<c0199d39>] sys_getdents64+0x69/0xb0
> [<c0102e48>] sysenter_do_call+0x12/0x36
prev parent reply other threads:[~2009-05-30 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 15:33 20090529: sysfs/reiserfs: possible circular locking dependency Alexander Beregalov
2009-05-30 15:56 ` Greg KH
2009-05-30 16:14 ` Frederic Weisbecker
2009-05-30 19:45 ` Frederic Weisbecker [this message]
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=20090530194502.GB8739@nowhere \
--to=fweisbec@gmail.com \
--cc=a.beregalov@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-next@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 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.