[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aPNjcWo8G3tTpin0@fedora>
Date: Sat, 18 Oct 2025 09:52:49 +0000
From: Hangbin Liu <liuhangbin@...il.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Nikolay Aleksandrov <razor@...ckwall.org>, 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
On Fri, Oct 17, 2025 at 11:56:55AM +0200, Jiri Pirko wrote:
> 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.
Once, I wanted to find the slaves from a master interface but couldn’t. So I
added it to my to-do list. Later, I noticed that the master information was
already available in the slave, but I forgot about it after long time.
Recently, when I reviewed my to-do list, I realized that printing all slaves
from the master interface seemed impractical. So I tried to list the master
information in the slave again — and forgot about IFLA_MASTER...
Hangbin
Powered by blists - more mailing lists