From nobody Mon Apr 10 23:44:35 2023 X-Original-To: freebsd-current@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 4PwQYr3ShKz44yBd for ; Mon, 10 Apr 2023 23:44:48 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f54.google.com (mail-vs1-f54.google.com [209.85.217.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PwQYr1ScTz3xY0 for ; Mon, 10 Apr 2023 23:44:48 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vs1-f54.google.com with SMTP id e20so5876622vsj.10 for ; Mon, 10 Apr 2023 16:44:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681170287; x=1683762287; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=mgQXBMxtB/0pm/OJ1yxi/mHqY9ZeWiUJzFUu+it9EDc=; b=kWkowU7UR1RIncJbEOhskvrgEkGxwXCW6+YuPuFFp9/feYPDcoAKhkTrmHZ4Nd1UCU j8W7w4hs9TRANUYVdtGTN7Yy6ziJoVTKAUk+Pgci6iJvybjLrMHAZytQoicyw5HzFHki lFNV1JtvhR2sEF5xT33+kcOwQk8hof8J9MNFAA4WmZo/P7wpT4PuKgRIHPOjGmgZ6+BK 7tM4xLxbUtIZFb16hJi7rO41UCCWJKnuVwe6cVE3bog5gnGDA3cDMutMGYYyn3iiZD9D NoJasEOZ+fbEcGLgT8QCYSqaw7VlDWmdhNKQpWYJvBcanHFcHp1d6xedzqbg38CrlfJ/ 0J3g== X-Gm-Message-State: AAQBX9dhON83y4afGdmlqxZwenVJfBIYY1e8ieb/ONXjLgdCFTLAC9Ur w5nlMLo69JWYD1Eg0ENVj5jwXhTfMkuoPqzC0+AwuH/J X-Google-Smtp-Source: AKy350aXvGnsiDfZl4GWCjks1RXX+d3BPRd4R0AfPwysWSw5j9Sj3o9wgzwtwiiGIi35oy+P15ReT2ZxI0arMkut7Y8= X-Received: by 2002:a67:d496:0:b0:42c:6917:15bc with SMTP id g22-20020a67d496000000b0042c691715bcmr3184692vsj.4.1681170287035; Mon, 10 Apr 2023 16:44:47 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202304102340.33ANe66j000558@donotpassgo.dyslexicfish.net> In-Reply-To: <202304102340.33ANe66j000558@donotpassgo.dyslexicfish.net> From: Alan Somers Date: Mon, 10 Apr 2023 16:44:35 -0700 Message-ID: Subject: Re: [FUSEFS] File close() failures relating to attempted atime update To: Jamie Landeg-Jones Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4PwQYr1ScTz3xY0 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Thanks for the head's up. Hopefully I'll be able to look at it later this = week. On Mon, Apr 10, 2023 at 4:40=E2=80=AFPM Jamie Landeg-Jones wrote: > > There is a replicable problem with file closing on fusefs, since > 0bade34633f997c22f5e4e0931df0d534f560a38, Alan Somers 2021-11-29 01:53:31 +0000 > > It appears to be related to attempting to update atime on a file you > don't have write-access to. > > I've posted much more details, and a potential fix to > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270749 > > Cheers, Jamie