From: Tycho Andersen <tycho@tycho.pizza>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: "Jürg Billeter" <j@bitron.ch>,
"Eric W. Biederman" <ebiederm@xmission.com>,
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: Tue, 29 Aug 2023 11:42:02 -0600 [thread overview]
Message-ID: <ZO4t6pnCokUoEsoi@tycho.pizza> (raw)
In-Reply-To: <CAJfpegt2WrKBswYgSzurNogLefO-vU6ZpbCkrDrjFL365kcsug@mail.gmail.com>
On Mon, Aug 21, 2023 at 05:31:48PM +0200, Miklos Szeredi wrote:
(Apologies for the delay, I have been away without cell signal for
some time.)
> > I think the idea is that they're saving snapshots of their own threads
> > to the fs for debugging purposes.
>
> This seems a fairly special situation. Have they (whoever they may
> be) thought about fixing this in their server?
Sorry, "we" here is some internal team that works for my employer
Netflix. We can't use imap clients on our corporate e-mails, whee.
> > Whether this is a sane thing to do or not, it doesn't seem like it
> > should deadlock pid ns destruction.
>
> True. So the suggested solution is to allow wait_event_killable() to
> return if a terminal signal is pending in the exiting state and only
> in that case turn the flush into a background request? That would
> still allow for regressions like the one reported, but that would be
> much less likely to happen in real life. Okay, I said this for the
> original solution as well, so this may turn out to be wrong as well.
I wonder if there's room here for a completion that doesn't use the
wait primitives. Something like an atomic + queuing in task_work()
would both fix this bug and not exhibit this regression, IIUC.
> Anyway, I'd prefer if this was fixed in the server code, as it looks
> fairly special and adding complexity to the kernel for this case might
> not be justifiable. But I'm also open to suggestions on fixing this
> in the kernel in a not too complex manner.
I don't think this is specific to the server-accessing-its-own-file
case. My reproducer uses that because I didn't quite understand the
bug fully at the time. I believe that *any* task that is killed with
an inflight fuse request will exhibit this. We have seen this fairly
rarely on another fuse fs we use throughout the fleet:
https://github.com/lxc/lxcfs and it doesn't really do anything
strange, and is mounted from the host's pid ns.
Tycho
next prev parent reply other threads:[~2023-08-29 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 6:03 [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush 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
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 [this message]
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=ZO4t6pnCokUoEsoi@tycho.pizza \
--to=tycho@tycho.pizza \
--cc=ebiederm@xmission.com \
--cc=j@bitron.ch \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).