From: liubaolin <liubaolin12138@163.com>
To: Hyunchul Lee <hyc.lee@gmail.com>
Cc: linkinjeon@kernel.org, ntfs@lists.linux.dev,
linux-kernel@vger.kernel.org, Xuewen Wang <wangxuewen@kylinos.cn>
Subject: Re: [PATCH v1 2/5] ntfs: preserve timestamps when creating hard links
Date: Thu, 29 Oct 2026 09:49:06 +0800 [thread overview]
Message-ID: <a81b1308-dc85-4d93-beb0-17d728e85f11@163.com> (raw)
In-Reply-To: <auKQCM-vwM5RPYDc@hyunchul-PC02>
在 2026/10/29 08:15, Hyunchul Lee 写道:
> Hi Baolin,
>
> On Tue, Oct 27, 2026 at 05:35:12PM +0800, Baolin Liu wrote:
>> From: Xuewen Wang <wangxuewen@kylinos.cn>
>>
>> ntfs_link() resets atime, mtime and ctime on both the source file and
>> the destination directory after creating a hard link. This overwrites
>> the source file's atime and mtime and the directory's atime.
>>
>> Update only the source ctime and the destination directory mtime/ctime.
>> Mark both inodes dirty so these changes are queued for writeback instead
>> of relying on the earlier FILE_NAME write.
>>
>> Signed-off-by: Xuewen Wang <wangxuewen@kylinos.cn>
>> ---
>> Tested with the complete five-patch series in QEMU. Explicitly assigned
>> atime and mtime are preserved across ordinary hard-link creation and
>> O_TMPFILE publication. A separate persistence check set and synced
>> atime/mtime on the published file, then verified those values after
>> cache eviction, remount and a fresh boot.
>>
>> fs/ntfs/namei.c | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/ntfs/namei.c b/fs/ntfs/namei.c
>> index 0c84a5c..4442e1d 100644
>> --- a/fs/ntfs/namei.c
>> +++ b/fs/ntfs/namei.c
>> @@ -1663,12 +1663,13 @@ static int ntfs_link(struct dentry *old_dentry, struct inode *dir,
>> }
>>
>> inode_inc_iversion(dir);
>> - simple_inode_init_ts(dir);
>> + inode_set_mtime_to_ts(dir, inode_set_ctime_current(dir));
>> + mark_inode_dirty(dir);
>>
>> inode_inc_iversion(vi);
>> - simple_inode_init_ts(vi);
>> + inode_set_ctime_current(vi);
>> + mark_inode_dirty(vi);
>
> Could you also update the last_mft_change_time of $FILE_NAME? it still
> appears to retains the old ctime.
>
> Additionaly, could you run run xfstests generic/004 and generic/389?
>
Hi Hyunchul,
Thanks for your review. Xuewen and I will make modifications and run
tests per your comments, and submit the v2 patch afterwards.
Thanks,
Baolin.
>
>>
>> - /* timestamp is already written, so mark_inode_dirty() is unneeded. */
>> d_instantiate(dentry, vi);
>> mutex_unlock(&dir_ni->mrec_lock);
>> mutex_unlock(&ni->mrec_lock);
>>
>
next prev parent reply other threads:[~2026-10-29 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 9:35 [PATCH v1 0/5] ntfs: support O_TMPFILE Baolin Liu
2026-10-27 9:35 ` [PATCH v1 1/5] ntfs: initialize inherited ACLs after allocating the MFT record Baolin Liu
2026-10-27 9:35 ` [PATCH v1 2/5] ntfs: preserve timestamps when creating hard links Baolin Liu
2026-10-29 0:15 ` Hyunchul Lee
2026-10-29 1:44 ` wangxuewen
2026-10-29 1:49 ` liubaolin [this message]
2026-10-27 9:35 ` [PATCH v1 3/5] ntfs: initialize packed EA size " Baolin Liu
2026-10-27 9:35 ` [PATCH v1 4/5] ntfs: write unlinked file attributes before dropping their cache Baolin Liu
2026-10-27 9:35 ` [PATCH v1 5/5] ntfs: support O_TMPFILE Baolin Liu
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=a81b1308-dc85-4d93-beb0-17d728e85f11@163.com \
--to=liubaolin12138@163.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs@lists.linux.dev \
--cc=wangxuewen@kylinos.cn \
/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
all inboxes | Powered by JetHome®