From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: NeilBrown <neilb@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH ] Fix some problems with truncate and mtime semantics.
Date: Mon, 14 Nov 2005 21:03:10 -0500 [thread overview]
Message-ID: <1132020190.8802.28.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1051115020002.9459@suse.de>
On Tue, 2005-11-15 at 13:00 +1100, NeilBrown wrote:
> Resubmitting this patch to fix truncate/mtime semantics.
>
> It is against 2.6.14-mm2 and is probably suitable for 2.6.15, but can
> be held over to 2.6.16 if you are feeling cautious.
>
> NeilBrown
>
> ### Comments for Changeset
>
> SUS requires that when truncating a file to the size that it currently
> is:
> truncate and ftruncate should NOT modify ctime or mtime
> O_EXCL SHOULD modify ctime and mtime.
^^^^^ O_CREAT ;-)
> Currently mtime and ctime are always modified on most local
> filesystems (side effect of ->truncate) or never modified (on NFS).
>
> With this patch:
> ATTR_CTIME|ATTR_MTIME are sent with ATTR_SIZE precisely when
> an update of these times is required whether size changes or not
> (via a new argument to do_truncate). This allows NFS to do
> the right thing for O_EXCL.
^^^^^
Cheers,
Trond
next prev parent reply other threads:[~2005-11-15 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051115125657.9403.patches@notabene>
2005-11-15 2:00 ` NeilBrown
2005-11-15 2:03 ` Trond Myklebust [this message]
2005-11-15 2:09 ` Neil Brown
2005-11-15 11:15 ` Anton Altaparmakov
2005-11-15 9:56 ` Christoph Hellwig
2005-11-15 10:16 ` Andrew Morton
2005-11-15 10:13 ` Miklos Szeredi
2005-11-15 10:41 ` Neil Brown
2005-11-15 12:48 ` Miklos Szeredi
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=1132020190.8802.28.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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
all inboxes | Powered by JetHome®