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,
shuah@kernel.org, linux-kselftest@vger.kernel.org,
russell@strong.id.au, dave.taht@gmail.com
Subject: Re: [PATCH net-next 0/4] inet: Separate DSCP from ECN bits using new dscp_t type
Date: Tue, 08 Feb 2022 05:10:09 +0000 [thread overview]
Message-ID: <164429700971.22743.17071261100500230532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1643981839.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 4 Feb 2022 14:58:09 +0100 you wrote:
> The networking stack currently doesn't clearly distinguish between DSCP
> and ECN bits. The entire DSCP+ECN bits are stored in u8 variables (or
> structure fields), and each part of the stack handles them in their own
> way, using different macros. This has created several bugs in the past
> and some uncommon code paths are still unfixed.
>
> Such bugs generally manifest by selecting invalid routes because of ECN
> bits interfering with FIB routes and rules lookups (more details in the
> LPC 2021 talk[1] and in the RFC of this series[2]).
>
> [...]
Here is the summary with links:
- [net-next,1/4] ipv6: Define dscp_t and stop taking ECN bits into account in fib6-rules
(no matching commit)
- [net-next,2/4] ipv4: Stop taking ECN bits into account in fib4-rules
https://git.kernel.org/netdev/net-next/c/563f8e97e054
- [net-next,3/4] ipv4: Reject routes specifying ECN bits in rtm_tos
https://git.kernel.org/netdev/net-next/c/f55fbb6afb8d
- [net-next,4/4] ipv4: Use dscp_t in struct fib_alias
https://git.kernel.org/netdev/net-next/c/32ccf1107980
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:[~2022-02-08 5:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 13:58 [PATCH net-next 0/4] inet: Separate DSCP from ECN bits using new dscp_t type Guillaume Nault
2022-02-04 13:58 ` [PATCH net-next 1/4] ipv6: Define dscp_t and stop taking ECN bits into account in fib6-rules Guillaume Nault
2022-02-04 13:58 ` [PATCH net-next 2/4] ipv4: Stop taking ECN bits into account in fib4-rules Guillaume Nault
2022-02-04 13:58 ` [PATCH net-next 3/4] ipv4: Reject routes specifying ECN bits in rtm_tos Guillaume Nault
2022-02-04 18:19 ` Shuah Khan
2022-02-04 13:58 ` [PATCH net-next 4/4] ipv4: Use dscp_t in struct fib_alias Guillaume Nault
2022-02-07 6:08 ` [PATCH net-next 0/4] inet: Separate DSCP from ECN bits using new dscp_t type David Ahern
2022-02-07 19:03 ` Toke Høiland-Jørgensen
2022-02-08 5:10 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-06 18:22 Guillaume Nault
2021-12-06 19:57 ` Guillaume Nault
2021-12-14 0:16 ` Toke Høiland-Jørgensen
2021-12-15 16:48 ` Guillaume Nault
2021-12-15 20:40 ` Dave Taht
2021-12-17 17:55 ` Toke Høiland-Jørgensen
2021-12-17 22:52 ` Guillaume Nault
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=164429700971.22743.17071261100500230532.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gnault@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=russell@strong.id.au \
--cc=shuah@kernel.org \
--cc=toke@redhat.com \
--cc=yoshfuji@linux-ipv6.org \
/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;
as well as URLs for NNTP newsgroup(s).