[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aQMHJlwcchqtoAa7@fedora>
Date: Thu, 30 Oct 2025 06:35:18 +0000
From: Hangbin Liu <liuhangbin@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, Donald Hunter <donald.hunter@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, Jan Stancek <jstancek@...hat.com>,
"Matthieu Baerts (NGI0)" <matttbe@...nel.org>,
Asbjørn Sloth Tønnesen <ast@...erby.net>,
Stanislav Fomichev <sdf@...ichev.me>, Shuah Khan <shuah@...nel.org>,
Ido Schimmel <idosch@...dia.com>,
Guillaume Nault <gnault@...hat.com>,
Petr Machata <petrm@...dia.com>, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH net-next 2/3] netlink: specs: update rt-rule src/dst
attribute types to support IPv4 addresses
On Wed, Oct 29, 2025 at 04:37:42PM -0700, Jakub Kicinski wrote:
> On Wed, 29 Oct 2025 08:22:44 +0000 Hangbin Liu wrote:
> > -
> > name: dst
> > - type: u32
> > + type: binary
> > + display-hint: ipv4
> > -
> > name: src
> > - type: u32
> > + type: binary
> > + display-hint: ipv4
>
> This will be annoying For C / C++, and you didn't set the max len
> so I think we'll also have to malloc each time. Do we not support
> display-hint for scalars?
Ah, I didn't notice this. Should we convert all the
type: binary
display-hint: ipv4
to
type: u32
byte-order: big-endian
display-hint: ipv4
Thanks
Hangbin
Powered by blists - more mailing lists