From: Nitesh Shetty <nj.shetty@samsung.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: Re: [PATCH] io_uring/rw: free potentially allocated iovec on cache put failure
Date: Mon, 19 Jan 2026 14:29:18 +0530 [thread overview]
Message-ID: <20260119085918.5ototxnmakj7qlf7@green245.gost> (raw)
In-Reply-To: <d98a65d5-3881-4029-8c2c-bc2dfb34c18e@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
On 18/01/26 08:15PM, Jens Axboe wrote:
>If a read/write request goes through io_req_rw_cleanup() and has an
>allocated iovec attached and fails to put to the rw_cache, then it may
>end up with an unaccounted iovec pointer. Have io_rw_recycle() return
>whether it recycled the request or not, and use that to gauge whether to
>free a potential iovec or not.
>
>Signed-off-by: Jens Axboe <axboe@kernel.dk>
>
Reviewed-by: Nitesh Shetty <nj.shetty@samsung.com>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2026-01-19 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260119090328epcas5p3457c9dbb7c69f70a3988e5f8f77c51d7@epcas5p3.samsung.com>
2026-01-19 3:15 ` [PATCH] io_uring/rw: free potentially allocated iovec on cache put failure Jens Axboe
2026-01-19 8:59 ` Nitesh Shetty [this message]
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=20260119085918.5ototxnmakj7qlf7@green245.gost \
--to=nj.shetty@samsung.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