From nobody Tue Sep 19 19:30:19 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 4RqsFR6KwNz4mB8T for ; Tue, 19 Sep 2023 19:30:19 +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 4RqsFR5H2fz3VjX for ; Tue, 19 Sep 2023 19:30:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1695151819; a=rsa-sha256; cv=none; b=URBOrydD1rg8MAGx+csl+bFT0Bykd9GRJ5ax/UybpgV6pdBD8mgEgCZzRCqCQDhGDYbJq+ alGxEy5ND9ik0Njd8wdB5VOjcE7eEfU0Hc/ChA2UOScmXKxMD8jkU0otQBGlCErk08gTtJ t0pbJ+NIZOSknCYNf9j/ycHTgMo7DT5oSbn0VgYHgQbb+Wu4tyoU+YCmD+/tF6pHOrVIpL frcM8xsjBEkhGXAVFEb38aWKkGrH2AS+zRwbJMsjWiuuCkMURN1QrcEQwNCkv88lwvx4AW oO8P1/cXQJwRaCV9x5oNNOuMzeXRmgREsyboYoH3Qe2wU7su05b46SjjHKbL3Q== 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=1695151819; 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=V27MM+R/MnN3wKvC4o4ByaCjMOYx8iummNVDn2ZGRdU=; b=SywvdJVw+SC4qbzs7WaLB++2kKGABi7/+gRzROn9Rsv8vGRMhhK3povxFC/AvmU3TVRr8l lCsE6lSCMrAGhS6AvV25JZMNtSP6pFZkuWdUoIVw3Ti5ck+MPcUpuW4cCFlBvEbx+azH5Z 3yym3bPHMvGgx4MHx/CAG/qJ4fjAZerIh7aSUOxDVW8Hhd3tD8BgDn4xmPeX/csyA3pXDf ZmMTYdrsJMflJgZ7mShtqaPAfEEqjwL2FLEtxCE0r+cPhVnCKsnXW+dMGqx8f/24Vo2yEi +LAqkswAcKJUd0KhDizAObF80BB+5OPBM0std93aw/MWW1VntXbheaMPpw+cSA== 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 4RqsFR4JvDzBKr for ; Tue, 19 Sep 2023 19:30:19 +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 38JJUJqF083543 for ; Tue, 19 Sep 2023 19:30:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 38JJUJ4N083542 for fs@FreeBSD.org; Tue, 19 Sep 2023 19:30:19 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 19:30:19 +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: chogata@moosefs.com 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 #6 from Agata --- Well, it's not a correct behaviour when it sets an arbitrary timestamp. As I said - using "now" would be OK-ish. Using an arbitrary timestamp makes the setattr indistinguishable from a user-made setattr, so it updates ctime (because setattr performed a metadata change), which is wrong. Best would be to not set anything :) FUSE leaves the atime/mtime/ctime hand= ling on the filesystem's side, why force it? --=20 You are receiving this mail because: You are the assignee for the bug.=