From: Jens Axboe <axboe@kernel.dk>
To: Hao-Yu Yang <naup96721@gmail.com>, linux-kernel@vger.kernel.org
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH v1] io_uring: fix dangling iovec after provided-buffer bundle grow failure
Date: Mon, 6 Jul 2026 10:19:10 -0600 [thread overview]
Message-ID: <717fd2f3-6493-4dc5-ba83-c8d2af278639@kernel.dk> (raw)
In-Reply-To: <20260705234534.768138-1-naup96721@gmail.com>
On 7/5/26 5:45 PM, Hao-Yu Yang wrote:
> diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
> index 3cd29477fff2..4055173e0c48 100644
> --- a/io_uring/kbuf.c
> +++ b/io_uring/kbuf.c
> @@ -256,6 +256,7 @@ static int io_ring_buffers_peek(struct io_kiocb *req, struct buf_sel_arg *arg,
> struct io_uring_buf_ring *br = bl->buf_ring;
> struct iovec *org_iovs = arg->iovs;
> struct iovec *iov = arg->iovs;
> + struct iovec *old = NULL;
> int nr_iovs = arg->nr_iovs;
> __u16 nr_avail, tail, head;
> struct io_uring_buf *buf;
> @@ -288,7 +289,7 @@ static int io_ring_buffers_peek(struct io_kiocb *req, struct buf_sel_arg *arg,
> if (unlikely(!iov))
> return -ENOMEM;
> if (arg->mode & KBUF_MODE_FREE)
> - kfree(arg->iovs);
> + old = arg->iovs;
> arg->iovs = iov;
> nr_iovs = nr_avail;
> } else if (nr_avail < nr_iovs) {
> @@ -318,6 +319,8 @@ static int io_ring_buffers_peek(struct io_kiocb *req, struct buf_sel_arg *arg,
> if (unlikely(!access_ok(iov->iov_base, len))) {
> if (arg->iovs != org_iovs)
> kfree(arg->iovs);
> + /* hand the still-live cached vec back to the owner */
> + arg->iovs = org_iovs;
> return -EFAULT;
> }
> iov++;
> @@ -330,6 +333,8 @@ static int io_ring_buffers_peek(struct io_kiocb *req, struct buf_sel_arg *arg,
> buf = io_ring_head_to_buf(br, ++head, bl->mask);
> } while (--nr_iovs);
>
> + kfree(old);
> +
> if (head == tail)
> req->flags |= REQ_F_BL_EMPTY;
Can't we just do the below, that seems a lot simpler?
diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
index 3cd29477fff2..3bb24d20c890 100644
--- a/io_uring/kbuf.c
+++ b/io_uring/kbuf.c
@@ -287,8 +287,6 @@ static int io_ring_buffers_peek(struct io_kiocb *req, struct buf_sel_arg *arg,
iov = kmalloc_objs(struct iovec, nr_avail);
if (unlikely(!iov))
return -ENOMEM;
- if (arg->mode & KBUF_MODE_FREE)
- kfree(arg->iovs);
arg->iovs = iov;
nr_iovs = nr_avail;
} else if (nr_avail < nr_iovs) {
@@ -330,6 +328,9 @@ static int io_ring_buffers_peek(struct io_kiocb *req, struct buf_sel_arg *arg,
buf = io_ring_head_to_buf(br, ++head, bl->mask);
} while (--nr_iovs);
+ if (arg->mode & KBUF_MODE_FREE)
+ kfree(org_iovs);
+
if (head == tail)
req->flags |= REQ_F_BL_EMPTY;
--
Jens Axboe
next prev parent reply other threads:[~2026-07-06 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 23:45 [PATCH v1] io_uring: fix dangling iovec after provided-buffer bundle grow failure Hao-Yu Yang
2026-07-06 16:19 ` Jens Axboe [this message]
2026-07-06 16:56 ` Hao-Yu Yang
2026-07-06 16:20 ` Jens Axboe
2026-07-06 17:01 ` Hao-Yu Yang
2026-07-06 17:13 ` Jens Axboe
2026-07-06 17:34 ` Hao-Yu Yang
2026-07-06 17:39 ` Jens Axboe
2026-07-06 17:46 ` Hao-Yu Yang
2026-07-06 18:06 ` 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=717fd2f3-6493-4dc5-ba83-c8d2af278639@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naup96721@gmail.com \
/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