public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring <io-uring@vger.kernel.org>
Subject: Re: [PATCH] io_uring/kbuf: fix memory leak if io_buffer_add_list fails
Date: Thu, 5 Feb 2026 18:11:31 +0000	[thread overview]
Message-ID: <1af36abc-4956-4461-9a06-50fd120c04d0@gmail.com> (raw)
In-Reply-To: <9f658484-0a25-49a1-ae27-d2ffa0f3132f@kernel.dk>

On 2/5/26 15:43, Jens Axboe wrote:
> io_register_pbuf_ring() ignores the return value of io_buffer_add_list(),
> which can fail if xa_store() returns an error (e.g., -ENOMEM). When this
> happens, the function returns 0 (success) to the caller, but the
> io_buffer_list structure is neither added to the xarray nor freed.
> 
> In practice this requires failure injection to hit, hence not a real
> issue. But it should get fixed up none the less.
> 
> Fixes: ef62de3c4ad5 ("io_uring/kbuf: use region api for pbuf rings")

Looks like that patch just moved the call, and the tag should be
more like:

c7fb19428d67d ("io_uring: add support for ring mapped supplied buffers")

> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> 
> ---
> 
> diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
> index 796d131107dd..67d4fe576473 100644
> --- a/io_uring/kbuf.c
> +++ b/io_uring/kbuf.c
> @@ -669,8 +669,9 @@ int io_register_pbuf_ring(struct io_ring_ctx *ctx, void __user *arg)
>   	bl->buf_ring = br;
>   	if (reg.flags & IOU_PBUF_RING_INC)
>   		bl->flags |= IOBL_INC;
> -	io_buffer_add_list(ctx, bl, reg.bgid);
> -	return 0;
> +	ret = io_buffer_add_list(ctx, bl, reg.bgid);
> +	if (!ret)
> +		return 0;
>   fail:
>   	io_free_region(ctx->user, &bl->region);
>   	kfree(bl);
> 

-- 
Pavel Begunkov


  reply	other threads:[~2026-02-05 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 15:43 [PATCH] io_uring/kbuf: fix memory leak if io_buffer_add_list fails Jens Axboe
2026-02-05 18:11 ` Pavel Begunkov [this message]
2026-02-05 18:13   ` Jens Axboe

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=1af36abc-4956-4461-9a06-50fd120c04d0@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --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