Date: Mon, 24 Jan 2022 22:30:00 +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-cShAQY2uLB@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 #8 from Ivan Rozhuk <rozhuk.im@gmail.com> --- (In reply to Alan Somers from comment #7) > The FUSE_SETATTR command allows the kernel to set any combination of time= stamps It may allow whatever, but it call utimens() with limited interface. Even more, this utimens() can not accept UTIME_OMIT because it have differe= nt values on linux and bsd. UTIME_NOW can be handled by sshfs locally. My point is: kernel must call utimens() with correct atime+mtime values. > So it's probably an sshfs bug that it always sets mtime whenever the kern= el sets atime. utimens() send SSH_FXP_SETSTAT/SSH_FXP_FSETSTAT that requires both: atime + mtime. > Have you tried reproducing on Linux? No. I load my linux first time since November 2020 just to make sure that t= his is not fresh openssh issue. Linux community too big to report and fix this issue years ago. > It will probably happen if you mount with atime=3Don I always use sshfs with atime=3Don, this is default. --=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-cShAQY2uLB>