https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261434
--- Comment #7 from Alan Somers <asom...@freebsd.org> ---
I meant, "the kernel only tries to change the file's atime". Sorry for the
typo. The FUSE_SETATTR command allows the kernel to set any combination of
timestamps, or none. For example, here is the debug output of a different FUSE
file system where the kernel only sets atime.
2022-01-24T21:01:26.008906Z DEBUG fuse3::raw::session: setattr unique 166
inode 3 set_attr SetAttr { mode: None, uid: None, gid: None, size: None,
lock_owner: None, atime: Some(Timestamp { sec: 1643058086, nsec: 8228000 }),
mtime: None, ctime: None }
So it's probably an sshfs bug that it always sets mtime whenever the kernel
sets atime. Have you tried reproducing on Linux? It will probably happen if
you mount with atime=on .
--
You are receiving this mail because:
You are the assignee for the bug.
