Date: Tue, 19 Sep 2023 19:30:19 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 273942] fusefs(5): read operation changes ctime on FUSE filesystems Message-ID: <bug-273942-3630-tbgeRIZRIZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273942-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-273942-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273942 --- Comment #6 from Agata <chogata@moosefs.com> --- Well, it's not a correct behaviour when it sets an arbitrary timestamp. As I said - using "now" would be OK-ish. Using an arbitrary timestamp makes the setattr indistinguishable from a user-made setattr, so it updates ctime (because setattr performed a metadata change), which is wrong. Best would be to not set anything :) FUSE leaves the atime/mtime/ctime hand= ling on the filesystem's side, why force it? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273942-3630-tbgeRIZRIZ>