From: Christoph Hellwig <hch@lst.de>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: [PATCH 3/4] simplify xfs_vn_getattr
Date: Wed, 19 Sep 2007 13:04:38 +0200 [thread overview]
Message-ID: <20070919110438.GB3703@lst.de> (raw)
In-Reply-To: <46F08F98.9070102@sgi.com>
On Wed, Sep 19, 2007 at 12:55:20PM +1000, Lachlan McIlroy wrote:
> Why do we copy the atime from the inode and not the xfs_inode?
>
> I think I see what's the deal here - the atime in the inode is
> the authoritative atime. It gets updated from various places and
> we synchronise it to the xfs inode before flushing the xfs inode
> to disk. This means we shouldn't be using the atime in the
> xfs_inode because it will be stale - is this correct?
Yes. atime is updated by the vfs without callouts to the filesystem
in various places unfortunately.
prev parent reply other threads:[~2007-09-19 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 16:27 [PATCH 3/4] simplify xfs_vn_getattr Christoph Hellwig
2007-09-19 2:55 ` Lachlan McIlroy
2007-09-19 11:04 ` Christoph Hellwig [this message]
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=20070919110438.GB3703@lst.de \
--to=hch@lst.de \
--cc=lachlan@sgi.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.