* Re: xfs mr_lock vs mmap_sem lock inversion?
[not found] <1247580955.7500.97.camel@twins>
@ 2009-07-17 15:09 ` Christoph Hellwig
0 siblings, 0 replies; only message in thread
From: Christoph Hellwig @ 2009-07-17 15:09 UTC (permalink / raw)
To: Peter Zijlstra; +Cc: Christoph Hellwig, linux-kernel, linux-mm
It's a problem in the VM code, which we already discussed a while
ago. The problem is that the VMA manipultation code calls fput
under the mmap_sem, while we can take mmap_sem ue to a page fault
from inside generic_file_aio_read/write. So any filesystem
that nees the same lock held over read/write also in release is
crewed.
Now on the positive side I think we can actually get rid of taking
the iolock in ->release in XFS, but I'm sure other filesystems
might continue hitting similar issues.
--
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>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-07-17 15:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1247580955.7500.97.camel@twins>
2009-07-17 15:09 ` xfs mr_lock vs mmap_sem lock inversion? Christoph Hellwig
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).