[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <864d12bc-2ecb-4770-af33-044232876376@redhat.com>
Date: Thu, 13 Feb 2025 19:12:38 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: 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 2/7] net: initialize mark in sockcm_init
On 2/13/25 4:35 PM, 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>
>>>
>>> Avoid open coding initialization of sockcm fields.
>>> Avoid reading the sk_priority field twice.
>>>
>>> This ensures all callers, existing and future, will correctly try a
>>> cmsg passed mark before sk_mark.
>>>
>>> This patch extends support for cmsg mark to:
>>> packet_spkt and packet_tpacket and net/can/raw.c.
>>>
>>> This patch extends support for cmsg priority to:
>>> packet_spkt and packet_tpacket.
>>
>> I admit I'm a little bit concerned vs possibly impacting existing
>> applications doing weird thing like passing the relevant cmsg and
>> expecting it to be ignored.
>
> We have a history of expanding support for passing variables by cmsg.
Ok, I should have paid more attention to other cmsg related changes.
git log says this is actually allowed, so I'm fine with the patch.
Thanks,
Paolo
Powered by blists - more mailing lists