From nobody Tue Sep 19 20:54:44 2023 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Rqv6r5XpCz4mHc9 for ; Tue, 19 Sep 2023 20:54:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Rqv6r3RWLz3bG3 for ; Tue, 19 Sep 2023 20:54:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1695156884; a=rsa-sha256; cv=none; b=iAaUHUrurlWFMFToLcAFltIejv5BuJU1SX2hYzGUTjkf2NXaOa37/gza4VRueS7HWtcM64 9nqqhtxcm70J1nzT58nKcoZBgJsMMUwkpS16DBH2rCHpJdSQzf6F/HstIPj3Sj0jCXlBc6 GSqTfZuyvxLq+PQlaoVRFbK99FzRSJ9CjH3/UsC/Gu+PmUUM3DBgtTs3U8lLQAMcs1M9sT wgJekZic1ILatawuXOE4lYGZl+b0tpmCozdx6pf0F7pgWC6OSHIGGkRxfqgxgCYqfTQhUE ODKz7MnzJZd1W5MEtZgKOXtg7Xlbfp46fapkyAOafDZSjOjrCXbv0KiUq1dH6Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1695156884; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=n+IgEjLc/5YMkabAe1X7dNSNNTpmo7PgNVQdAU+0AV0=; b=x0H7F9BdB7KXvol4W/J9jhmQiZ73kwowfdJZke72PUOlqD1KMOFcHD6tjgUyH6+Yv9bcTy xBmd9qiHa7jqkciMCF6ErRDGb2Z7X4lq7MebpvAE9FgzQsaWhFfPTJ9hA+DRFNJSYLIyZ/ vBoeP77hVjYunUvz/3oobwVJar2lNjiS1lX4iiSKZllzNLqeMw2Cgk/+9h/glQtvqcJL3u nRRDI1uZ5UWj1odgVNwDh9Upv7T4MObhB+Mxq9cOcZ2szwIK4u5ldqAAzI0lzjhNHSNhdw j9/TadIFPGSnh8ZPb5NEnL35Flpgw7lmd0QZ5E0vfY2sDg9xrehpJFHLd+0Bkg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Rqv6r2W9pzDC8 for ; Tue, 19 Sep 2023 20:54:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 38JKsiWh008255 for ; Tue, 19 Sep 2023 20:54:44 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 38JKsiCZ008254 for fs@FreeBSD.org; Tue, 19 Sep 2023 20:54:44 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 273942] fusefs(5): read operation changes ctime on FUSE filesystems Date: Tue, 19 Sep 2023 20:54:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: asomers@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273942 --- Comment #7 from Alan Somers --- When a FUSE file system uses the data cache, then the FUSE daemon cannot ha= ndle atime updates itself, because a read may be serviced by cache. In such a c= ase, the OS must issue the atime updates. If the data cache is not enabled, but atime and the attribute cache are, th= en the OS has a choice. Either it can track atime updates itself, or it can a= sk the server, which causes a new FUSE_GETATTR request after every read. That kind of defeats the purpose of the attribute cache. It seems to me that if the OS sends a FUSE_SETATTR with the valid field set= to FATTR_ATIME, then the server should not update the CTIME. Do you disagree?= =20 Fir if the atime update actually came from userland, for example from utimensat(), then the FATTR_CTIME bit will be set, too. --=20 You are receiving this mail because: You are the assignee for the bug.=