From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793210256; b=5F7sZ3Qxc2BNotQg/6jOdKp/zOYZzO0B0lRWELdPQrUdnmrPBlVpqwaRbXbFtKRDJ2lR sVG51/QANwy5wDBKeimo7YzpUCEmOMjS8kQEUBxjF63KT4Q/QrqVYNk3AStSb9PlM29Os TkecDZKqJBCaqBf6dH58Q8D+Wl9KDeZ6lATy7UyHVCEjXOyrWYTyLnQPtXpWLb5fLb+IK KUa5r/VvwSbheyKePbFCYQXl79UODRb1867U8WF5xNS7yAjJc0s+TwJ34lCaU8bg1azY6 tkmXwDuqxRv6+/Q3G8xNGRtqlvlA3D9Eim12AfJ/u0hpybZJG6wqSsXunCa+JfOnPkg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793210256; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: In-Reply-To:References:User-Agent:X-stable:X-Patchwork-Hint: MIME-Version:Content-Transfer-Encoding; bh=4o+HPqDj4dzFtJCYI+MB359F6BQJ6mjivOp5kZM3Pd8=; b=oYFRsP9CKxWy6YqAMsmg0uO7PuhPBj2yKNUhxpqZ4m6JOQ1mgupAZgX872LPyaCF4l+C 6vzAh3mv91p6oJ+WFE2yEhBK6L+00oD+iHLrUW8AgItbtV7U5Pi/V6l7qeK2hzgMU7vVT tME+wpv3gjd22QuB0N52vy/TgURyFhR+BpqzS6ETbjc0QOMJCl+4EPa4hK39cqF2zmEW9 8LZMm/OsLVSOFgb4fhUVJkBDDGD7JRSPYdsFx1lmFrFVkr+Ep06NBwLhewGnT4Ipnf6yU R+sqAnUJP6m0fCEE25X67iDxERlapptGI7ru20VL8HneCihQJXgi+CVdi7hRXb7zVMg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=sm9Gz1Zg; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E172F606A324; Wed, 28 Oct 2026 17:57:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=sm9Gz1Zg Received: by smtp.kernel.org (Postfix) with ESMTPSA id EE6FB1F01825; Wed, 28 Oct 2026 17:57:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1793210255; bh=4o+HPqDj4dzFtJCYI+MB359F6BQJ6mjivOp5kZM3Pd8=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=sm9Gz1ZgQgW3KMKYiXMcQNkyLm4lKrfqqwgufC7KqtNkyIIQ0SYYGORkBVGLQn+6o odQ+oQpftRKJfPxmW3iIH6BrvSYfChDKQdhYYj4fdDTA0RnEAMF+3xIyyRRNrelMFf 0Pt8Xjw0VjEq4w+cWu47X9scmJ6lSJ/spWjqtPhk= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, Josef Bacik , Jens Axboe Subject: [PATCH 6.6 130/168] io_uring: dont flood a cancelling task with task_work Date: Wed, 28 Oct 2026 18:01:06 +0100 Message-ID: <20261028165946.164090058@linuxfoundation.org> X-Mailer: git-send-email 2.56.0 In-Reply-To: <20261028165943.089486480@linuxfoundation.org> References: <20261028165943.089486480@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore X-Mailing-List: patches@lists.linux.dev List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 6.6-stable review patch. If anyone has any objections, please let me know. ------------------ From: Josef Bacik Commit 22e643e61b9b6299b42ff7d88bab48bccada8a5d upstream. io_ring_exit_work() asks each task which has used the ring to remove its tctx node, by task_work, and repeats that until the list is empty. io_tctx_exit_cb() doesn't touch the node while the task is in io_uring_cancel_generic(), which removes all the nodes at its end. So the work item queues the callback again as soon as it has completed, for nothing. That is more than a waste of time. task_work_run() only returns when it finds the list empty. If the rings are released from inside the cancellation, because requests of other rings held the last references to their files, up to 64 work items keep sending callbacks to the one task which is running them. It never finds the list empty, never gets back to the cancellation, the nodes stay, and so it goes on: a task with 60 pairs of rings which poll each other ran 280000 callbacks in 5 seconds, 20 seconds after exit_group(). It ends when all the senders happen to be late at the same time. Until then the task keeps a CPU and the work items busy. An exiting task can't be killed meanwhile. execve() cancels the requests in the same way, so a live task can get stuck there as well, for minutes. If it takes more than five, the work items run into the WARN_ON_ONCE(time_after(jiffies, timeout)) of io_ring_exit_work(). No privilege is needed for any of this. If the callback has met a task in cancellation, wait a little before it is sent again. Nobody has to wake the work item up for that: either the node is gone by then, or it is the turn of the next round. Fixes: d56d938b4bef ("io_uring: do ctx initiated file note removal") Assisted-by: LLM Signed-off-by: Josef Bacik Link: https://patch.msgid.link/20261015-b4-io-uring-fixes-v1-6-c1556f5d7bf5@toxicpanda.com Signed-off-by: Jens Axboe Signed-off-by: Greg Kroah-Hartman --- io_uring/io_uring.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) --- a/io_uring/io_uring.c +++ b/io_uring/io_uring.c @@ -3169,6 +3169,7 @@ struct io_tctx_exit { struct callback_head task_work; struct completion completion; struct io_ring_ctx *ctx; + bool in_cancel; }; static __cold void io_tctx_exit_cb(struct callback_head *cb) @@ -3183,7 +3184,8 @@ static __cold void io_tctx_exit_cb(struc * tctx can be NULL if the queueing of this task_work raced with * work cancelation off the exec path. */ - if (tctx && !atomic_read(&tctx->in_cancel)) + work->in_cancel = tctx && atomic_read(&tctx->in_cancel); + if (tctx && !work->in_cancel) io_uring_del_tctx_node((unsigned long)work->ctx); complete(&work->completion); } @@ -3277,6 +3279,14 @@ static __cold void io_ring_exit_work(str * wait is marked as interruptible. */ wait_for_completion_interruptible(&exit.completion); + /* + * The task removes the node when it is done with its + * cancellation. Give it the time for that: it doesn't get back + * to it as long as it finds new task_work each time it has run + * the old one, and we may be one of many who send it. + */ + if (exit.in_cancel) + schedule_timeout_idle(HZ / 20); mutex_lock(&ctx->uring_lock); } mutex_unlock(&ctx->uring_lock);