fuse: fix missing barriers in io-uring init
Status from this message: Applied, thanks.
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest3 patches 1 replyApplied
- v23 patches 4 repliesSuperseded
- v12 patches 4 repliesSuperseded
Patches in v3 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | fuse: fix missing barrier when checking io-uring readinessfs/ | +7 | 0 replies | |
| 2/3 | fuse: use release/acquire for fch->initializedfs/ fs/ fs/ | +11 | 0 replies | |
| 3/3 | fuse: publish io-uring queues with release semanticsfs/ | +11 | 0 replies |
Reviews trailers per patch
2 of 3 patches have a Reviewed-by or Acked-by.
| Patch | Bernd Schubert |
|---|---|
| 1/3 | R-b |
| 2/3 | |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v3 0/3] fuse: fix missing barriers in io-uring init
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
---------
v2: https://lore.kernel.org/fuse-devel/[email protected]/
* Add Bernd's reviewed-bys
* Move deletion of unnecessary smp_rmb() in fuse_get_req from 2nd patch to 1st patch (Bernd)
* Add READ_ONCE for uniformity per Bernd's preference
v1: https://lore.kernel.org/fuse-devel/[email protected]/
* Fix some other pre-existing issues Sashiko found in response to v1
* Add patch for using releasing/acquire for fch->initialized to make things
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 | 24 ++++++++++++++---------- 3 files changed, 25 insertions(+), 19 deletions(-)
Signature · 1 line
2.52.0