From: Leon Romanovsky <leon@kernel.org>
To: Guillaume Nault <gnault@redhat.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Mustafa Ismail <mustafa.ismail@intel.com>,
Shiraz Saleem <shiraz.saleem@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Michal Kalderon <mkalderon@marvell.com>,
Ariel Elior <aelior@marvell.com>,
Jay Vosburgh <j.vosburgh@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
David Ahern <dsahern@kernel.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>
Subject: Re: [PATCH net-next] ipv4: Set scope explicitly in ip_route_output().
Date: Mon, 8 Apr 2024 13:55:11 +0300 [thread overview]
Message-ID: <20240408105511.GD8764@unreal> (raw)
In-Reply-To: <1f3c874fb825cdc030f729d2e48e6f45f3e3527f.1712347466.git.gnault@redhat.com>
On Fri, Apr 05, 2024 at 10:05:00PM +0200, Guillaume Nault wrote:
> Add a "scope" parameter to ip_route_output() so that callers don't have
> to override the tos parameter with the RTO_ONLINK flag if they want a
> local scope.
>
> This will allow converting flowi4_tos to dscp_t in the future, thus
> allowing static analysers to flag invalid interactions between
> "tos" (the DSCP bits) and ECN.
>
> Only three users ask for local scope (bonding, arp and atm). The others
> continue to use RT_SCOPE_UNIVERSE. While there, add a comment to warn
> users about the limitations of ip_route_output().
>
> Signed-off-by: Guillaume Nault <gnault@redhat.com>
> ---
> drivers/infiniband/hw/irdma/cm.c | 3 ++-
> drivers/infiniband/hw/qedr/qedr_iw_cm.c | 3 ++-
> drivers/net/bonding/bond_main.c | 4 ++--
> drivers/net/ethernet/broadcom/cnic.c | 3 ++-
> include/net/route.h | 9 ++++++++-
> net/atm/clip.c | 2 +-
> net/bridge/br_netfilter_hooks.c | 3 ++-
> net/ipv4/arp.c | 9 ++++++---
> net/ipv4/igmp.c | 3 ++-
> net/mpls/af_mpls.c | 2 +-
> 10 files changed, 28 insertions(+), 13 deletions(-)
>
Thanks,
Acked-by: Leon Romanovsky <leonro@nvidia.com> # infiniband
next prev parent reply other threads:[~2024-04-08 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 20:05 [PATCH net-next] ipv4: Set scope explicitly in ip_route_output() Guillaume Nault
2024-04-08 10:55 ` Leon Romanovsky [this message]
2024-04-08 12:21 ` patchwork-bot+netdevbpf
2024-04-11 9:36 ` Hangbin Liu
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=20240408105511.GD8764@unreal \
--to=leon@kernel.org \
--cc=aelior@marvell.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=j.vosburgh@gmail.com \
--cc=jgg@ziepe.ca \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=mkalderon@marvell.com \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=shiraz.saleem@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.