From: "Darrick J. Wong" <djwong@kernel.org>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
linux-fsdevel@vger.kernel.org, Bernd Schubert <bernd@bsbernd.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3 1/7] fuse: abort on fatal signal during sync init
Date: Mon, 23 Mar 2026 10:53:21 -0700 [thread overview]
Message-ID: <20260323175321.GB6202@frogsfrogsfrogs> (raw)
In-Reply-To: <CAJnrk1ZCLS4BhGJm7y4HC07tvAL-KHeU_B-0ep_1r9kaaf1Lnw@mail.gmail.com>
On Mon, Mar 16, 2026 at 11:48:09AM -0700, Joanne Koong wrote:
> On Mon, Mar 16, 2026 at 9:53 AM Miklos Szeredi <mszeredi@redhat.com> wrote:
> >
> > When sync init is used and the server exits for some reason (error, crash)
> > while processing FUSE_INIT, the filesystem creation will hang. The reason
> > is that while all other threads will exit, the mounting thread (or process)
> > will keep the device fd open, which will prevent an abort from happening.
> >
> > This is a regression from the async mount case, where the mount was done
> > first, and the FUSE_INIT processing afterwards, in which case there's no
> > such recursive syscall keeping the fd open.
> >
> > Fixes: dfb84c330794 ("fuse: allow synchronous FUSE_INIT")
> > Cc: stable@vger.kernel.org # v6.18
> > Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
>
> LGTM but left a comment below
>
> Reviewed-by: Joanne Koong <joannelkoong@gmail.com>
>
> > ---
> > fs/fuse/dev.c | 6 +++++-
> > fs/fuse/fuse_i.h | 1 +
> > fs/fuse/inode.c | 1 +
> > 3 files changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
> > index 2c16b94357d5..f0631c48abef 100644
> > --- a/fs/fuse/dev.c
> > +++ b/fs/fuse/dev.c
> > @@ -576,6 +576,9 @@ static void request_wait_answer(struct fuse_req *req)
> > removed = fuse_remove_pending_req(req, &fiq->lock);
> > if (removed)
> > return;
> > +
> > + if (req->args->abort_on_kill)
> > + fuse_abort_conn(fc);
>
> Maybe more straightforward to move this logic a few lines above? eg
>
> @@ -570,6 +570,11 @@ static void request_wait_answer(struct fuse_req *req)
> /* Only fatal signals may interrupt this */
> err = wait_event_killable(req->waitq,
> test_bit(FR_FINISHED, &req->flags));
> if (!err)
> return;
>
> + if (req->args->abort_on_kill) {
> + fuse_abort_conn(fc);
> + return;
> + }
Either's fine with me -- AFAICT it doesn't matter if we just abort the
connection without fiddling with the request in which case FUSE_INIT
fails with ECONNABORTED; or we try to remove it and end up cancelling it
with EINTR. Either way the connection aborts, the mount stops working,
and the fuse server is gone.
I like this fix much better :)
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
>
> Thanks,
> Joanne
>
> > }
> >
> > /*
> > @@ -676,7 +679,8 @@ ssize_t __fuse_simple_request(struct mnt_idmap *idmap,
> > fuse_force_creds(req);
> >
> > __set_bit(FR_WAITING, &req->flags);
> > - __set_bit(FR_FORCE, &req->flags);
> > + if (!args->abort_on_kill)
> > + __set_bit(FR_FORCE, &req->flags);
> > } else {
> > WARN_ON(args->nocreds);
> > req = fuse_get_req(idmap, fm, false);
> > diff --git a/fs/fuse/fuse_i.h b/fs/fuse/fuse_i.h
> > index 7f16049387d1..23a241f18623 100644
> > --- a/fs/fuse/fuse_i.h
> > +++ b/fs/fuse/fuse_i.h
> > @@ -345,6 +345,7 @@ struct fuse_args {
> > bool is_ext:1;
> > bool is_pinned:1;
> > bool invalidate_vmap:1;
> > + bool abort_on_kill:1;
> > struct fuse_in_arg in_args[4];
> > struct fuse_arg out_args[2];
> > void (*end)(struct fuse_mount *fm, struct fuse_args *args, int error);
> > diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
> > index e57b8af06be9..84f78fb89d35 100644
> > --- a/fs/fuse/inode.c
> > +++ b/fs/fuse/inode.c
> > @@ -1551,6 +1551,7 @@ int fuse_send_init(struct fuse_mount *fm)
> > int err;
> >
> > if (fm->fc->sync_init) {
> > + ia->args.abort_on_kill = true;
> > err = fuse_simple_request(fm, &ia->args);
> > /* Ignore size of init reply */
> > if (err > 0)
> > --
> > 2.53.0
> >
> >
>
next prev parent reply other threads:[~2026-03-23 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260316165320.3245526-1-mszeredi@redhat.com>
2026-03-16 16:53 ` [PATCH v3 1/7] fuse: abort on fatal signal during sync init Miklos Szeredi
2026-03-16 18:48 ` Joanne Koong
2026-03-23 17:53 ` Darrick J. Wong [this message]
2026-03-17 20:19 ` Bernd Schubert
2026-03-18 9:33 ` Miklos Szeredi
2026-03-23 14:19 ` 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=20260323175321.GB6202@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bernd@bsbernd.com \
--cc=joannelkoong@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=stable@vger.kernel.org \
/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