netdev - RE: Re: [PATCH iproute2-next] tc: Classifier support for SPI field

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: 
 <MWHPR1801MB191863234AD01108DD846F88D30AA@MWHPR1801MB1918.namprd18.prod.outlook.com>
Date: Tue, 1 Aug 2023 02:43:08 +0000
From: Ratheesh Kannoth <rkannoth@...vell.com>
To: David Ahern <dsahern@...il.com>,
        "stephen@...workplumber.org"
	<stephen@...workplumber.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "davem@...emloft.net"
	<davem@...emloft.net>,
        "kuba@...nel.org" <kuba@...nel.org>,
        Leon Romanovsky
	<leon@...nel.org>,
        "edumazet@...gle.com" <edumazet@...gle.com>,
        "pabeni@...hat.com" <pabeni@...hat.com>
Subject: RE:  Re: [PATCH iproute2-next] tc: Classifier support for SPI field

> From: David Ahern <dsahern@...il.com>
> Sent: Tuesday, August 1, 2023 8:06 AM
> To: Ratheesh Kannoth <rkannoth@...vell.com>;
> stephen@...workplumber.org
> Cc: netdev@...r.kernel.org; davem@...emloft.net; kuba@...nel.org;
> Leon Romanovsky <leon@...nel.org>; edumazet@...gle.com;
> pabeni@...hat.com
> Subject: [EXT] Re: [PATCH iproute2-next] tc: Classifier support for SPI field
>> --- a/include/uapi/linux/pkt_cls.h
> >> +++ b/include/uapi/linux/pkt_cls.h
> >> @@ -594,6 +594,9 @@ enum {
> >>
> >>  	TCA_FLOWER_KEY_L2TPV3_SID,	/* be32 */
> >>
> >> +	TCA_FLOWER_KEY_SPI,		/* be32 */
> >> +	TCA_FLOWER_KEY_SPI_MASK,	/* be32 */
> >> +
> >>  	TCA_FLOWER_L2_MISS,		/* u8 */
> >>
> >>  	TCA_FLOWER_KEY_CFM,		/* nested */
> >
> 
> you do not need to include uapi changes in an iproute2 patch; headers are
> sync'ed from the kernel.

Thanks, but if user is compiling ip-route2 package in  a different linux machine ?
This is what I did. Not compiled against the kernel that I use.  
Backward compatibility will also break in this case, right ?  correct me.