From: Taesoo Kim <taesoo@gatech.edu>
To: lczerner@redhat.com, cmaiolino@redhat.com, xfs@oss.sgi.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: taesoo@gatech.edu, changwoo@gatech.edu, sanidhya@gatech.edu,
blee@gatech.edu, csong84@gatech.edu
Subject: inconsistent timestamp update in rename() of xfs/fat/gfs2/ramfs/jffs2...
Date: Fri, 20 Mar 2015 16:23:39 -0400 [thread overview]
Message-ID: <20150320202339.GK25797@taesoo.org> (raw)
Hi all,
We've cross-checking patches from ext3/ext4, and found out
inconsistent implementations of other fs. We want to ask whether this
is intended or unexpected behavior. We will be able to send patches as
soon as confirmed/acknowledged.
Ref.
(ext4) 53b7e9f6807c1274eee19201396b4c2b5f721553
(ext3) 0b23076988b44b2c165e060248345de6f2337387
| ext3/4: fix update of mtime and ctime on rename
---------------------------------------------------------------------
We summarized our finding:
(* means what we believe is correct beahvoir)
<Linux 4.0-rc2>
ramfs affs fsplus
vfs xfs fat gfs2 jffs2 hfsh
operation | * | | | | | | | | |
===========================================================
new_inode->i_ctime | V | - | - | V | V | - | - | V | - | -
old_inode->i_ctime | V | V | V | - | V | V | - | - | - | -
old_dir->i_ctime | V | V | V | V | V | V | V | - | V | V
old_dir->i_mtime | V | V | V | V | V | V | V | - | V | V
new_dir->i_ctime | V | V | V | V | - | V | V | - | V | V
new_dir->i_mtime | V | V | V | V | - | V | V | - | V | V
new_dir->i_atime | - | - | - | V | - | - | - | - | - | -
* Correct behavior in
ext2, ext3, ext4, btrfs, f2fs, nilfs, reiserfs, cifs, exofs, jfs,
ubifs, ocfs and minix
---------------------------------------------------------------------
Thanks,
Taesoo
next reply other threads:[~2015-03-20 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 20:23 Taesoo Kim [this message]
2015-03-20 22:28 ` inconsistent timestamp update in rename() of xfs/fat/gfs2/ramfs/jffs2 Dave Chinner
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=20150320202339.GK25797@taesoo.org \
--to=taesoo@gatech.edu \
--cc=blee@gatech.edu \
--cc=changwoo@gatech.edu \
--cc=cmaiolino@redhat.com \
--cc=csong84@gatech.edu \
--cc=lczerner@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanidhya@gatech.edu \
--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 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).