[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <67ae1ddf79d37_254fdb2949f@willemb.c.googlers.com.notmuch>
Date: Thu, 13 Feb 2025 11:29:19 -0500
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>,
Paolo Abeni <pabeni@...hat.com>,
Willem de Bruijn <willemdebruijn.kernel@...il.com>,
netdev@...r.kernel.org
Cc: davem@...emloft.net,
kuba@...nel.org,
edumazet@...gle.com,
dsahern@...nel.org,
horms@...nel.org,
Willem de Bruijn <willemb@...gle.com>
Subject: Re: [PATCH net-next v2 4/7] ipv4: remove get_rttos
Willem de Bruijn wrote:
> Paolo Abeni wrote:
> > On 2/12/25 3:09 AM, Willem de Bruijn wrote:
> > > From: Willem de Bruijn <willemb@...gle.com>
> > >
> > > Initialize the ip cookie tos field when initializing the cookie, in
> > > ipcm_init_sk.
> > >
> > > The existing code inverts the standard pattern for initializing cookie
> > > fields. Default is to initialize the field from the sk, then possibly
> > > overwrite that when parsing cmsgs (the unlikely case).
> > >
> > > This field inverts that, setting the field to an illegal value and
> > > after cmsg parsing checking whether the value is still illegal and
> > > thus should be overridden.
> > >
> > > Be careful to always apply mask INET_DSCP_MASK, as before.
> >
> > I have a similar doubt here. I'm unsure we can change an established
> > behavior.
>
> This patch does not change behavior.
>
> Does not intend to, at least.
I should have added that that is what the cmsg_ipv4 test extension is
for. It was indeed not covered by existing tests, unlike much of the
other changes.
That said, this is the least self evident patch of the series. If you
prefer I can send without.
Either way, I'll follow up with a cmsg_ip.sh refactoring of
cmsg_ipv6.sh that extends coverage to IPv4.
Powered by blists - more mailing lists