From: Andreas Schwab <schwab@suse.de>
To: linux-riscv@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Multigrain timestamps do not work on RISC-V
Date: Wed, 29 Jan 2025 11:07:15 +0100 [thread overview]
Message-ID: <mvmv7ty3pd8.fsf@suse.de> (raw)
The statx06 test in the LTP testsuite fails since the multigrain
timestamp feature was merged:
https://openqa.opensuse.org/tests/4800409#step/statx06/7
The issue is that the nsec part of ctime does not change from the time
the file is created:
$ touch xx
$ stat -c $'mtime %y\nctime %z' xx
mtime 2025-01-29 09:43:44.677442605 +0100
ctime 2025-01-29 09:43:44.677442605 +0100
$ touch xx
$ stat -c $'mtime %y\nctime %z' xx
mtime 2025-01-29 09:43:51.641581658 +0100
ctime 2025-01-29 09:43:51.677442605 +0100
My guess would be that something in inode_set_ctime_current is going
wrong.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: linux-riscv@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Multigrain timestamps do not work on RISC-V
Date: Wed, 29 Jan 2025 11:07:15 +0100 [thread overview]
Message-ID: <mvmv7ty3pd8.fsf@suse.de> (raw)
The statx06 test in the LTP testsuite fails since the multigrain
timestamp feature was merged:
https://openqa.opensuse.org/tests/4800409#step/statx06/7
The issue is that the nsec part of ctime does not change from the time
the file is created:
$ touch xx
$ stat -c $'mtime %y\nctime %z' xx
mtime 2025-01-29 09:43:44.677442605 +0100
ctime 2025-01-29 09:43:44.677442605 +0100
$ touch xx
$ stat -c $'mtime %y\nctime %z' xx
mtime 2025-01-29 09:43:51.641581658 +0100
ctime 2025-01-29 09:43:51.677442605 +0100
My guess would be that something in inode_set_ctime_current is going
wrong.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next reply other threads:[~2025-01-29 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 10:07 Andreas Schwab [this message]
2025-01-29 10:07 ` Multigrain timestamps do not work on RISC-V Andreas Schwab
2025-01-29 17:20 ` Andreas Schwab
2025-01-29 17:20 ` Andreas Schwab
2025-01-29 23:06 ` Jeff Layton
2025-01-29 23:06 ` Jeff Layton
2025-01-29 23:28 ` Jeff Layton
2025-01-29 23:28 ` Jeff Layton
2025-01-30 9:29 ` Andreas Schwab
2025-01-30 9:29 ` Andreas Schwab
2025-01-29 23:03 ` Jeff Layton
2025-01-29 23:03 ` Jeff Layton
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=mvmv7ty3pd8.fsf@suse.de \
--to=schwab@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
/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.