| To: | Gu Zheng <guz.fnst@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs: possible deadlock warning |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Wed, 28 May 2014 16:00:50 +1000 |
| Cc: | xfs@xxxxxxxxxxx, linux-kernel <linux-kernel@xxxxxxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <538571D4.70904@xxxxxxxxxxxxxx> |
| References: | <538571D4.70904@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 0/2, RFC] xfsprogs: try to handle mkfs of a file on 4k sector device, Christoph Hellwig |
|---|---|
| Next by Date: | [PATCH 04/16] xfs: convert dir byte/off conversion to xfs_da_geometry, Dave Chinner |
| Previous by Thread: | xfs: possible deadlock warning, Gu Zheng |
| Next by Thread: | Re: xfs: possible deadlock warning, Gu Zheng |
| Indexes: | [Date] [Thread] [Top] [All Lists] |