All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joanne Koong <joannelkoong@gmail.com>
To: miklos@szeredi.hu
Cc: fuse-devel@lists.linux.dev, bernd@bsbernd.com, ali@ddn.com,
	horst@birthelmer.de
Subject: [PATCH v1 0/3] fuse: fix io-uring abort races and cancel null deref
Date: Thu, 14 May 2026 21:55:38 -0700	[thread overview]
Message-ID: <20260515045541.1171335-1-joannelkoong@gmail.com> (raw)

Patches 1 and 2 fix races between fuse uring ring creation and abort and
registration and abort that can result in indefinite hangs during unmount and
leaked resources.

Patch 3 fixes fuse_uring_cancel() moving cancelled entries (which have no
fuse_req) to ent_in_userspace, which can crash ent_list_request_expired().
It also removes the queue_refs > 0 gate in fuse_uring_abort() so that
request flushing always happens, since cancel now decrements queue_refs
directly.

[1] https://lore.kernel.org/linux-fsdevel/adiiTGjP1tqZfIrI@fedora/

Joanne Koong (3):
  fuse: fix race between ring creation and connection abortion
  fuse: fix race between registration and connection abortion
  fuse: fix moving cancelled entry to ent_in_userspace list

 fs/fuse/dev_uring.c   | 32 ++++++++++++++++++++++++--------
 fs/fuse/dev_uring_i.h |  6 +++---
 2 files changed, 27 insertions(+), 11 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-05-15  4:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  4:55 Joanne Koong [this message]
2026-05-15  4:55 ` [PATCH v1 1/3] fuse: fix race between ring creation and connection abortion Joanne Koong
2026-05-15 11:57   ` Bernd Schubert
2026-05-15 20:49     ` Joanne Koong
2026-05-15  4:55 ` [PATCH v1 2/3] fuse: fix race between registration " Joanne Koong
2026-05-15 11:59   ` Bernd Schubert
2026-05-15  4:55 ` [PATCH v1 3/3] fuse: fix moving cancelled entry to ent_in_userspace list Joanne Koong
2026-05-15 11:10   ` Bernd Schubert
2026-05-15 21:11     ` Joanne Koong
2026-05-15 22:27       ` 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=20260515045541.1171335-1-joannelkoong@gmail.com \
    --to=joannelkoong@gmail.com \
    --cc=ali@ddn.com \
    --cc=bernd@bsbernd.com \
    --cc=fuse-devel@lists.linux.dev \
    --cc=horst@birthelmer.de \
    --cc=miklos@szeredi.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.