From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Andrew Morton <akpm@linux-foundation.org>, Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: lockdep wierdness...
Date: Mon, 24 Sep 2007 18:07:38 -0400 [thread overview]
Message-ID: <1190671658.6700.31.camel@heimdal.trondhjem.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 298 bytes --]
I'm seeing lockdep warning about a potential lock inversion between
&mm->mmap_sem and &inode->i_mutex in NFS (see attachment).
Unfortunately the basis for the warning appears to be the behaviour in
ext3(???). AFAICS there is no way for NFS to share an inode->i_mutex
with ext3. What to do?
Trond
[-- Attachment #2: Type: text/plain, Size: 2363 bytes --]
=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.23-rc7-g8809e921 #1
-------------------------------------------------------
beagle-build-in/24375 is trying to acquire lock:
(&mm->mmap_sem){----}, at: [<c05a2887>] do_page_fault+0x17d/0x591
but task is already holding lock:
(&inode->i_mutex){--..}, at: [<c059f9e3>] mutex_lock+0x1c/0x1f
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&inode->i_mutex){--..}:
[<c043d4da>] __lock_acquire+0x9f3/0xba6
[<c043da62>] lock_acquire+0x5f/0x78
[<c059f832>] __mutex_lock_slowpath+0xe5/0x27a
[<c059f9e3>] mutex_lock+0x1c/0x1f
[<f8c92495>] nfs_revalidate_mapping+0x64/0x9c [nfs]
[<f8c8ff2a>] nfs_file_mmap+0x46/0x75 [nfs]
[<c046097c>] mmap_region+0x1ea/0x3b8
[<c0460e9b>] do_mmap_pgoff+0x27b/0x2da
[<c0407d77>] sys_mmap2+0x9b/0xb5
[<c040405e>] sysenter_past_esp+0x5f/0x99
[<ffffffff>] 0xffffffff
-> #0 (&mm->mmap_sem){----}:
[<c043d3c6>] __lock_acquire+0x8df/0xba6
[<c043da62>] lock_acquire+0x5f/0x78
[<c04360db>] down_read+0x3a/0x4c
[<c05a2887>] do_page_fault+0x17d/0x591
[<c05a1382>] error_code+0x72/0x78
[<f88acaac>] call_filldir+0xac/0xc3 [ext3]
[<f88acdb2>] ext3_readdir+0x217/0x5e5 [ext3]
[<c04798a1>] vfs_readdir+0x67/0x93
[<c0479af6>] sys_getdents+0x5f/0x9d
[<c040405e>] sysenter_past_esp+0x5f/0x99
[<ffffffff>] 0xffffffff
other info that might help us debug this:
1 lock held by beagle-build-in/24375:
#0: (&inode->i_mutex){--..}, at: [<c059f9e3>] mutex_lock+0x1c/0x1f
stack backtrace:
[<c04050ee>] show_trace_log_lvl+0x1a/0x2f
[<c0405b58>] show_trace+0x12/0x14
[<c0405b70>] dump_stack+0x16/0x18
[<c043bc05>] print_circular_bug_tail+0x5f/0x68
[<c043d3c6>] __lock_acquire+0x8df/0xba6
[<c043da62>] lock_acquire+0x5f/0x78
[<c04360db>] down_read+0x3a/0x4c
[<c05a2887>] do_page_fault+0x17d/0x591
[<c05a1382>] error_code+0x72/0x78
[<f88acaac>] call_filldir+0xac/0xc3 [ext3]
[<f88acdb2>] ext3_readdir+0x217/0x5e5 [ext3]
[<c04798a1>] vfs_readdir+0x67/0x93
[<c0479af6>] sys_getdents+0x5f/0x9d
[<c040405e>] sysenter_past_esp+0x5f/0x99
=======================
next reply other threads:[~2007-09-24 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 22:07 Trond Myklebust [this message]
2007-09-25 2:13 ` Steven Rostedt
2007-09-27 13:51 ` Peter Zijlstra
2007-09-27 14:00 ` Christoph Hellwig
2007-09-27 15:58 ` Peter Zijlstra
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=1190671658.6700.31.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®