[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251105161319.0591f96e@kernel.org>
Date: Wed, 5 Nov 2025 16:13:19 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Hangbin Liu <liuhangbin@...il.com>
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, 5 Nov 2025 07:55:47 +0000 Hangbin Liu wrote:
> > > I just realize that most of the address/src/dst in rt-addr/route are
> > > dual stack. The same with FRA_DST. We can't simply change binary to u32.
> > > So can we keep this u32 -> binary change?
> >
> > Ah, should have looked at more context..
> > Yes, and in that case without the display-hint?
>
> The display-hint is required; otherwise, the displayed src and dst fields
> appear as binary data, and setting the rule’s src/dst values also fails. I
> haven’t checked the code yet, but with
> - display-hint: ipv4
> the IPv6 addresses are also displayed correctly :)
Heh, we should have called the hint "ip" in that case :)
Powered by blists - more mailing lists