[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aSaf1D-N5ONmnys8@fedora>
Date: Wed, 26 Nov 2025 06:36:04 +0000
From: Hangbin Liu <liuhangbin@...il.com>
To: Asbjørn Sloth Tønnesen <ast@...erby.net>
Cc: netdev@...r.kernel.org, Donald Hunter <donald.hunter@...il.com>,
Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>,
"Matthieu Baerts (NGI0)" <matttbe@...nel.org>,
Stanislav Fomichev <sdf@...ichev.me>,
Jacob Keller <jacob.e.keller@...el.com>,
Yuyang Huang <yuyanghuang@...gle.com>,
Daniel Borkmann <daniel@...earbox.net>
Subject: Re: [PATCH net-next] netlink: specs: add big-endian byte-order for
u32 IPv4 addresses
Hi,
On Tue, Nov 25, 2025 at 05:03:13PM +0000, Asbjørn Sloth Tønnesen wrote:
> I also checked how consistently defined the fields using the ipv6 display helper are,
> and it looks like they could use some realignment too. Obviously not for this fix.
>
> git grep -C6 'display-hint.*ipv6$' Documentation/netlink/specs/
The ip6gre spec shows
-
name: local
display-hint: ipv6
-
name: remote
display-hint: ipv6
The dump result looks good. So for others ipv6 field, what alignment should we
use? Should we add checks: min-len: 16? Do we need byte-order: big-endian?
Thanks
Hangbin
Powered by blists - more mailing lists