[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7quap7umeeksodg62bbv4ob4344edplb7f33yiebs2hvhrrdvf@wndrzz7rxi7v>
Date: Fri, 17 Oct 2025 11:56:55 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Nikolay Aleksandrov <razor@...ckwall.org>
Cc: Hangbin Liu <liuhangbin@...il.com>, netdev@...r.kernel.org,
Jay Vosburgh <jv@...sburgh.net>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
Stephen Hemminger <stephen@...workplumber.org>, David Ahern <dsahern@...il.com>, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH net-next] bonding: show master index when dumping slave
info
Fri, Oct 17, 2025 at 08:10:09AM +0200, razor@...ckwall.org wrote:
>On 10/17/25 06:03, Hangbin Liu wrote:
>> Currently, there is no straightforward way to obtain the master/slave
>> relationship via netlink. Users have to retrieve all slaves through sysfs
>> to determine these relationships.
>>
>
>How about IFLA_MASTER? Why not use that?
It's been there for a decade. Plus is, it exposes master for all
slave-master devices. Odd that you missed it.
Powered by blists - more mailing lists