From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5B3391AB521; Mon, 14 Oct 2024 14:42:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728916946; cv=none; b=iw96sk+p7Gj5mFLyqFha7Ij6tuh6FmbyjxRJxK78v+bozrhXDLtsvABt8AVPRdozykblR930AZAKriCtbH5NhWKP+QWN6N02HT2ik8QHuvcZSADsJtet71jcpUMAqJNP4jX4ku4eCHzmfO+sI/SnpcToathvFOO3ZAE3psPiAtI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728916946; c=relaxed/simple; bh=P2/nVTV2sMZa1dEwF9uRNa5XtbJX/e+KKlF8iUlh6bE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=sP8SwXBn9NiHjtfwvVgAhcgkxooqFiBbh7zXj/MGoqxYz7E6JPlOtCVq0BYEmHVeNYopftLUz40yaM8WLfUpAvmfnX8AfnRBsLHcgEsgiyef8mXx++fN50+PchqtpP9+xO7tz6j7+feuwk/S/pDJNYwdmN2KUkNI9LQubfuyY2I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=Qa//XmO/; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="Qa//XmO/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C6E2EC4CEC3; Mon, 14 Oct 2024 14:42:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1728916946; bh=P2/nVTV2sMZa1dEwF9uRNa5XtbJX/e+KKlF8iUlh6bE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Qa//XmO/OFzTCd95QejGllsp+9T3KYvIo4EZAnLVY0z+cTDZqKmZr18yrikuiR/3x qSNY6CGE27zgdOAYTuIRf8fvaZkQckZGijylTTI9w7Q7hRqI9gDWEh/nkmgRrEyV9V 7FU3yPa7PBBToJgRcqGrd3FOMI67HCF3kXsZuJK4= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, syzbot+5fca234bd7eb378ff78e@syzkaller.appspotmail.com, Jens Axboe , Sasha Levin Subject: [PATCH 6.6 078/213] io_uring: check if we need to reschedule during overflow flush Date: Mon, 14 Oct 2024 16:19:44 +0200 Message-ID: <20241014141046.025015422@linuxfoundation.org> X-Mailer: git-send-email 2.47.0 In-Reply-To: <20241014141042.954319779@linuxfoundation.org> References: <20241014141042.954319779@linuxfoundation.org> User-Agent: quilt/0.67 X-stable: review X-Patchwork-Hint: ignore Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 6.6-stable review patch. If anyone has any objections, please let me know. ------------------ From: Jens Axboe [ 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 Signed-off-by: Sasha Levin --- io_uring/io_uring.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c index 7b0a100e1139a..39d8d1fc5c2bc 100644 --- a/io_uring/io_uring.c +++ b/io_uring/io_uring.c @@ -701,6 +701,21 @@ static void __io_cqring_overflow_flush(struct io_ring_ctx *ctx) memcpy(cqe, &ocqe->cqe, cqe_size); 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_cq_unlock_post(ctx); + mutex_unlock(&ctx->uring_lock); + cond_resched(); + mutex_lock(&ctx->uring_lock); + io_cq_lock(ctx); + } } if (list_empty(&ctx->cq_overflow_list)) { -- 2.43.0