From: patchwork-bot+netdevbpf@kernel.org
To: Samuel Moelius <sam.moelius@trailofbits.com>
Cc: jhs@mojatatu.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, mtottenh@akamai.com, pctammela@mojatatu.com,
johunt@akamai.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 1/2] net/sched: act_pedit: require matching IPv4 L4 protocol
Date: Fri, 12 Jun 2026 22:20:22 +0000 [thread overview]
Message-ID: <178130282214.1269656.1323140123470715734.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260609185636.1599359-2-sam.moelius@trailofbits.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 9 Jun 2026 18:56:34 +0000 you wrote:
> The extended IPv4 L4 header mode in act_pedit can select TCP or UDP
> header fields without confirming that the IPv4 protocol field matches
> the selected transport header.
>
> That lets a rule written for TCP or UDP modify unrelated payload bytes
> in a packet carrying a different protocol.
>
> [...]
Here is the summary with links:
- [net,v3,1/2] net/sched: act_pedit: require matching IPv4 L4 protocol
https://git.kernel.org/netdev/net-next/c/d504a9785722
- [net,v3,2/2] net/sched: act_pedit: require matching IPv4 L4 protocol
https://git.kernel.org/netdev/net-next/c/f7d109f176f2
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-06-12 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260609185636.1599359-1-sam.moelius@trailofbits.com>
2026-06-09 18:56 ` [PATCH net v3 1/2] net/sched: act_pedit: require matching IPv4 L4 protocol Samuel Moelius
2026-06-12 22:20 ` patchwork-bot+netdevbpf [this message]
2026-06-09 18:56 ` [PATCH net v3 2/2] " Samuel Moelius
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=178130282214.1269656.1323140123470715734.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=johunt@akamai.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtottenh@akamai.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=sam.moelius@trailofbits.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