Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <e7499d0942a4489086c803dcdf1a5bb4317e973e.camel@bitron.ch>
Subject: Re: [REGRESSION] fuse: execve() fails with ETXTBSY due to async
 fuse_flush
From:   =?ISO-8859-1?Q?J=FCrg?= Billeter <j@bitron.ch>
To:     Miklos Szeredi <miklos@szeredi.hu>,
        Bernd Schubert <bernd.schubert@fastmail.fm>
Cc:     "Eric W. Biederman" <ebiederm@xmission.com>,
        Tycho Andersen <tycho@tycho.pizza>,
        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: <CAJfpegtUVUDac5_Y7BMJvCHfeicJkNxca2hO1crQjCNFoM54Lg@mail.gmail.com>
References: <4f66cded234462964899f2a661750d6798a57ec0.camel@bitron.ch>
         <CAJfpeguG4f4S-pq+_EXHxfB63mbof-VnaOy-7a-7seWLMj_xyQ@mail.gmail.com>
         <da17987a-b096-9ebb-f058-8eb91f15b560@fastmail.fm>
         <CAJfpegtUVUDac5_Y7BMJvCHfeicJkNxca2hO1crQjCNFoM54Lg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.1 
MIME-Version: 1.0
Precedence: bulk

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 <bschubert@ddn.com>
> >=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