From: Christoph Hellwig <hch@infradead.org>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fix ctime update of on-disk inode
Date: Thu, 8 Dec 2011 21:03:50 -0500 [thread overview]
Message-ID: <20111209020350.GA29118@infradead.org> (raw)
In-Reply-To: <4EE16713.2070907@cn.fujitsu.com>
On Fri, Dec 09, 2011 at 09:40:35AM +0800, Li Zefan wrote:
> To reproduce the bug:
>
> # touch /mnt/tmp
> # stat /mnt/tmp | grep Change
> Change: 2011-12-09 09:32:23.412105981 +0800
> # chattr +i /mnt/tmp
> # stat /mnt/tmp | grep Change
> Change: 2011-12-09 09:32:43.198105295 +0800
> # umount /mnt
> # mount /dev/loop1 /mnt
> # stat /mnt/tmp | grep Change
> Change: 2011-12-09 09:32:23.412105981 +0800
>
> We should update ctime of in-memory inode before calling
> btrfs_update_inode().
Can you submit this one as a test for xfstests?
next prev parent reply other threads:[~2011-12-09 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 1:40 [PATCH] Btrfs: fix ctime update of on-disk inode Li Zefan
2011-12-09 2:03 ` Christoph Hellwig [this message]
2011-12-09 2:12 ` Li Zefan
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=20111209020350.GA29118@infradead.org \
--to=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox