From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Li Xiasong <lixiasong1@huawei.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
yuehaibing@huawei.com, zhangchangzhong@huawei.com,
weiyongjun1@huawei.com
Subject: Re: [PATCH net-next] net: core: avoid WARN_ONCE for stale RX queue mappings
Date: Tue, 11 Aug 2026 14:58:31 +0800 [thread overview]
Message-ID: <156834bb-8e40-496e-9443-9d515fa18eab@linux.dev> (raw)
In-Reply-To: <20260810125029.1567742-1-lixiasong1@huawei.com>
On 8/10/26 8:50 PM, Li Xiasong wrote:
> An skb may retain its recorded RX queue index while a network device
> reduces its number of active RX queues. For example, when a TUN queue
> is detached, queued skbs can still carry the queue's previous index.
>
> Both get_rps_cpu() and netif_get_rxqueue() validate the index before
> accessing the RX queue array. They safely fall back to local processing
> or the first RX queue, so an invalid index does not cause an
> out-of-bounds access.
>
> Using WARN_ONCE() for this recoverable condition can unnecessarily
> panic systems with panic_on_warn enabled. Replace it with
> netdev_warn_once() to retain the diagnostic without emitting a WARN
> splat.
>
> Signed-off-by: Li Xiasong <lixiasong1@huawei.com>
Reviewed-by: Jiayuan Chen <jiayuan.chen@linux.dev>
I just run ethtool -L rx 2 on my host and got such message..
------------[ cut here ]------------
veth1 received packet on queue 2, but number of RX queues is 2
WARNING: net/core/dev.c:5132 at get_rps_cpu+0x1d1/0x4b0, CPU#2:
kworker/2:1/59
<TASK>
netif_rx_internal+0xa1/0x120
__netif_rx+0x19/0xc0
veth_xmit+0x267/0x360
dev_hard_start_xmit+0x64/0x1d0
__dev_queue_xmit+0x803/0x1190
ip6_finish_output2+0x2d2/0x700
ip6_finish_output+0xfb/0x3c0
ip6_output+0x81/0x180
NF_HOOK.constprop.0+0x4f/0x110
mld_sendpack+0x1bf/0x290
mld_ifc_work+0x19a/0x400
process_one_work+0x19c/0x3e0
worker_thread+0x1a8/0x330
kthread+0xfb/0x140
ret_from_fork+0x1c1/0x2c0
ret_from_fork_asm+0x1a/0x30
</TASK>
---[ end trace 0000000000000000 ]---
> ---
> net/core/dev.c | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/net/core/dev.c b/net/core/dev.c
> index af260ff5462a..5db98b0a853f 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -5126,10 +5126,11 @@ static int get_rps_cpu(struct net_device *dev, struct sk_buff *skb,
> u16 index = skb_get_rx_queue(skb);
>
> if (unlikely(index >= dev->real_num_rx_queues)) {
> - WARN_ONCE(dev->real_num_rx_queues > 1,
> - "%s received packet on queue %u, but number "
> - "of RX queues is %u\n",
> - dev->name, index, dev->real_num_rx_queues);
> + if (dev->real_num_rx_queues > 1)
> + netdev_warn_once(dev,
> + "received packet on queue %u, but number "
> + "of RX queues is %u\n",
> + index, dev->real_num_rx_queues);
> goto done;
> }
> rxqueue += index;
> @@ -5443,11 +5444,11 @@ static struct netdev_rx_queue *netif_get_rxqueue(struct sk_buff *skb)
> u16 index = skb_get_rx_queue(skb);
>
> if (unlikely(index >= dev->real_num_rx_queues)) {
> - WARN_ONCE(dev->real_num_rx_queues > 1,
> - "%s received packet on queue %u, but number "
> - "of RX queues is %u\n",
> - dev->name, index, dev->real_num_rx_queues);
> -
> + if (dev->real_num_rx_queues > 1)
> + netdev_warn_once(dev,
> + "received packet on queue %u, but number "
> + "of RX queues is %u\n",
> + index, dev->real_num_rx_queues);
> return rxqueue; /* Return first rxqueue */
> }
> rxqueue += index;
prev parent reply other threads:[~2026-08-11 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 12:50 [PATCH net-next] net: core: avoid WARN_ONCE for stale RX queue mappings Li Xiasong
2026-08-11 6:58 ` Jiayuan Chen [this message]
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=156834bb-8e40-496e-9443-9d515fa18eab@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiasong1@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=weiyongjun1@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.