| To: | Andy Lutomirski <luto@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS locking issues in 3.18-rc3+ |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Fri, 14 Nov 2014 16:25:23 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CALCETrWN71T1JsSNix52+ez_Sxt4i+vL-fX_2RTNbt8Ex1p=vw@xxxxxxxxxxxxxx> |
| References: | <CALCETrWN71T1JsSNix52+ez_Sxt4i+vL-fX_2RTNbt8Ex1p=vw@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Mismatch of UUIDS on raid 5, Robert Tench |
|---|---|
| Next by Date: | Go Computerized with your Calls and Get More Attention, Virtual Number |
| Previous by Thread: | XFS locking issues in 3.18-rc3+, Andy Lutomirski |
| Next by Thread: | Re: XFS locking issues in 3.18-rc3+, Andy Lutomirski |
| Indexes: | [Date] [Thread] [Top] [All Lists] |