Date: Wed, 20 Sep 2023 16:05:02 +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-yEvCQxePF9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273942-3630@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273942 --- Comment #10 from Agata <chogata@moosefs.com> --- I tested atime change with futimens call from userland (FreeBSD 13.2) and it did not send ctime change (no ctime flag on in setattr, both the setattr after read and the setattr caused by futimens call have 0x10). So I'm back to the starting point: no way to say if setattr is a result of internal atime change after a read operation or a user-made operation. (I'm leaving on 2 weeks vacation tomorrow, so I won't be able to follow here for a while). -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273942-3630-yEvCQxePF9>