[Bug 261434] [sysutils/fusefs-sshfs] updating a file's atime causes its mtime to change too

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 25 Jan 2022 04:15:39 UTC

Alan Somers <asomers@FreeBSD.org> changed:

           What    |Removed                     |Added
         Resolution|FIXED                       |Works As Intended

--- Comment #19 from Alan Somers <asomers@FreeBSD.org> ---
> atime WAS UPDATED without strictatime.

I tried it myself on Linux.  With relatime (the default), the kernel sends no
FUSE_SETATTR operation at all.  Instead, the reason you see atime change must
be because the ssh server changed it.

> With option got error: fuse: unknown option(s): `-o strictatime'

That's a limitation of sshfs's CLI then.  There's probably a way to convince
Linux to use strictatime by using "mount -o remount ...", but I'm not going to
spend my evening figuring it out.

> Without testing all fuselib consumers you can not mark this as only sshfs bug.

You are speaking nonsense.  There are dozens if not hundreds of FUSE file
systems, many of them not even in ports.  We have already verified, from
reading its code, that sshfs ignores any UTIME_OMIT value.  That is the bug. 
Report it upstream.

You are receiving this mail because:
You are the assignee for the bug.