From: Frederic Weisbecker <fweisbec@gmail.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Reiserfs <reiserfs-devel@vger.kernel.org>
Subject: Re: [PATCH 0/4] kill-the-bkl/reiserfs: fix some lock dependency inversions
Date: Mon, 14 Sep 2009 22:37:51 +0200 [thread overview]
Message-ID: <20090914203749.GF6045@nowhere> (raw)
In-Reply-To: <20090826201330.GA18761@orion>
On Thu, Aug 27, 2009 at 12:13:30AM +0400, Alexander Beregalov wrote:
> Hi,
> possible circular locking dependency detected
>
> Is it false positive?
>
> REISERFS (device sda1): found reiserfs format "3.6" with standard journal
> REISERFS (device sda1): using ordered data mode
> REISERFS (device sda1): journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
> REISERFS (device sda1): checking transaction log (sda1)
> REISERFS debug (device sda1): journal-1153: found in header: first_unflushed_offset 6766, last_flushed_trans_id 1836992
> REISERFS debug (device sda1): journal-1206: Starting replay from offset 7889824857987694, trans_id 18
> REISERFS debug (device sda1): journal-1299: Setting newest_mount_id to 229
> REISERFS (device sda1): Using r5 hash to sort names
> VFS: Mounted root (reiserfs filesystem) readonly on device 8:1.
>
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> 2.6.31-rc7-00135-g9399a4c #5
> -------------------------------------------------------
> init.sh/599 is trying to acquire lock:
> (&mm->mmap_sem){++++++}, at: [<c1071056>] might_fault+0x46/0xa0
>
> but task is already holding lock:
> (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c10ff20e>] reiserfs_write_lock+0x1e/0x30
>
> which lock already depends on the new lock.
>
>
> the existing dependency chain (in reverse order) is:
>
> -> #1 (&REISERFS_SB(s)->lock){+.+.+.}:
> [<c104dd18>] __lock_acquire+0xd28/0x1390
> [<c104e3ef>] lock_acquire+0x6f/0x90
> [<c133af96>] __mutex_lock_common+0x46/0x310
> [<c133b318>] mutex_lock_nested+0x38/0x40
> [<c10ff1ce>] reiserfs_write_lock_once+0x1e/0x40
> [<c10db74c>] reiserfs_get_block+0x5c/0x1440
> [<c10ae7a0>] do_mpage_readpage+0x120/0x4b0
> [<c10aec2f>] mpage_readpages+0x9f/0xe0
> [<c10d8c39>] reiserfs_readpages+0x19/0x20
> [<c10671f5>] __do_page_cache_readahead+0x195/0x210
> [<c1067291>] ra_submit+0x21/0x30
> [<c1061229>] filemap_fault+0x2e9/0x380
> [<c1072f08>] __do_fault+0x38/0x3b0
> [<c1073b5d>] handle_mm_fault+0xcd/0x550
> [<c101ad63>] do_page_fault+0xf3/0x240
> [<c133cd53>] error_code+0x63/0x68
> [<c10baa74>] padzero+0x24/0x40
> [<c10bc062>] load_elf_binary+0x632/0x1480
> [<c108aafa>] search_binary_handler+0x8a/0x270
> [<c108cb15>] do_execve+0x215/0x2a0
> [<c1001658>] sys_execve+0x28/0x60
> [<c1002d99>] syscall_call+0x7/0xb
> [<ffffffff>] 0xffffffff
>
> -> #0 (&mm->mmap_sem){++++++}:
> [<c104dd99>] __lock_acquire+0xda9/0x1390
> [<c104e3ef>] lock_acquire+0x6f/0x90
> [<c1071087>] might_fault+0x77/0xa0
> [<c11c1886>] copy_to_user+0x36/0x130
> [<c1093c29>] filldir64+0xa9/0xf0
> [<c10deda1>] reiserfs_readdir_dentry+0x4a1/0x7b0
> [<c10df0c7>] reiserfs_readdir+0x17/0x20
> [<c1093eb5>] vfs_readdir+0x85/0xa0
> [<c1093f34>] sys_getdents64+0x64/0xb0
> [<c1002d18>] sysenter_do_call+0x12/0x36
> [<ffffffff>] 0xffffffff
>
> other info that might help us debug this:
>
> 2 locks held by init.sh/599:
> #0: (&sb->s_type->i_mutex_key#4){+.+.+.}, at: [<c1093e82>] vfs_readdir+0x52/0xa0
> #1: (&REISERFS_SB(s)->lock){+.+.+.}, at: [<c10ff20e>] reiserfs_write_lock+0x1e/0x30
>
> stack backtrace:
> Pid: 599, comm: init.sh Not tainted 2.6.31-rc7-00135-g9399a4c #5
> Call Trace:
> [<c133a11a>] ? printk+0x18/0x1e
> [<c104bfdd>] print_circular_bug_tail+0x8d/0xd0
> [<c104dd99>] __lock_acquire+0xda9/0x1390
> [<c104e3ef>] lock_acquire+0x6f/0x90
> [<c1071056>] ? might_fault+0x46/0xa0
> [<c1071087>] might_fault+0x77/0xa0
> [<c1071056>] ? might_fault+0x46/0xa0
> [<c11c1886>] copy_to_user+0x36/0x130
> [<c1093c29>] filldir64+0xa9/0xf0
> [<c10ff20e>] ? reiserfs_write_lock+0x1e/0x30
> [<c10deda1>] reiserfs_readdir_dentry+0x4a1/0x7b0
> [<c1093b80>] ? filldir64+0x0/0xf0
> [<c104d453>] ? __lock_acquire+0x463/0x1390
> [<c104c62e>] ? trace_hardirqs_on_caller+0x7e/0x170
> [<c1093b80>] ? filldir64+0x0/0xf0
> [<c133b153>] ? __mutex_lock_common+0x203/0x310
> [<c1093b80>] ? filldir64+0x0/0xf0
> [<c10df0c7>] reiserfs_readdir+0x17/0x20
> [<c1093eb5>] vfs_readdir+0x85/0xa0
> [<c1093f34>] sys_getdents64+0x64/0xb0
> [<c1002d18>] sysenter_do_call+0x12/0x36
Hi Alexander,
It should be fixed now, still in the following tree:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
reiserfs/kill-bkl
Don't hesistate to tell me if you see other problems.
Thanks a lot for your report!
Frederic.
next prev parent reply other threads:[~2009-09-14 20:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 2:32 [PATCH 0/4] kill-the-bkl/reiserfs: fix some lock dependency inversions Frederic Weisbecker
2009-08-25 2:32 ` [PATCH 1/4] kill-the-bkl/reiserfs: fix "reiserfs lock" / "inode mutex" lock inversion dependency Frederic Weisbecker
2009-08-25 2:32 ` [PATCH 2/4] kill-the-bkl/reiserfs: fix recursive reiserfs lock in reiserfs_mkdir() Frederic Weisbecker
2009-08-25 2:32 ` [PATCH 3/4] kill-the-bkl/reiserfs: fix recursive reiserfs write lock in reiserfs_commit_write() Frederic Weisbecker
2009-08-25 2:32 ` [PATCH 4/4] kill-the-bkl/reiserfs: panic in case of lock imbalance Frederic Weisbecker
2009-08-26 20:13 ` [PATCH 0/4] kill-the-bkl/reiserfs: fix some lock dependency inversions Alexander Beregalov
2009-09-01 22:16 ` Frederic Weisbecker
2009-09-14 20:37 ` Frederic Weisbecker [this message]
2009-09-14 21:33 ` Alexander Beregalov
2009-09-14 21:50 ` Frederic Weisbecker
2009-09-16 20:37 ` Frederic Weisbecker
2009-09-16 23:37 ` Alexander Beregalov
2009-09-16 23:37 ` Alexander Beregalov
2009-09-17 5:06 ` [PATCH] kill-the-bkl/reiserfs: Fix induced mm->mmap_sem to sysfs_mutex dependency Frederic Weisbecker
2009-09-22 13:55 ` Alexander Beregalov
2009-09-29 7:46 ` Frederic Weisbecker
2009-09-29 10:22 ` Alexander Beregalov
2009-09-29 10:22 ` Alexander Beregalov
2009-10-05 18:12 ` [PATCH] kill-the-bkl/reiserfs: fix reiserfs lock to cpu_add_remove_lock dependency Frederic Weisbecker
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=20090914203749.GF6045@nowhere \
--to=fweisbec@gmail.com \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@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.