Date: Mon, 24 Jan 2022 22:48:13 +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-bO9SUC0DVF@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 #9 from Alan Somers <asomers@FreeBSD.org> --- (In reply to Ivan Rozhuk from comment #8) What is utimens? FreeBSD has no such thing. Do you mean utimensat? utime= nsat is a syscall. The kernel can't call it. All the kernel does it send upcal= ls like FUSE_SETATTR to the fuse server, which in this case is sshfs. If anyt= hing is calling utimensat, it's sftp-server, which is what sshfs invokes on the = ssh server. The platform-specific value of UTIME_OMIT doesn't matter, because sshfs is compiled separately on each platform and any way UTIME_OMIT should never cross the wire over ssh. Instead, the sftp protocol presumably has s= ome other way to convey that meaning. > Linux community too big to report and fix this issue years ago. What do you mean? Are you suggesting that you're unable to report issues t= o a large community, or that because it's a large community, surely this issue must've been fixed on Linux so you aren't going to check? I'm having troub= le following your English. You really should try this on Linux with atime=3Don. I think that by defau= lt Linux sets atime=3Doff, which is probably why you didn't notice the problem there. --=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-bO9SUC0DVF>