From: Simon Horman <horms@kernel.org>
To: David Carlier <devnexen@gmail.com>
Cc: danishanwar@ti.com, rogerq@kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, m-malladi@ti.com, jacob.e.keller@intel.com,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ti: icssg-prueth: fix missing data copy and wrong recycle in ZC RX dispatch
Date: Fri, 27 Mar 2026 10:29:24 +0000 [thread overview]
Message-ID: <20260327102924.GF111839@horms.kernel.org> (raw)
In-Reply-To: <20260325125131.53399-1-devnexen@gmail.com>
+ Meghana Malladi
On Wed, Mar 25, 2026 at 12:51:30PM +0000, David Carlier wrote:
> emac_dispatch_skb_zc() allocates a new skb via napi_alloc_skb() but
> never copies the packet data from the XDP buffer into it. The skb is
> passed up the stack containing uninitialized heap memory instead of
> the actual received packet, leaking kernel heap contents to userspace.
>
> Copy the received packet data from the XDP buffer into the skb using
> skb_copy_to_linear_data().
>
> Additionally, remove the skb_mark_for_recycle() call since the skb is
> backed by the NAPI page frag allocator, not page_pool. Marking a
> non-page_pool skb for recycle causes the free path to return pages to
> a page_pool that does not own them, corrupting page_pool state.
>
> The non-ZC path (emac_rx_packet) does not have these issues because it
> uses napi_build_skb() to wrap the existing page_pool page directly,
> requiring no copy, and correctly marks for recycle since the page comes
> from page_pool_dev_alloc_pages().
>
> Fixes: 7a64bb388df3 ("net: ti: icssg-prueth: Add AF_XDP zero copy for RX")
> Signed-off-by: David Carlier <devnexen@gmail.com>
> ---
> drivers/net/ethernet/ti/icssg/icssg_common.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Hi David,
Thanks for the update.
My understanding is that this addresses the review of v1.
Reviewed-by: Simon Horman <horms@kernel.org>
v1: https://lore.kernel.org/all/20260324211402.342474-1-devnexen@gmail.com/
Some points to keep in mind for the future:
* Please include a version number in the subject when posting versions >
This helps a lot in tracking things.
Subject: [PATCH v2] ...
* Please include the target tree. As a fix for code, which I asusme
is present in net, in this case that would be the net tree.
Subject: [PATCH net v2] ...
Otherwise it would probably be the net-next tree.
* Please CC all relevant parties. In this case that would
include Meghana as he provided review of v1.
* Please consider including a changelog, along with links to earlier
versions below the scissors ("---")
* b4 can help with most of these things
* More information on the Netdev development process can be found at
https://docs.kernel.org/process/maintainer-netdev.html
...
next prev parent reply other threads:[~2026-03-27 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 12:51 [PATCH] net: ti: icssg-prueth: fix missing data copy and wrong recycle in ZC RX dispatch David Carlier
2026-03-27 10:29 ` Simon Horman [this message]
2026-03-27 10:39 ` David CARLIER
2026-03-27 12:10 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2026-03-24 21:14 David Carlier
2026-03-25 9:14 ` Meghana Malladi
2026-03-25 9:23 ` David CARLIER
2026-03-25 9:28 ` David Carlier
2026-03-25 11:44 ` Meghana Malladi
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=20260327102924.GF111839@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=devnexen@gmail.com \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-malladi@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
/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