From: patchwork-bot+netdevbpf@kernel.org
To: Mina Almasry <almasrymina@google.com>
Cc: kuba@kernel.org, kaiyuanz@google.com, willemb@google.com,
edumazet@google.com, zoltan.kiss@citrix.com, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
pabeni@redhat.com, horms@kernel.org, kerneljasonxing@gmail.com
Subject: Re: [PATCH net v1 1/2] net: core: check skb_frags_readable before uncloning in skb_copy_ubufs
Date: Tue, 25 Aug 2026 09:50:06 +0000 [thread overview]
Message-ID: <178765140614.3359754.9513103982415965156.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260823183602.1051453-1-almasrymina@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 23 Aug 2026 18:36:01 +0000 you wrote:
> skb_copy_ubufs drops clones and modifies the SKB via pskb_expand_head()
> before checking for !skb_frags_readable(skb). This alters the SKB
> geometry prior to throwing an -EFAULT on an invalid SKB. Check
> readability first.
>
> Fixes: 65249feb6b3d ("net: add support for skbs with unreadable frags")
>
> [...]
Here is the summary with links:
- [net,v1,1/2] net: core: check skb_frags_readable before uncloning in skb_copy_ubufs
https://git.kernel.org/netdev/net/c/00e11ee9831b
- [net,v1,2/2] net: core: fix head-page leak in skb_zerocopy
https://git.kernel.org/netdev/net/c/97148bcb7511
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-25 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 18:36 [PATCH net v1 1/2] net: core: check skb_frags_readable before uncloning in skb_copy_ubufs Mina Almasry
2026-08-23 18:36 ` [PATCH net v1 2/2] net: core: fix head-page leak in skb_zerocopy Mina Almasry
2026-08-25 9:25 ` Paolo Abeni
2026-08-25 9:50 ` 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=178765140614.3359754.9513103982415965156.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kaiyuanz@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=zoltan.kiss@citrix.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.