linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: linux-fsdevel@vger.kernel.org, mikulas@artax.karlin.mff.cuni.cz,
	zippel@linux-m68k.org
Subject: ctime/mtime update in affs and hpfs write path
Date: Tue, 1 Nov 2005 00:53:06 +0100	[thread overview]
Message-ID: <20051031235306.GA21218@lst.de> (raw)

Both AFFS and HPFS update the ctime and mtime in the write path, after
generic_file_write returned and mark the inode dirty.  Anyone's got an
idea why these two filesystems aren't happy with the ctime/mtime updates
vi generic_file_write before we copied the data into the pagecache?

             reply	other threads:[~2005-10-31 23:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 23:53 Christoph Hellwig [this message]
2005-11-01  1:03 ` ctime/mtime update in affs and hpfs write path Roman Zippel
2005-11-01  1:07   ` [PATCH] remove superflous ctime/mtime updates in affs Christoph Hellwig
2005-11-01  1:20     ` Roman Zippel
2005-11-03  0:29 ` ctime/mtime update in affs and hpfs write path Mikulas Patocka

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=20051031235306.GA21218@lst.de \
    --to=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mikulas@artax.karlin.mff.cuni.cz \
    --cc=zippel@linux-m68k.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).