From: Joanne Koong <joannelkoong@gmail.com>
To: miklos@szeredi.hu, bernd@bsbernd.com
Cc: fuse-devel@lists.linux.dev
Subject: [PATCH v2 0/3] fuse: fix missing barriers in io-uring init
Date: Wed, 15 Jul 2026 10:43:02 -0700 [thread overview]
Message-ID: <20260715174305.336261-1-joannelkoong@gmail.com> (raw)
These are pre-existing issues Sashiko reported [1] on the fuse zerocopy
series.
[1] https://sashiko.dev/#/patchset/20260630211436.2062816-1-joannelkoong%40gmail.com
Changelog
---------
v1: https://lore.kernel.org/fuse-devel/20260713175345.2542331-1-joannelkoong@gmail.com/
* Fix some other pre-existing issues Sashiko found in response to v1
* Add patch for using releasing/acquire for fch->initialized to make things
simpler
Joanne Koong (3):
fuse: fix missing barrier when checking io-uring readiness
fuse: use release/acquire for fch->initialized
fuse: publish io-uring queues with release semantics
fs/fuse/cuse.c | 3 ++-
fs/fuse/dev.c | 17 +++++++++--------
fs/fuse/dev_uring.c | 18 +++++++++++-------
3 files changed, 22 insertions(+), 16 deletions(-)
--
2.52.0
next reply other threads:[~2026-07-15 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 17:43 Joanne Koong [this message]
2026-07-15 17:43 ` [PATCH v2 1/3] fuse: fix missing barrier when checking io-uring readiness Joanne Koong
2026-07-15 22:26 ` Bernd Schubert
2026-07-16 18:17 ` Joanne Koong
2026-07-15 17:43 ` [PATCH v2 2/3] fuse: use release/acquire for fch->initialized Joanne Koong
2026-07-15 17:43 ` [PATCH v2 3/3] fuse: publish io-uring queues with release semantics Joanne Koong
2026-07-15 22:54 ` Bernd Schubert
2026-07-16 18:21 ` Joanne Koong
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=20260715174305.336261-1-joannelkoong@gmail.com \
--to=joannelkoong@gmail.com \
--cc=bernd@bsbernd.com \
--cc=fuse-devel@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox