From: patchwork-bot+netdevbpf@kernel•org
To: Guillaume Nault <gnault@redhat•com>
Cc: davem@davemloft•net, kuba@kernel•org, netdev@vger•kernel.org,
yoshfuji@linux-ipv6•org, dsahern@kernel•org, toke@redhat•com
Subject: Re: [PATCH net-next] ipv4: Reject again rules with high DSCP values
Date: Thu, 10 Feb 2022 15:40:09 +0000 [thread overview]
Message-ID: <164450760952.15967.596511068493586554.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cca72292694a74c76a6e155b34a8480df2918a14.1644495285.git.gnault@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft•net>:
On Thu, 10 Feb 2022 13:24:51 +0100 you wrote:
> Commit 563f8e97e054 ("ipv4: Stop taking ECN bits into account in
> fib4-rules") replaced the validation test on frh->tos. While the new
> test is stricter for ECN bits, it doesn't detect the use of high order
> DSCP bits. This would be fine if IPv4 could properly handle them. But
> currently, most IPv4 lookups are done with the three high DSCP bits
> masked. Therefore, using these bits doesn't lead to the expected
> result.
>
> [...]
Here is the summary with links:
- [net-next] ipv4: Reject again rules with high DSCP values
https://git.kernel.org/netdev/net-next/c/dc513a405cad
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:[~2022-02-10 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 12:24 [PATCH net-next] ipv4: Reject again rules with high DSCP values Guillaume Nault
2022-02-10 15:40 ` 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=164450760952.15967.596511068493586554.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=gnault@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=toke@redhat$(echo .)com \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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