From: Valerie Aurora <vaurora@redhat.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, Jan Blunck <jblunck@suse.de>,
Christoph Hellwig <hch@infradead.org>
Subject: Need i_mutex on lookup in a really really read-only fs?
Date: Sat, 10 Oct 2009 21:06:54 -0400 [thread overview]
Message-ID: <20091011010654.GA12667@shell> (raw)
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/
reply other threads:[~2009-10-11 1:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091011010654.GA12667@shell \
--to=vaurora@redhat.com \
--cc=hch@infradead.org \
--cc=jblunck@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.