* Need i_mutex on lookup in a really really read-only fs?
@ 2009-10-11 1:06 Valerie Aurora
0 siblings, 0 replies; only message in thread
From: Valerie Aurora @ 2009-10-11 1:06 UTC (permalink / raw)
To: Alexander Viro; +Cc: linux-fsdevel, Jan Blunck, Christoph Hellwig
Hey all,
Given a file system that is mounted really really read-only[1], do we
still need the directory i_mutex when doing a lookup through a
writable overlay/union mount? If not, we can probably union together
several read-only file systems underneath a writable layer without any
lock ordering problems.
Even with only one read-only layer, getting rid of the i_mutex during
lookup would simplify the locking strategy significantly.
Writable overlay/union mounts doc here:
http://lkml.org/lkml/2009/10/1/291
-VAL
[1] VFS: Add read-only users count to superblock
http://lwn.net/Articles/341129/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-10-11 1:07 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-11 1:06 Need i_mutex on lookup in a really really read-only fs? Valerie Aurora
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).