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/msg_ring: kill alloc_cache for io_kiocb allocations
Date: Fri, 19 Sep 2025 15:06:23 +0100 [thread overview]
Message-ID: <23a67fd6-0179-4578-82ef-cf796bea4346@gmail.com> (raw)
In-Reply-To: <0ee30a2f-4e36-4c0a-8e84-7da568da08d3@kernel.dk>
On 9/18/25 21:04, Jens Axboe wrote:
> A recent commit:
>
> fc582cd26e88 ("io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU")
>
> fixed an issue with not deferring freeing of io_kiocb structs that
I didn't care to mention before, but that patch was doing nothing
meaningful, adding a second RCU grace period rarely solves anything.
If you're curious what the problem most likely is, see
commit 569f5308e54352a12181cc0185f848024c5443e8
Author: Pavel Begunkov <asml.silence@gmail.com>
Date: Wed Aug 9 13:22:16 2023 +0100
io_uring: fix false positive KASAN warnings
--
Pavel Begunkov
next prev parent reply other threads:[~2025-09-19 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 20:04 [PATCH] io_uring/msg_ring: kill alloc_cache for io_kiocb allocations Jens Axboe
2025-09-19 14:06 ` Pavel Begunkov [this message]
2025-09-19 14:51 ` 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=23a67fd6-0179-4578-82ef-cf796bea4346@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