From: Dave Jones <davej@redhat.com>
To: Josh Boyer <jboyer@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: hugetlbfs lockdep spew revisited.
Date: Thu, 16 Feb 2012 19:08:57 -0500 [thread overview]
Message-ID: <20120217000856.GA13112@redhat.com> (raw)
Remember this ? https://lkml.org/lkml/2011/4/15/272
Josh took a stab at fixing it in e096d0c7e2e4e5893792db865dd065ac73cf1f00,
but it seems to still be there.
Dave
======================================================
[ INFO: possible circular locking dependency detected ]
3.3.0-rc3+ #2 Not tainted
-------------------------------------------------------
trinity/30663 is trying to acquire lock:
(&sb->s_type->i_mutex_key#18){+.+...}, at: [<ffffffff81298169>] hugetlbfs_file_mmap+0x89/0x140
but task is already holding lock:
(&mm->mmap_sem){++++++}, at: [<ffffffff81182d97>] sys_mmap_pgoff+0x1d7/0x230
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&mm->mmap_sem){++++++}:
[<ffffffff810d073d>] lock_acquire+0x9d/0x220
[<ffffffff811789c0>] might_fault+0x80/0xb0
[<ffffffff811d2997>] filldir+0x77/0xe0
[<ffffffff811e61ae>] dcache_readdir+0x5e/0x220
[<ffffffff811d2c68>] vfs_readdir+0xb8/0xf0
[<ffffffff811d2d99>] sys_getdents+0x89/0x100
[<ffffffff816a5b69>] system_call_fastpath+0x16/0x1b
-> #0 (&sb->s_type->i_mutex_key#18){+.+...}:
[<ffffffff810d0008>] __lock_acquire+0x1bf8/0x1c20
[<ffffffff810d073d>] lock_acquire+0x9d/0x220
[<ffffffff8169a5b9>] __mutex_lock_common+0x59/0x500
[<ffffffff8169ab94>] mutex_lock_nested+0x44/0x50
[<ffffffff81298169>] hugetlbfs_file_mmap+0x89/0x140
[<ffffffff811826a9>] mmap_region+0x369/0x4f0
[<ffffffff81182b9f>] do_mmap_pgoff+0x36f/0x390
[<ffffffff81182db7>] sys_mmap_pgoff+0x1f7/0x230
[<ffffffff8101eda2>] sys_mmap+0x22/0x30
[<ffffffff816a5b69>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&mm->mmap_sem);
lock(&sb->s_type->i_mutex_key#18);
lock(&mm->mmap_sem);
lock(&sb->s_type->i_mutex_key#18);
*** DEADLOCK ***
1 lock held by trinity/30663:
#0: (&mm->mmap_sem){++++++}, at: [<ffffffff81182d97>] sys_mmap_pgoff+0x1d7/0x230
stack backtrace:
Pid: 30663, comm: trinity Not tainted 3.3.0-rc3+ #2
Call Trace:
[<ffffffff816924d7>] print_circular_bug+0x1fb/0x20c
[<ffffffff810d0008>] __lock_acquire+0x1bf8/0x1c20
[<ffffffff816a1c2d>] ? sub_preempt_count+0x9d/0xd0
[<ffffffff811a40cc>] ? deactivate_slab+0x54c/0x5f0
[<ffffffff810d073d>] lock_acquire+0x9d/0x220
[<ffffffff81298169>] ? hugetlbfs_file_mmap+0x89/0x140
[<ffffffff810d12fd>] ? trace_hardirqs_on_caller+0x10d/0x1a0
[<ffffffff8169a5b9>] __mutex_lock_common+0x59/0x500
[<ffffffff81298169>] ? hugetlbfs_file_mmap+0x89/0x140
[<ffffffff811825e5>] ? mmap_region+0x2a5/0x4f0
[<ffffffff81298169>] ? hugetlbfs_file_mmap+0x89/0x140
[<ffffffff8169ab94>] mutex_lock_nested+0x44/0x50
[<ffffffff81298169>] hugetlbfs_file_mmap+0x89/0x140
[<ffffffff811826a9>] mmap_region+0x369/0x4f0
[<ffffffff812c1e9a>] ? file_map_prot_check+0xaa/0xe0
[<ffffffff81182b9f>] do_mmap_pgoff+0x36f/0x390
[<ffffffff81182d97>] ? sys_mmap_pgoff+0x1d7/0x230
[<ffffffff81182db7>] sys_mmap_pgoff+0x1f7/0x230
[<ffffffff810d12fd>] ? trace_hardirqs_on_caller+0x10d/0x1a0
[<ffffffff8101eda2>] sys_mmap+0x22/0x30
[<ffffffff816a5b69>] system_call_fastpath+0x16/0x1b
next reply other threads:[~2012-02-17 0:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 0:08 Dave Jones [this message]
2012-02-17 0:16 ` hugetlbfs lockdep spew revisited Josh Boyer
2012-02-17 0:34 ` Al Viro
2012-02-17 0:38 ` Tyler Hicks
2012-02-17 0:49 ` Al Viro
2012-02-17 3:42 ` Tyler Hicks
2012-02-21 18:21 ` Mimi Zohar
2012-02-17 6:47 ` J. R. Okajima
2012-02-17 17:48 ` udf deadlock (was Re: hugetlbfs lockdep spew revisited.) Al Viro
2012-02-20 16:01 ` Jan Kara
2012-02-18 10:55 ` hugetlbfs lockdep spew revisited Aneesh Kumar K.V
2012-02-17 0:27 ` Al Viro
2012-02-23 9:27 ` Aneesh Kumar K.V
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=20120217000856.GA13112@redhat.com \
--to=davej@redhat.com \
--cc=jboyer@redhat.com \
--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 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.