linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jubin Zhong <zhongjubin@huawei.com>
To: <hch@infradead.org>
Cc: <kechengsong@huawei.com>, <linux-fsdevel@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <viro@zeniv.linux.org.uk>,
	<wangfangpeng1@huawei.com>, <zhongjubin@huawei.com>
Subject: Re: [PATCH] fs: Fix truncate never updates m/ctime
Date: Tue, 16 Nov 2021 11:58:10 +0800	[thread overview]
Message-ID: <1637035090-52547-1-git-send-email-zhongjubin@huawei.com> (raw)
In-Reply-To: <YZKfr5ZIvNBmKDQI@infradead.org>

> On Mon, Nov 15, 2021 at 07:00:18PM +0800, Jubin Zhong wrote:
>> From: zhongjubin <zhongjubin@huawei.com>
>> 
>> Syscall truncate() never updates m/ctime even if the file size is
>> changed. However, this is incorrect according to man file:
>> 
>>   truncate (2):
>>   If  the  size  changed, then the st_ctime and st_mtime fields
>>   (respectively, time of last status change and time of last modification;
>>   see stat(2)) for the file are updated, and the set-user-ID and
>>   set-group-ID mode bits may be cleared.
>> 
>> Check file size before do_truncate() to fix this.
>
> Please try to actually reproduce your alleged "bug".  And maybe also
> look at the actual setattr implementations.  Hint: The XFS one even
> has extensive comments.

Thanks for your advice. I found this problem on yaffs2 in the beginning,
ftruncate() always works fine but truncate() does not. Now I have done 
a few more tests and the following are the results:

Test Environmont:
	kernel: Linux Kernel v5.16
	hardware: QEMU emulator version 3.1.0
	arch: vexpress-v2p-ca9

Teset Results:
	filesystems     m/ctime updated by truncate?
	jffs2           fail
	yaffs2          fail
	ubifs           success
	ext2            success
	ext4            success
	tmpfs           success
	xfs             success

Test Steps:
	1. cd /path/to/mnt/point
	2. dd if=/dev/zero of=test bs=1M count=1
	3. stat test
	4. /bin/my_truncate -s 1024 test
	5. stat test
	6. compare m/ctime of step 5 with step 3

Program source:
	#include <stdio.h>
	#include <stdlib.h>
	#include <string.h>
	#include <unistd.h>
	#include <sys/types.h>
	int main(int argc, char **argv)
	{
		int ret;
		char file_name[128] = {0};
		
		if (argc < 4 || argv == NULL || argv[1] == NULL || argv[2] == NULL || argv[3] == NULL) {
			return -1;
		}
		
		if (strcmp(argv[1], "-s")) {
			return -1;
		}
		
		if (realpath(argv[3], file_name) == NULL) {
			printf("truncate: input file name %s err.\n", argv[3]);
			return -1;
		}
		
		off_t size = (off_t)strtol(argv[2], 0, 0);
		ret = truncate(file_name, size);
		if (ret) {
			printf("truncate return err %d\n", ret);
		}   
		return ret;
	}   

I work on embedded devices so concern about jffs2/yaffs2/ubifs the most. 
If there are any errors in my test program please let me know.

Thanks.

  reply	other threads:[~2021-11-16  3:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 11:00 [PATCH] fs: Fix truncate never updates m/ctime Jubin Zhong
2021-11-15 17:58 ` Christoph Hellwig
2021-11-16  3:58   ` Jubin Zhong [this message]
2021-11-16  5:22     ` Christoph Hellwig
2021-11-16  6:57       ` Jubin Zhong
2021-11-16  7:02         ` Christoph Hellwig

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=1637035090-52547-1-git-send-email-zhongjubin@huawei.com \
    --to=zhongjubin@huawei.com \
    --cc=hch@infradead.org \
    --cc=kechengsong@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wangfangpeng1@huawei.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).