From: "Jürg Billeter" <j@bitron.ch>
To: Miklos Szeredi <miklos@szeredi.hu>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: Tycho Andersen <tycho@tycho.pizza>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush
Date: Mon, 14 Aug 2023 08:03:29 +0200 [thread overview]
Message-ID: <4f66cded234462964899f2a661750d6798a57ec0.camel@bitron.ch> (raw)
Since v6.3-rc1 commit 5a8bee63b1 ("fuse: in fuse_flush only wait if
someone wants the return code") `fput()` is called asynchronously if a
file is closed as part of a process exiting, i.e., if there was no
explicit `close()` before exit.
If the file was open for writing, also `put_write_access()` is called
asynchronously as part of the async `fput()`.
If that newly written file is an executable, attempting to `execve()`
the new file can fail with `ETXTBSY` if it's called after the writer
process exited but before the async `fput()` has run.
I've confirmed that this issue is absent in v6.2 and reverting
5a8bee63b1 on top of v6.4.10 fixes the regression.
#regzbot introduced: 5a8bee63b1
Jürg
next reply other threads:[~2023-08-14 6:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 6:03 Jürg Billeter [this message]
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
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=4f66cded234462964899f2a661750d6798a57ec0.camel@bitron.ch \
--to=j@bitron.ch \
--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®