From: Fengguang Wu <fengguang.wu@intel.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Sasha Levin <levinsasha928@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>,
Kamal Mostafa <kamal@canonical.com>,
"Peter M. Petrakis" <peter.petrakis@canonical.com>,
Dann Frazier <dann.frazier@canonical.com>,
Massimo Morana <massimo.morana@canonical.com>,
Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: mq: INFO: possible circular locking dependency detected
Date: Wed, 8 Aug 2012 15:17:38 +0800 [thread overview]
Message-ID: <20120808071738.GA20090@localhost> (raw)
In-Reply-To: <20120807063955.GX23464@ZenIV.linux.org.uk>
On Tue, Aug 07, 2012 at 07:39:55AM +0100, Al Viro wrote:
> On Tue, Aug 07, 2012 at 01:04:12PM +0800, Fengguang Wu wrote:
>
> > FYI, here is a different back trace on that commit.
> >
> > [ 3.255043] ======================================================
> > [ 3.255052] [ INFO: possible circular locking dependency detected ]
> > [ 3.255052] 3.5.0-rc6-bisect-00355-geb04c28 #4 Not tainted
> > [ 3.255052] -------------------------------------------------------
> > [ 3.255052] init/1 is trying to acquire lock:
> > [ 3.255052] (&mm->mmap_sem){++++++}, at: [<ffffffff81180d00>] might_fault+0x70/0xe0
> > [ 3.255052]
> > [ 3.255052] but task is already holding lock:
> > [ 3.255052] (&sb->s_type->i_mutex_key){+.+.+.}, at: [<ffffffff811d191e>] vfs_readdir+0x6e/0x130
>
> Do you see any similar with the _next_ commit?
Stress tests show that the next commit is free from both the "circular
locking dependency" issues.
Thanks,
Fengguang
next prev parent reply other threads:[~2012-08-08 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 10:59 mq: INFO: possible circular locking dependency detected Sasha Levin
2012-08-05 17:08 ` Fengguang Wu
2012-08-07 5:04 ` Fengguang Wu
2012-08-07 6:39 ` Al Viro
2012-08-08 7:17 ` Fengguang Wu [this message]
2012-08-08 7:54 ` Fengguang Wu
2012-08-14 22:09 ` Jan Kara
2012-08-14 22:13 ` Al Viro
2012-08-14 22:29 ` Jan Kara
2012-08-06 6:34 ` Al Viro
2012-08-07 14:54 ` Sasha Levin
2012-08-08 8:50 ` Fengguang Wu
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=20120808071738.GA20090@localhost \
--to=fengguang.wu@intel.com \
--cc=dann.frazier@canonical.com \
--cc=davej@redhat.com \
--cc=jack@suse.cz \
--cc=kamal@canonical.com \
--cc=levinsasha928@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=massimo.morana@canonical.com \
--cc=peter.petrakis@canonical.com \
--cc=viro@ZenIV.linux.org.uk \
/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.