From: Dave Chinner <david@fromorbit.com>
To: Gu Zheng <guz.fnst@cn.fujitsu.com>
Cc: xfs@oss.sgi.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: xfs: possible deadlock warning
Date: Wed, 28 May 2014 16:00:50 +1000 [thread overview]
Message-ID: <20140528060050.GK8554@dastard> (raw)
In-Reply-To: <538571D4.70904@cn.fujitsu.com>
On Wed, May 28, 2014 at 01:19:16PM +0800, Gu Zheng wrote:
> Hi all,
> When running the latest Linus' tree, the following possible deadlock warning occurs.
false positive. There isn't a deadlock between inode locks on
different filesystems. i.e. there is no dependency between shmem
inodes and xfs inodes, nor on their security contexts. Nor can you
take a page fault on a directory inode, which is the XFS inode lock
class it's complaining about.
Fundamentally, the problem here is shmem instantiating a new inode
with the mmap_sem held. That's just plain wrong...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-05-28 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 5:19 xfs: possible deadlock warning Gu Zheng
2014-05-28 6:00 ` Dave Chinner [this message]
2014-05-29 3:34 ` Gu Zheng
2014-05-29 7:49 ` Dave Chinner
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=20140528060050.GK8554@dastard \
--to=david@fromorbit.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).