From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 69C2FC41513 for ; Mon, 14 Aug 2023 12:39:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229987AbjHNMjN (ORCPT ); Mon, 14 Aug 2023 08:39:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53262 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230418AbjHNMi6 (ORCPT ); Mon, 14 Aug 2023 08:38:58 -0400 Received: from nov-007-i659.relay.mailchannels.net (nov-007-i659.relay.mailchannels.net [46.232.183.213]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 002BDE5B; Mon, 14 Aug 2023 05:38:53 -0700 (PDT) X-Sender-Id: novatrend|x-authuser|juerg@bitron.ch Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id C1B086C0082; Mon, 14 Aug 2023 12:38:50 +0000 (UTC) X-Sender-Id: novatrend|x-authuser|juerg@bitron.ch X-MC-Relay: Neutral X-MailChannels-SenderId: novatrend|x-authuser|juerg@bitron.ch X-MailChannels-Auth-Id: novatrend X-Cold-Shoe: 6263835827e2b840_1692016730527_1977572546 X-MC-Loop-Signature: 1692016730527:1089382471 X-MC-Ingress-Time: 1692016730527 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitron.ch; s=default; h=MIME-Version:Content-Transfer-Encoding:Content-Type:References: In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=UnFq8cK/dpffTOxd/mAzwBFyBjuZ38mvKS1JaKUYa+Y=; b=LqKqitPka07ght4saTNSkUYEjR rq04ITnySzAE1qoVlKxNWbQTSAFZsi49hUVCXX8ECbwBKXLyKj+1boiHTDcUrvcIeF0d63c/JhpC7 xxkcOBCd5/GyCpnMjp/NNZ/Ht; Message-ID: Subject: Re: [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush From: =?ISO-8859-1?Q?J=FCrg?= Billeter To: Miklos Szeredi , Bernd Schubert Cc: "Eric W. Biederman" , Tycho Andersen , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, regressions@lists.linux.dev Date: Mon, 14 Aug 2023 14:38:44 +0200 In-Reply-To: References: <4f66cded234462964899f2a661750d6798a57ec0.camel@bitron.ch> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.1 MIME-Version: 1.0 X-AuthUser: juerg@bitron.ch Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2023-08-14 at 14:28 +0200, Miklos Szeredi wrote: > On Mon, 14 Aug 2023 at 14:07, Bernd Schubert=20 > > fuse: Avoid flush for O_RDONLY > >=20 > > From: Bernd Schubert > >=20 > > A file opened in read-only moded does not have data to be > > flushed, so no need to send flush at all. > >=20 > > This also mitigates -EBUSY for executables, which is due to > > async flush with commit 5a8bee63b1. >=20 > Does it?=C2=A0 If I read the bug report correctly, it's the write case th= at > causes EBUSY. Indeed, I see this when trying to execute a file after a process wrote to (created) that file. As far as I can tell, `ETXTBSY` can't happen on exec without the file being opened for writing and thus, I don't see this patch mitigating this bug. J=C3=BCrg