Date: Tue, 25 Jan 2022 03:03:42 +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-THJx7sEEDj@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 Alan Somers <asomers@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Works As Intended Status|New |Closed --- Comment #13 from Alan Somers <asomers@FreeBSD.org> --- (In reply to Ivan Rozhuk from comment #12) > libfuse does not call utimens() in case UTIME_OMIT, as far I understand. = I have no plans to report it. Yes it does. That link you sent shows that libfuse will call the file syste= m's utimens callback if EITHER atime or mtime is valid. That's what's happening here. The kernel is trying to set atime, but not mtime. > There is no place to nsec and magic values. If this bug is caused by a limitation in the SFTP protocol, then there's nothing that FreeBSD can do about it. You should take it up upstream. Per= haps sshfs should always disable atime. > No, just -o atime. Then his test is irrelevant. He needs to use -o strictatime. This is not a FreeBSD bug. You need to report it to https://github.com/libfuse/sshfs . I'm going to close it now. --=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-THJx7sEEDj>