netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2/3] raw: Stop using RTO_ONLINK.
Date: Tue, 23 May 2023 09:13:35 -0600	[thread overview]
Message-ID: <4927162d-1766-c495-4be2-873fa280218f@kernel.org> (raw)
In-Reply-To: <6ca7a70859803ff272cc965409856de354fa4e6c.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.
> 
> The MSG_DONTROUTE and SOCK_LOCALROUTE cases were already handled by
> raw_sendmsg() (SOCK_LOCALROUTE was handled by the RT_CONN_FLAGS*()
> macros called by get_rtconn_flags()). However, opt.is_strictroute
> wasn't taken into account. Therefore, a side effect of this patch is to
> now honour opt.is_strictroute, and thus align raw_sendmsg() with
> ping_v4_sendmsg() and udp_sendmsg().
> 
> Since raw_sendmsg() was the only user of get_rtconn_flags(), we can now
> remove this function.
> 
> Signed-off-by: Guillaume Nault <gnault@redhat.com>
> ---
>  include/net/ip.h |  5 -----
>  net/ipv4/raw.c   | 10 ++++------
>  2 files changed, 4 insertions(+), 11 deletions(-)
> 

Reviewed-by: David Ahern <dsahern@kernel.org>



  reply	other threads:[~2023-05-23 15:13 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 [this message]
2023-05-22 14:38 ` [PATCH net-next 3/3] udp: " Guillaume Nault
2023-05-23 15:14   ` David Ahern
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=4927162d-1766-c495-4be2-873fa280218f@kernel.org \
    --to=dsahern@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gnault@redhat.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemdebruijn.kernel@gmail.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 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).