From: Dave Chinner <david@fromorbit.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: xfs@oss.sgi.com
Subject: Re: XFS locking issues in 3.18-rc3+
Date: Fri, 14 Nov 2014 16:25:23 +1100 [thread overview]
Message-ID: <20141114052523.GB29950@dastard> (raw)
In-Reply-To: <CALCETrWN71T1JsSNix52+ez_Sxt4i+vL-fX_2RTNbt8Ex1p=vw@mail.gmail.com>
On Thu, Nov 13, 2014 at 04:57:11PM -0800, Andy Lutomirski wrote:
> I'm running a kernel somewhere between 3.18-rc3 and 3.18-rc4. I got
> the warnings below. Is this a known issue?
Yup, false positive. shmem is instantiating an inode under the
mmap_sem and in doing so taking inode locks under the mmap_sem,
which triggers other filesystems to issue false warnings about
mmap_sem <-> inode lock order.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-11-14 5:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 0:57 XFS locking issues in 3.18-rc3+ Andy Lutomirski
2014-11-14 5:25 ` Dave Chinner [this message]
2014-11-14 21:02 ` Andy Lutomirski
2014-11-14 21:50 ` Dave Chinner
2014-11-14 22:05 ` Andy Lutomirski
2014-11-14 23:02 ` 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=20141114052523.GB29950@dastard \
--to=david@fromorbit.com \
--cc=luto@amacapital.net \
--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