From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-mm@kvack.org
Subject: fput under mmap_sem
Date: Wed, 18 Mar 2009 03:13:13 -0400 [thread overview]
Message-ID: <20090318071313.GA30011@infradead.org> (raw)
In-Reply-To: <20090315221921.GY26138@disturbed>
On Mon, Mar 16, 2009 at 09:19:21AM +1100, Dave Chinner wrote:
> This is a VM problem where it calls fput() with the mmap_sem() held
> in remove_vma(). It makes the incorrect assumption that filesystems
> will never use the same lock in the IO path and the inode release path.
>
> This can deadlock if you are really unlucky.
I really wonder why other filesystems haven't hit this yet. Any chance
we can get the fput moved out of mmap_sem to get rid of this class of
problems?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2009-03-18 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903151459.01320.denys@visp.net.lb>
[not found] ` <20090315221921.GY26138@disturbed>
2009-03-18 7:13 ` Christoph Hellwig [this message]
2009-03-18 12:37 ` Nick Piggin
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=20090318071313.GA30011@infradead.org \
--to=hch@infradead.org \
--cc=linux-mm@kvack.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