All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sun Jian <sun.jian.kdev@gmail.com>
Cc: netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	davem@davemloft.net, kuba@kernel.org, hawk@kernel.org,
	john.fastabend@gmail.com, sdf@fomichev.me, bpf@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] fix skb length accounting after XDP frag adjustment
Date: Sat, 08 Aug 2026 00:10:08 +0000	[thread overview]
Message-ID: <178614780893.2472232.3476445161092062849.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260804054040.613675-1-sun.jian.kdev@gmail.com>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon,  3 Aug 2026 22:40:37 -0700 you wrote:
> This series fixes skb length accounting after an XDP program adjusts its
> fragment area, in both the generic XDP path (net/core/dev.c) and the veth
> native path (drivers/net/veth.c). When the fragment area is resized,
> skb->len and skb->data_len can go out of sync, and in the reproduced UDP
> receive path this leaked skb_shared_info contents (including a kernel
> pointer) to userspace while truncating real payload.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/2] net: fix skb length accounting after generic XDP frag adjustment
    https://git.kernel.org/netdev/net/c/33f2b2eb33d6
  - [net,v3,2/2] veth: fix skb length accounting after XDP frag adjustment
    https://git.kernel.org/netdev/net/c/cb6379feaaff

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-08  0:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  5:40 [PATCH net v3 0/2] fix skb length accounting after XDP frag adjustment Sun Jian
2026-08-04  5:40 ` [PATCH net v3 1/2] net: fix skb length accounting after generic " Sun Jian
2026-08-05  5:41   ` sashiko-bot
2026-08-04  5:40 ` [PATCH net v3 2/2] veth: fix skb length accounting after " Sun Jian
2026-08-05  5:41   ` sashiko-bot
2026-08-08  0:10 ` patchwork-bot+netdevbpf [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=178614780893.2472232.3476445161092062849.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@fomichev.me \
    --cc=sun.jian.kdev@gmail.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.