RE: [PATCH net-next v8 1/5] netlink: specs: rt-addr: fix the type of target-netnsid

From: Loktionov, Aleksandr

Date: Mon Sep 28 2026 - 11:29:18 EST




> -----Original Message-----
> From: Yuyang Huang <uyoko90@xxxxxxxxx> On Behalf Of Yuyang Huang
> Sent: Sunday, September 27, 2026 2:24 AM
> To: Yuyang Huang <sigefriedhyy@xxxxxxxxx>
> Cc: Loktionov, Aleksandr <aleksandr.loktionov@xxxxxxxxx>; Andrew Lunn
> <andrew+netdev@xxxxxxx>; David S. Miller <davem@xxxxxxxxxxxxx>; David
> Ahern <dsahern@xxxxxxxxxx>; Donald Hunter <donald.hunter@xxxxxxxxx>;
> Eric Dumazet <edumazet@xxxxxxxxxx>; Ido Schimmel <idosch@xxxxxxxxxx>;
> Keller, Jacob E <jacob.e.keller@xxxxxxxxx>; Jakub Kicinski
> <kuba@xxxxxxxxxx>; Kuniyuki Iwashima <kuniyu@xxxxxxxxxx>; Nicolas
> Dichtel <nicolas.dichtel@xxxxxxxxx>; Nikolaos Gkarlis
> <nickgarlis@xxxxxxxxx>; Paolo Abeni <pabeni@xxxxxxxxxx>; Sabrina
> Dubroca <sd@xxxxxxxxxxxxxxx>; Shuah Khan <shuah@xxxxxxxxxx>; Simon
> Horman <horms@xxxxxxxxxx>; Stanislav Fomichev <sdf.kernel@xxxxxxxxx>;
> Willem de Bruijn <willemb@xxxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx;
> linux-kselftest@xxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx
> Subject: [PATCH net-next v8 1/5] netlink: specs: rt-addr: fix the type
> of target-netnsid
>
> The kernel parses IFA_TARGET_NETNSID as NLA_S32 and rt-link.yaml
> declares its target-netnsid as s32, but rt-addr.yaml has it as binary.
>
> Signed-off-by: Yuyang Huang <sigefriedhyy@xxxxxxxxx>
> Reviewed-by: Nicolas Dichtel <nicolas.dichtel@xxxxxxxxx>
> ---
> Documentation/netlink/specs/rt-addr.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/netlink/specs/rt-addr.yaml
> b/Documentation/netlink/specs/rt-addr.yaml
> index 0ecbd24c890c..17ead2203451 100644
> --- a/Documentation/netlink/specs/rt-addr.yaml
> +++ b/Documentation/netlink/specs/rt-addr.yaml
> @@ -119,7 +119,7 @@ attribute-sets:
> type: u32
> -
> name: target-netnsid
> - type: binary
> + type: s32
> -
> name: proto
> type: u8
> --
> 2.43.0

Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@xxxxxxxxx>