From: Anvik Loitongbam <permissiontogallop@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
Olivier Langlois <olivier@trillion01.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
Anvik Loitongbam <permissiontogallop@gmail.com>
Subject: [PATCH v2] io_uring/napi: clean up list traversal with list_for_each_entry_safe()
Date: Thu, 29 Oct 2026 20:17:45 +0530 [thread overview]
Message-ID: <20261029144745.23792-1-permissiontogallop@gmail.com> (raw)
Switch both loops to the standard list_for_each_entry_safe() pattern and
remove the explanatory comment.
Signed-off-by: Anvik Loitongbam <permissiontogallop@gmail.com>
---
v2:
- Resend as a cleanup rather than a PREEMPT_RT UAF fix.
io_uring/napi.c | 14 ++++----------
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/io_uring/napi.c b/io_uring/napi.c
index 7e698720cd51..d299c89cfc3d 100644
--- a/io_uring/napi.c
+++ b/io_uring/napi.c
@@ -110,16 +110,10 @@ static int __io_napi_del_id(struct io_ring_ctx *ctx, unsigned int napi_id)
static void __io_napi_remove_stale(struct io_ring_ctx *ctx)
{
- struct io_napi_entry *e;
+ struct io_napi_entry *e, *next;
guard(spinlock)(&ctx->napi_lock);
- /*
- * list_for_each_entry_safe() is not required as long as:
- * 1. list_del_rcu() does not reset the deleted node next pointer
- * 2. kfree_rcu() delays the memory freeing until the next quiescent
- * state
- */
- list_for_each_entry(e, &ctx->napi_list, list) {
+ list_for_each_entry_safe(e, next, &ctx->napi_list, list) {
if (time_after(jiffies, READ_ONCE(e->timeout))) {
list_del_rcu(&e->list);
hash_del_rcu(&e->node);
@@ -264,10 +258,10 @@ void io_napi_init(struct io_ring_ctx *ctx)
*/
void io_napi_free(struct io_ring_ctx *ctx)
{
- struct io_napi_entry *e;
+ struct io_napi_entry *e, *next;
guard(spinlock)(&ctx->napi_lock);
- list_for_each_entry(e, &ctx->napi_list, list) {
+ list_for_each_entry_safe(e, next, &ctx->napi_list, list) {
hash_del_rcu(&e->node);
kfree_rcu(e, rcu);
}
--
next reply other threads:[~2026-10-29 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 14:47 Anvik Loitongbam [this message]
2026-10-29 15:34 ` 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=20261029144745.23792-1-permissiontogallop@gmail.com \
--to=permissiontogallop@gmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivier@trillion01.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
all inboxes | Powered by JetHome®