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 E3633191; Tue, 8 Jul 2025 00:02:19 +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=1751932940; cv=none; b=rFzSEbfJniahAAsvZDMwcHjPdqLYSJ/H8wOgmGM/a1WyoA0o5kA9TXV/06AI1CYUPxqMq7mE/3MWkHd54sto5we4vPgCgOhsCitfXpchS/CUGptg7d8K1H//uQ/4+8vpeCVc5b39RT0/ZCEFkUDKyXUcSlNKTx75xPXTBWBSaRw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751932940; c=relaxed/simple; bh=t5zmAG5UEvVd4XtHi1/WfmDFoTa8UUYg8Lwk7/npk3w=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=o2X/iQPAZN9vvafP7lonKEbtUyns+amSQa8+xR7gTRalpRwsou2yQiARLL8vxwEV61/MZ6+QEvSZ37xg74tLcRgREknNYxTQMCOSAXoS8o453BqAmMePqUsS9tAh7fg5TwJIoCqy2qyE2vMk6Vf9cs4HlMD3haf39EZXDihJFH8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=pNGAtzut; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="pNGAtzut" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 46B14C4CEF1; Tue, 8 Jul 2025 00:02:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1751932939; bh=t5zmAG5UEvVd4XtHi1/WfmDFoTa8UUYg8Lwk7/npk3w=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=pNGAtzutSGSI+5bIJhYypmZDUmt9LdZkF5xEV5qZNofmWNSepe44I5Dn69u8Uzhdh C9sKubCf6ph512z8wQTMmI4UFeGEhpdZQpuENi2DhRtvSVOA+QoBw55820BCSBZ0VB JfwtmcSigjz1QeIk7HH1Mq2TxrqsqNj/K+ZgYSlxIT2dHo0zE1LQQA2rykfAsjWA4I tryCMH98jAg5OZ8aSpKgEGofXo+BRbbssF2rtlRrQXBYHVPl/xxwdyd5Yenm3frJiF a69nsERhDd3DzoXaIvTgwok1yJ7BtO28c81dFpomJFa51R2iGnXXHJLQtvdHABayJN emUf0wW1PVuTA== From: Sasha Levin To: patches@lists.linux.dev, stable@vger.kernel.org Cc: Laurent Vivier , Lei Yang , Xuan Zhuo , Jason Wang , "Michael S . Tsirkin" , Paolo Abeni , Sasha Levin , davem@davemloft.net, edumazet@google.com, kuba@kernel.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org Subject: [PATCH AUTOSEL 6.15 2/8] virtio_net: Enforce minimum TX ring size for reliability Date: Mon, 7 Jul 2025 20:02:09 -0400 Message-Id: <20250708000215.793090-2-sashal@kernel.org> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250708000215.793090-1-sashal@kernel.org> References: <20250708000215.793090-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 6.15.5 Content-Transfer-Encoding: 8bit From: Laurent Vivier [ Upstream commit 24b2f5df86aaebbe7bac40304eaf5a146c02367c ] The `tx_may_stop()` logic stops TX queues if free descriptors (`sq->vq->num_free`) fall below the threshold of (`MAX_SKB_FRAGS` + 2). If the total ring size (`ring_num`) is not strictly greater than this value, queues can become persistently stopped or stop after minimal use, severely degrading performance. A single sk_buff transmission typically requires descriptors for: - The virtio_net_hdr (1 descriptor) - The sk_buff's linear data (head) (1 descriptor) - Paged fragments (up to MAX_SKB_FRAGS descriptors) This patch enforces that the TX ring size ('ring_num') must be strictly greater than (MAX_SKB_FRAGS + 2). This ensures that the ring is always large enough to hold at least one maximally-fragmented packet plus at least one additional slot. Reported-by: Lei Yang Signed-off-by: Laurent Vivier Reviewed-by: Xuan Zhuo Acked-by: Jason Wang Link: https://patch.msgid.link/20250521092236.661410-4-lvivier@redhat.com Tested-by: Lei Yang Acked-by: Michael S. Tsirkin Signed-off-by: Paolo Abeni Signed-off-by: Sasha Levin --- **YES** This commit should be backported to stable kernel trees. Here's my extensive analysis: ## 1. **Critical Bug Fix** The commit fixes a severe bug where TX queues can become permanently stopped, causing complete network transmission failure. Looking at the code change, it adds a crucial validation in `virtnet_tx_resize()`: ```c if (ring_num <= MAX_SKB_FRAGS + 2) { netdev_err(vi->dev, "tx size (%d) cannot be smaller than %d\n", ring_num, MAX_SKB_FRAGS + 2); return -EINVAL; } ``` This prevents a configuration that would make the network interface essentially unusable. ## 2. **Root Cause Analysis** The bug occurs because the `tx_may_stop()` logic (used throughout virtio_net for flow control) stops the TX queue when free descriptors fall below `MAX_SKB_FRAGS + 2`. If the total ring size is not strictly greater than this threshold, the queue can: - Stop after transmitting just one packet - Never have enough free slots to wake up again - Result in a permanently stalled TX queue ## 3. **User Impact** This affects real users who: - Use virtio_net in virtualized environments (very common in cloud/VM deployments) - Configure TX ring sizes via ethtool or other management tools - May unknowingly set ring sizes that trigger this bug The commit message explicitly mentions a report from Lei Yang at Red Hat, indicating this was discovered through real-world usage. ## 4. **Minimal and Safe Fix** The fix is: - **Small**: Only 6 lines of code added - **Contained**: Only affects ring resize operations - **Safe**: Adds validation without changing existing behavior for valid configurations - **Clear**: Returns -EINVAL with a descriptive error message ## 5. **Meets Stable Criteria** According to stable kernel rules, this commit qualifies because it: - Fixes a bug that affects users (network stalls) - Is relatively small and contained - Has no major side effects - Doesn't introduce new features - Has been tested (by Lei Yang) and reviewed by maintainers (Jason Wang, Michael S. Tsirkin) ## 6. **Comparison with Similar Commits** Looking at the historical commits: - Similar commit #3 (virtio_net: ensure netdev_tx_reset_queue) was backported because it fixed TX queue handling issues - This commit is even more critical as it prevents complete TX failure - The fix is simpler than commit #3 (just validation vs. callback handling) ## 7. **No Architectural Changes** Unlike commits #1 and #2 which made architectural changes to ring sizing, this commit: - Only adds input validation - Doesn't change data structures - Doesn't modify existing workflows - Simply prevents an invalid configuration The fact that experienced maintainers like Jason Wang and Michael S. Tsirkin acked this change further supports its importance for stable backporting. This is a textbook example of a fix that should go to stable: it addresses a real bug with minimal risk. drivers/net/virtio_net.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c index e53ba600605a5..3054b2b4f6a0c 100644 --- a/drivers/net/virtio_net.c +++ b/drivers/net/virtio_net.c @@ -3481,6 +3481,12 @@ static int virtnet_tx_resize(struct virtnet_info *vi, struct send_queue *sq, { int qindex, err; + if (ring_num <= MAX_SKB_FRAGS + 2) { + netdev_err(vi->dev, "tx size (%d) cannot be smaller than %d\n", + ring_num, MAX_SKB_FRAGS + 2); + return -EINVAL; + } + qindex = sq - vi->sq; virtnet_tx_pause(vi, sq); -- 2.39.5