Date: Tue, 25 Jan 2022 03:44:41 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 261434] [sysutils/fusefs-sshfs] updating a file's atime causes its mtime to change too Message-ID: <bug-261434-227-n1dIz4JDjR@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 Ivan Rozhuk <rozhuk.im@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|Works As Intended |--- Status|Closed |New --- Comment #16 from Ivan Rozhuk <rozhuk.im@gmail.com> --- (In reply to Alan Somers from comment #15) > That's in the else statement. Look above, at line 2855. #ifdef HAVE_UTIMENSAT - "new code" block, added in 2012, before it 4 years = work only code that requires both times together. > As I've said, you haven't performed a valid test, because you haven't use= d -o strictatime . This change nothing. >> It looks like that mount option is required on Linux in order for it to = actually update the atime. atime changed, mtime - not. I do not understand what do you expect to see playing with flags. Do you test all fusefs consumers to ensure that updating only atime work correctly? --=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-n1dIz4JDjR>