Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Jan 2022 01:34:06 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 261434] [fusefs] mtime and ctime changed on every read file
Message-ID:  <bug-261434-227-3RNqcb6NIN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-261434-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-261434-227@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=3D261434

--- Comment #11 from Alan Somers <asomers@FreeBSD.org> ---
(In reply to Ivan Rozhuk from comment #10)
Always sending mtime along with atime would be exactly the wrong thing for =
the
kernel to do.  Only sending atime is what it's supposed to do.

Looking at the code you sent, sshfs_utimens is ignoring the tv_nsec field,
which is clearly a bug.  If those fields are set to UTIME_OMIT then it
shouldn't set that timestamp.  This is a bug in sshfs, and you should repor=
t it
upstream.

Did your friend use "-o strictatime"?  It looks like that mount option is
required on Linux in order for it to actually update the atime.

--=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-261434-227-3RNqcb6NIN>