From: David Ahern <dsahern@kernel•org>
To: Guillaume Nault <gnault@redhat•com>,
David Miller <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
Eric Dumazet <edumazet@google•com>
Cc: netdev@vger•kernel.org,
Willem de Bruijn <willemdebruijn.kernel@gmail•com>
Subject: Re: [PATCH net-next 3/3] udp: Stop using RTO_ONLINK.
Date: Tue, 23 May 2023 09:14:06 -0600 [thread overview]
Message-ID: <a9dec8d0-9485-e044-5954-54d6e7f55685@kernel.org> (raw)
In-Reply-To: <abc28174280c6947ab78ce77772df695b812843c.1684764727.git.gnault@redhat.com>
On 5/22/23 8:38 AM, Guillaume Nault wrote:
> Use ip_sendmsg_scope() to properly initialise the scope in
> flowi4_init_output(), instead of overriding tos with the RTO_ONLINK
> flag. The objective is to eventually remove RTO_ONLINK, which will
> allow converting .flowi4_tos to dscp_t.
>
> Now that the scope is determined by ip_sendmsg_scope(), we need to
> check its result to set the 'connected' variable.
>
> Signed-off-by: Guillaume Nault <gnault@redhat•com>
> ---
> net/ipv4/udp.c | 17 ++++++-----------
> 1 file changed, 6 insertions(+), 11 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel•org>
next prev parent reply other threads:[~2023-05-23 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 14:37 [PATCH net-next 0/3] ipv4: Remove RTO_ONLINK from udp, ping and raw sockets Guillaume Nault
2023-05-22 14:37 ` [PATCH net-next 1/3] ping: Stop using RTO_ONLINK Guillaume Nault
2023-05-23 15:09 ` David Ahern
2023-05-22 14:38 ` [PATCH net-next 2/3] raw: " Guillaume Nault
2023-05-23 15:13 ` David Ahern
2023-05-22 14:38 ` [PATCH net-next 3/3] udp: " Guillaume Nault
2023-05-23 15:14 ` David Ahern [this message]
2023-05-24 7:30 ` [PATCH net-next 0/3] ipv4: Remove RTO_ONLINK from udp, ping and raw sockets patchwork-bot+netdevbpf
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=a9dec8d0-9485-e044-5954-54d6e7f55685@kernel.org \
--to=dsahern@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gnault@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=willemdebruijn.kernel@gmail$(echo .)com \
/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