linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Kazuya Mio <k-mio@sx.jp.nec.com>
Cc: Jan Kara <jack@suse.cz>, ext4 <linux-ext4@vger.kernel.org>,
	Andreas Dilger <adilger@dilger.ca>
Subject: Re: [PATCH 2/2] ext3: Don't update ctime in ext3_splice_branch()
Date: Wed, 1 Feb 2012 11:46:33 +0100	[thread overview]
Message-ID: <20120201104633.GA16714@quack.suse.cz> (raw)
In-Reply-To: <4F28F021.8030904@sx.jp.nec.com>

On Wed 01-02-12 16:56:17, Kazuya Mio wrote:
> 2012/01/31 2:52, Jan Kara wrote:
> >  Thanks for the patches.  This is true for ordinary writes but not true
> >when you write via mmap. We call file_update_time() during page fault so
> >ctime won't be completely wrong but still we should update it after block
> >is allocated during writeback to reflect that new block is allocated to
> >the inode.
> 
> Should we update ctime whenever a block is allocated?
  Since ctime should be updated whenever inode is changed, and allocating
block updates i_blocks (via dquot_alloc_block()), we should update ctime.

> If so, ordinary write in ext4 with indirect block mapping has the same problem
> due to the following patch, right?
> http://marc.info/?l=linux-ext4&m=124505184027078&w=4
  It's kind of the same problem. But things are more complicated by the
fact that ext4 also does delayed allocation so, as changelog of the patch
you reference says, it's kind of unexpected from users to see ctime
suddently update when VM decides to do writeout triggering block
allocation. I'd think updating ctime is a correct (although unexpected)
thing to do but I can understand Ted's position as well and he's ext4
maintainer :).

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2012-02-01 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30  8:41 [PATCH 2/2] ext3: Don't update ctime in ext3_splice_branch() Kazuya Mio
2012-01-30 17:52 ` Jan Kara
2012-02-01  7:56   ` Kazuya Mio
2012-02-01 10:46     ` Jan Kara [this message]
2012-02-08  8:36       ` Kazuya Mio

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=20120201104633.GA16714@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=adilger@dilger.ca \
    --cc=k-mio@sx.jp.nec.com \
    --cc=linux-ext4@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).