Date: Wed, 10 Apr 2019 13:50:00 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 237181] [FUSEFS] support UTIME_NOW in utimensat Message-ID: <bug-237181-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237181 Bug ID: 237181 Summary: [FUSEFS] support UTIME_NOW in utimensat Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: asomers@FreeBSD.org UTIME_NOW is a flag value used by utimensat(2) that means "set the mtime an= d/or atime to the current time". In the FUSE protocol, this intention is indica= ted by the FATTR_ATIME_NOW and FATTR_MTIME_NOW bits of the fuse_setattr_in.valid field during the FUSE_SETATTR command. We need to support this in our fuse driver.=20=20 Currently, if you try to use UTIME_NOW on a FUSE file, I think I think "now" will be resolved in the kernel, which is ok. However, setting an explicit timestamp requires VADMIN privileges, whereas setting the time to "now" mer= ely requires VWRITE. That means a user without VADMIN privileges can't use UTIME_NOW until we implement this feature. --=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-237181-227>