From: Christoph Hellwig <hch@lst.de>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Shaya Potter <spotter@cs.columbia.edu>,
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: Tue, 8 Nov 2005 05:34:12 +0100 [thread overview]
Message-ID: <20051108043412.GB8531@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0511072156340.13960@hermes-1.csi.cam.ac.uk>
On Mon, Nov 07, 2005 at 10:02:01PM +0000, Anton Altaparmakov wrote:
> 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.
>
> Which codepaths cause inode/file_update_time() to be called for a
> read-only mount?
The callers right now are the write methods of the various filesystems,
so you are right indeed that we shouldn't need it.
> I do not believe there are any!
>
> And assuming that I am correct this makes the IS_RDONLY() check
> pointless and this in turn makes the whole patch pointless
Yes, I think you're right here that we can removed it.
> and given it
> breaks existing file systems it should be sent to the nirvana of useless
> patches.
and here I disagree. Given that the only intended use of this function
is to be used in the ->write methods the file is a useful argument. The
only other use that sneaked in recently is ntfs ->truncate that
shouldn't use and has been fixed by a patch I sent offlist.
next prev parent reply other threads:[~2005-11-08 4:34 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
2005-11-07 22:13 ` Anton Altaparmakov
2005-11-08 4:34 ` Christoph Hellwig [this message]
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=20051108043412.GB8531@lst.de \
--to=hch@lst.de \
--cc=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=spotter@cs.columbia.edu \
/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).