From: Shaya Potter <spotter@cs.columbia.edu>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Christoph Hellwig <hch@lst.de>,
akpm@osdl.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] replace inode_update_time with file_update_time
Date: Mon, 07 Nov 2005 17:10:20 -0500 [thread overview]
Message-ID: <1131401420.8063.11.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0511072156340.13960@hermes-1.csi.cam.ac.uk>
On Mon, 2005-11-07 at 22:02 +0000, Anton Altaparmakov wrote:
> On Mon, 7 Nov 2005, Shaya Potter wrote:
> > On Mon, 2005-11-07 at 21:40 +0000, Anton Altaparmakov wrote:
> > > On Sat, 29 Oct 2005, Christoph Hellwig wrote:
> > > > To allow various options to work per-mount instead of per-sb we need
> > >
> > > What are those various options? Please spell them out. (I mean it! I
> > > really do not know what you have in mind and I cannot see anything that
> > > would require a vfs mount wrt cmtime updates.)
> >
> > I'm thinking you should think of things like read only bind mounts,
> > where even meta data wont be updated.
>
> But that is my point! A read-only bind mount is just like any other
> read-only mount and should never even try to update metadata.
there's no such thing as a read only bind mount right now, I believe
this is to enable support of such a thing, but I could be wrong.
next prev parent reply other threads:[~2005-11-07 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 16:52 [PATCH] replace inode_update_time with file_update_time Christoph Hellwig
2005-10-31 22:54 ` Andrew Morton
2005-10-31 22:57 ` Christoph Hellwig
2005-11-07 21:40 ` Anton Altaparmakov
2005-11-07 21:52 ` Shaya Potter
2005-11-07 22:02 ` Anton Altaparmakov
2005-11-07 22:10 ` Shaya Potter [this message]
2005-11-07 22:13 ` Anton Altaparmakov
2005-11-08 4:34 ` Christoph Hellwig
2005-11-08 9:52 ` Anton Altaparmakov
2005-11-08 4:30 ` Christoph Hellwig
2005-11-08 9:50 ` Anton Altaparmakov
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=1131401420.8063.11.camel@localhost.localdomain \
--to=spotter@cs.columbia.edu \
--cc=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).