From: Simon Horman <horms@kernel.org>
To: Mengyuan Lou <mengyuanlou@net-swift.com>
Cc: netdev@vger.kernel.org, jiawenwu@trustnetic.com,
duanqiangwen@net-swift.com, linglingzhang@net-swift.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net v2] net: libwx: protect ring accesses with RCU
Date: Thu, 20 Aug 2026 19:29:43 +0100 [thread overview]
Message-ID: <20260820182943.GD265046@horms.kernel.org> (raw)
In-Reply-To: <20260818100841.37483-1-mengyuanlou@net-swift.com>
On Tue, Aug 18, 2026 at 06:08:41PM +0800, Mengyuan Lou wrote:
> During queue teardown or channel reconfiguration (e.g. via ethtool -L),
> ring pointers in wx->rx_ring[] and wx->tx_ring[] can be cleared to NULL
> and freed asynchronously via kfree_rcu().
>
> Concurrency between interface reconfiguration and background tasks
> (such as service tasks or dev_get_stats) can result in NULL pointer
> dereferences or Use-After-Free (UAF) issues when accessing per-queue
> structures. Specifically:
> 1. wx_update_stats() accesses per-queue Rx, RSC, and Tx rings without
> RCU read-side protection, and lacked NULL checks in the RSC
> accumulation loop.
> 2. wx_update_xoff_rx_lfc() walks wx->tx_ring[] and modifies ring->state
> without RCU protection or NULL checks, risking a kernel panic when
> flow control pause frames are received during queue teardown.
> 3. Queue assignment in wx_alloc_q_vector() used plain stores without
> release barrier semantics needed for lockless RCU readers.
>
> Fix these by:
> 1. Enclosing queue statistics gathering and wx_update_xoff_rx_lfc() inside
> an rcu_read_lock() / rcu_read_unlock() section in wx_update_stats().
> 2. Adding READ_ONCE() and NULL checks when traversing wx->rx_ring[] and
> wx->tx_ring[] in wx_update_stats() and wx_update_xoff_rx_lfc().
> 3. Using rcu_assign_pointer() when publishing or clearing ring pointers in
> wx_alloc_q_vector() and wx_free_q_vector().
>
> Fixes: 46b92e10d631 ("net: libwx: support hardware statistics")
> Signed-off-by: Mengyuan Lou <mengyuanlou@net-swift.com>
> ---
> Changelogs:
> v2:
> - Moved rcu_read_unlock() after wx_update_xoff_rx_lfc() in wx_update_stats()
> to ensure flow control processing remains fully protected within the RCU
> read-side critical section.
> - Replaced WRITE_ONCE() with rcu_assign_pointer() when assigning and clearing
> ring pointers in wx_alloc_q_vector() and wx_free_q_vector(), providing
> proper release memory barrier semantics for lockless RCU readers.
> - Added __rcu annotations to tx_ring and rx_ring in struct wx (wx_type.h) to
> align with Linux kernel RCU coding standards and fix Sparse warnings.
> v1: https://lore.kernel.org/netdev/20260813095141.88227-1-mengyuanlou@net-swift.com/
Although this patch does apply to net now (at least in my local testing),
the CI failed to do so the time it ran.
So I think this needs to be reposted.
next prev parent reply other threads:[~2026-08-20 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 10:08 [PATCH net v2] net: libwx: protect ring accesses with RCU Mengyuan Lou
2026-08-20 18:29 ` Simon Horman [this message]
2026-08-21 6:20 ` mengyuanlou
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=20260820182943.GD265046@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=duanqiangwen@net-swift.com \
--cc=edumazet@google.com \
--cc=jiawenwu@trustnetic.com \
--cc=kuba@kernel.org \
--cc=linglingzhang@net-swift.com \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).