From: patchwork-bot+netdevbpf@kernel.org
To: Haishuang Yan <yanhaishuang@cmss.chinamobile.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org,
michal.swiatkowski@linux.intel.com, aleksander.lobakin@intel.com,
marcin.szycik@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] pfcp: fix two bugs in the receive path
Date: Wed, 07 Oct 2026 02:00:05 +0000 [thread overview]
Message-ID: <179133840503.2870283.6220566218471653405.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930124818.114224-1-yanhaishuang@cmss.chinamobile.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 30 Sep 2026 20:48:16 +0800 you wrote:
> This series fixes two bugs in pfcp_encap_recv(), both introduced when
> the receive path started filling in PFCP tunnel metadata.
>
> Patch 1 fixes a metadata_dst leak when iptunnel_pull_header() fails
> after tun_dst has been allocated.
>
> Patch 2 makes sure the SEID is in the linear area before it is read, so
> that a short packet with the S flag set cannot make the driver read
> beyond the end of the packet data.
>
> [...]
Here is the summary with links:
- [net,1/2] pfcp: fix metadata_dst leak in pfcp_encap_recv()
(no matching commit)
- [net,2/2] pfcp: make sure the SEID is linear before reading it
https://git.kernel.org/netdev/net/c/23609bce9e1d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-10-07 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 12:48 [PATCH net 0/2] pfcp: fix two bugs in the receive path Haishuang Yan
2026-09-30 12:48 ` [PATCH net 1/2] pfcp: fix metadata_dst leak in pfcp_encap_recv() Haishuang Yan
2026-09-30 12:48 ` [PATCH net 2/2] pfcp: make sure the SEID is linear before reading it Haishuang Yan
2026-09-30 15:24 ` [PATCH net 0/2] pfcp: fix two bugs in the receive path netdev-bot+sinfo
2026-10-07 2:00 ` patchwork-bot+netdevbpf [this message]
2026-10-07 2:00 ` patchwork-bot+netdevbpf
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=179133840503.2870283.6220566218471653405.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.szycik@linux.intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yanhaishuang@cmss.chinamobile.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.