From: Joanne Koong <joannelkoong@gmail.com>
To: axboe@kernel.dk
Cc: csander@purestorage.com, asml.silence@gmail.com,
io-uring@vger.kernel.org
Subject: [PATCH v1 3/5] io_uring/rsrc: allow buffer release callback to be optional
Date: Mon, 23 Mar 2026 17:10:05 -0700 [thread overview]
Message-ID: <20260324001007.1144471-4-joannelkoong@gmail.com> (raw)
In-Reply-To: <20260324001007.1144471-1-joannelkoong@gmail.com>
This is a preparatory patch for supporting kernel-populated buffers in
fuse io-uring, which does not need a release callback.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
Reviewed-by: Caleb Sander Mateos <csander@purestorage.com>
---
io_uring/rsrc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/io_uring/rsrc.c b/io_uring/rsrc.c
index 1902ab7941ac..3a89eec9265f 100644
--- a/io_uring/rsrc.c
+++ b/io_uring/rsrc.c
@@ -133,7 +133,8 @@ static void io_buffer_unmap(struct io_ring_ctx *ctx, struct io_mapped_ubuf *imu)
if (imu->acct_pages)
io_unaccount_mem(ctx->user, ctx->mm_account, imu->acct_pages);
- imu->release(imu->priv);
+ if (imu->release)
+ imu->release(imu->priv);
io_free_imu(ctx, imu);
}
--
2.52.0
next prev parent reply other threads:[~2026-03-24 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 0:10 [PATCH v1 0/5] io_uring: extend bvec registration and add mem region lookup Joanne Koong
2026-03-24 0:10 ` [PATCH v1 1/5] io_uring/rsrc: rename io_buffer_register_bvec()/io_buffer_unregister_bvec() Joanne Koong
2026-03-24 0:10 ` [PATCH v1 2/5] io_uring/rsrc: split io_buffer_register_request() logic Joanne Koong
2026-03-24 18:13 ` Joanne Koong
2026-03-24 0:10 ` Joanne Koong [this message]
2026-03-24 0:10 ` [PATCH v1 4/5] io_uring/rsrc: add io_buffer_register_bvec() Joanne Koong
2026-03-24 0:10 ` [PATCH v1 5/5] io_uring/rsrc: add io_uring_registered_mem_region_get() 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=20260324001007.1144471-4-joannelkoong@gmail.com \
--to=joannelkoong@gmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@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