From: patchwork-bot+netdevbpf@kernel•org
To: Guillaume Nault <gnault@redhat•com>
Cc: davem@davemloft•net, kuba@kernel•org, netdev@vger•kernel.org,
steffen.klassert@secunet•com, herbert@gondor•apana.org.au,
yoshfuji@linux-ipv6•org, dsahern@kernel•org, wenxu@ucloud•cn,
varun@chelsio•com, saeedm@nvidia•com, leon@kernel•org,
vladbu@nvidia•com, ogerlitz@mellanox•com
Subject: Re: [PATCH v2 net 0/4] ipv4: Fix accidental RTO_ONLINK flags passed to ip_route_output_key_hash()
Date: Wed, 12 Jan 2022 04:50:10 +0000 [thread overview]
Message-ID: <164196301084.21433.5520835462235159586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1641821242.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Mon, 10 Jan 2022 14:43:04 +0100 you wrote:
> The IPv4 stack generally uses the last bit of ->flowi4_tos as a flag
> indicating link scope for route lookups (RTO_ONLINK). Therefore, we
> have to be careful when copying a TOS value to ->flowi4_tos. In
> particular, the ->tos field of IPv4 packets may have this bit set
> because of ECN. Also tunnel keys generally accept any user value for
> the tos.
>
> [...]
Here is the summary with links:
- [v2,net,1/4] xfrm: Don't accidentally set RTO_ONLINK in decode_session4()
https://git.kernel.org/netdev/net/c/23e7b1bfed61
- [v2,net,2/4] gre: Don't accidentally set RTO_ONLINK in gre_fill_metadata_dst()
https://git.kernel.org/netdev/net/c/f7716b318568
- [v2,net,3/4] libcxgb: Don't accidentally set RTO_ONLINK in cxgb_find_route()
https://git.kernel.org/netdev/net/c/a915deaa9abe
- [v2,net,4/4] mlx5: Don't accidentally set RTO_ONLINK before mlx5e_route_lookup_ipv4_get()
https://git.kernel.org/netdev/net/c/48d67543e01d
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-01-12 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 13:43 [PATCH v2 net 0/4] ipv4: Fix accidental RTO_ONLINK flags passed to ip_route_output_key_hash() Guillaume Nault
2022-01-10 13:43 ` [PATCH v2 net 1/4] xfrm: Don't accidentally set RTO_ONLINK in decode_session4() Guillaume Nault
2022-01-10 13:43 ` [PATCH v2 net 2/4] gre: Don't accidentally set RTO_ONLINK in gre_fill_metadata_dst() Guillaume Nault
2022-01-10 13:43 ` [PATCH v2 net 3/4] libcxgb: Don't accidentally set RTO_ONLINK in cxgb_find_route() Guillaume Nault
2022-01-10 13:43 ` [PATCH v2 net 4/4] mlx5: Don't accidentally set RTO_ONLINK before mlx5e_route_lookup_ipv4_get() Guillaume Nault
2022-01-12 4:50 ` 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=164196301084.21433.5520835462235159586.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=herbert@gondor$(echo .)apana.org.au \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ogerlitz@mellanox$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=steffen.klassert@secunet$(echo .)com \
--cc=varun@chelsio$(echo .)com \
--cc=vladbu@nvidia$(echo .)com \
--cc=wenxu@ucloud$(echo .)cn \
--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