linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Josef Bacik <josef@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, viro@ZenIV.linux.org.uk,
	linux-btrfs@vger.kernel.org, hch@infradead.org
Subject: Re: [RFC] [PATCH 1/2] fs: introduce inode operation ->update_time
Date: Mon, 30 Apr 2012 11:21:47 -0400	[thread overview]
Message-ID: <20120430152147.GA20554@infradead.org> (raw)
In-Reply-To: <1332771031-3337-1-git-send-email-josef@redhat.com>

On Mon, Mar 26, 2012 at 10:10:30AM -0400, Josef Bacik wrote:
> Btrfs has to make sure we have space to allocate new blocks in order to modify
> the inode, so updating time can fail.  We've gotten around this by having our
> own file_update_time but this is kind of a pain, and Christoph has indicated he
> would like to make xfs do something different with atime updates.  So introduce
> ->update_time, where we will deal with i_version an a/m/c time updates and
> indicate which changes need to be made.  The normal version just does what it
> has always done, updates the time and marks the inode dirty, and then
> filesystems can choose to do something different.
> 
> I've gone through all of the users of file_update_time and made them check for
> errors with the exception of the fault code since it's complicated and I wasn't
> quite sure what to do there, also Jan is going to be pushing the file time
> updates into page_mkwrite for those who have it so that should satisfy btrfs and
> make it not a big deal to check the file_update_time() return code in the
> generic fault path. Thanks,

Any reason that atime updates ignore the return value?

Otherwise looks fine,

Reviewed-by: Christoph Hellwig <hch@lst.de>

  parent reply	other threads:[~2012-04-30 15:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26 14:10 [RFC] [PATCH 1/2] fs: introduce inode operation ->update_time Josef Bacik
2012-03-26 14:10 ` [RFC] [PATCH 2/2] Btrfs: move over to use ->update_time Josef Bacik
2012-04-04 17:24   ` Kasatkin, Dmitry
2012-04-04 17:43     ` Josef Bacik
2012-04-04 17:47       ` Mimi Zohar
2012-04-04 18:12         ` Kasatkin, Dmitry
2012-04-04 18:16           ` Josef Bacik
2012-04-04 18:21             ` Kasatkin, Dmitry
2012-04-09 15:16             ` J. Bruce Fields
2012-04-10  7:48               ` David Sterba
2012-04-12 11:09                 ` Kasatkin, Dmitry
2012-04-12 11:32                   ` David Sterba
2012-04-12 11:43                     ` Kasatkin, Dmitry
2012-05-11  6:06                     ` Kasatkin, Dmitry
2012-05-11 18:34                       ` Josef Bacik
2012-04-30 15:21 ` Christoph Hellwig [this message]
2012-04-30 17:12   ` [RFC] [PATCH 1/2] fs: introduce inode operation ->update_time Josef Bacik

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=20120430152147.GA20554@infradead.org \
    --to=hch@infradead.org \
    --cc=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).