From: "Jürg 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
Subject: Re: [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush
Date: Mon, 14 Aug 2023 14:38:44 +0200 [thread overview]
Message-ID: <e7499d0942a4489086c803dcdf1a5bb4317e973e.camel@bitron.ch> (raw)
In-Reply-To: <CAJfpegtUVUDac5_Y7BMJvCHfeicJkNxca2hO1crQjCNFoM54Lg@mail.gmail.com>
On Mon, 2023-08-14 at 14:28 +0200, Miklos Szeredi wrote:
> On Mon, 14 Aug 2023 at 14:07, Bernd Schubert
> > fuse: Avoid flush for O_RDONLY
> >
> > From: Bernd Schubert <bschubert@ddn.com>
> >
> > A file opened in read-only moded does not have data to be
> > flushed, so no need to send flush at all.
> >
> > This also mitigates -EBUSY for executables, which is due to
> > async flush with commit 5a8bee63b1.
>
> Does it? If I read the bug report correctly, it's the write case that
> 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ürg
next prev parent reply other threads:[~2023-08-14 12:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 6:03 Jürg Billeter
2023-08-14 11:02 ` Miklos Szeredi
2023-08-14 12:07 ` Bernd Schubert
2023-08-14 12:28 ` Miklos Szeredi
2023-08-14 12:38 ` Jürg Billeter [this message]
2023-08-14 13:44 ` Bernd Schubert
2023-08-14 14:00 ` Tycho Andersen
2023-08-14 14:35 ` Miklos Szeredi
2023-08-14 22:36 ` Tycho Andersen
2023-08-21 14:24 ` Miklos Szeredi
2023-08-21 15:02 ` Tycho Andersen
2023-08-21 15:31 ` Miklos Szeredi
2023-08-29 17:42 ` Tycho Andersen
2023-08-14 21:34 ` Bernd Schubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7499d0942a4489086c803dcdf1a5bb4317e973e.camel@bitron.ch \
--to=j@bitron.ch \
--cc=bernd.schubert@fastmail.fm \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=regressions@lists.linux.dev \
--cc=tycho@tycho.pizza \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®