
From: Jens Axboe <axboe@kernel.dk> stable inclusion from stable-v6.6.57 commit f4ce3b5d26ce149e77e6b8e8f2058aa80e5b034e category: bugfix bugzilla: https://gitee.com/src-openeuler/kernel/issues/IAYRF9 CVE: CVE-2024-50060 Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=... -------------------------------- [ Upstream commit eac2ca2d682f94f46b1973bdf5e77d85d77b8e53 ] In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it'll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while. Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There's no state to maintain here as overflows always prune from head-of-list, hence it's fine to drop and reacquire the locks at the end of the loop. Link: https://lore.kernel.org/io-uring/66ed061d.050a0220.29194.0053.GAE@google.com... Reported-by: syzbot+5fca234bd7eb378ff78e@syzkaller.appspotmail.com Signed-off-by: Jens Axboe <axboe@kernel.dk> Signed-off-by: Sasha Levin <sashal@kernel.org> Conflicts: io_uring/io_uring.c [Context conflicts because there are no commits: 253993210bd8 ("io_uring: introduce locking helpers for CQE posting") 1b346e4aa8e7 ("io_uring: don't check overflow flush failures") etc.] Signed-off-by: Baokun Li <libaokun1@huawei.com> --- io_uring/io_uring.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c index 8cd66544fce0..efcaf9e74c83 100644 --- a/io_uring/io_uring.c +++ b/io_uring/io_uring.c @@ -1676,6 +1676,23 @@ static bool __io_cqring_overflow_flush(struct io_ring_ctx *ctx, bool force) posted = true; list_del(&ocqe->list); kfree(ocqe); + + /* + * For silly syzbot cases that deliberately overflow by huge + * amounts, check if we need to resched and drop and + * reacquire the locks if so. Nothing real would ever hit this. + * Ideally we'd have a non-posting unlock for this, but hard + * to care for a non-real case. + */ + if (need_resched()) { + io_commit_cqring(ctx); + spin_unlock(&ctx->completion_lock); + io_cqring_ev_posted(ctx); + mutex_unlock(&ctx->uring_lock); + cond_resched(); + mutex_lock(&ctx->uring_lock); + spin_lock(&ctx->completion_lock); + } } all_flushed = list_empty(&ctx->cq_overflow_list); -- 2.46.1