Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@xxxxxxxxxx>:
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
