From: Hangbin Liu <liuhangbin@gmail.com>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, Jay Vosburgh <jv@jvosburgh.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
David Ahern <dsahern@gmail.com>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] bonding: show master index when dumping slave info
Date: Fri, 17 Oct 2025 07:26:50 +0000 [thread overview]
Message-ID: <aPHvunOUhX6iYnFi@fedora> (raw)
In-Reply-To: <0be57e07-3b90-44f7-85d5-97a90ac13831@blackwall.org>
On Fri, Oct 17, 2025 at 09:10:09AM +0300, Nikolay Aleksandrov 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?
Ah, I didn't notice this. We can show the master info directly with this...
# ip link show dummy0
3: dummy0: <BROADCAST,NOARP,SLAVE,UP,LOWER_UP> mtu 1500 qdisc noqueue master bond0 ...
Please ignore this patch.
Thanks
Hangbin
next prev parent reply other threads:[~2025-10-17 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 3:03 [PATCH net-next] bonding: show master index when dumping slave info Hangbin Liu
2025-10-17 3:05 ` [PATCH iproute2-next] bond: slave: print master name Hangbin Liu
2025-10-18 8:57 ` Stephen Hemminger
2025-10-17 6:10 ` [PATCH net-next] bonding: show master index when dumping slave info Nikolay Aleksandrov
2025-10-17 7:26 ` Hangbin Liu [this message]
2025-10-17 9:56 ` Jiri Pirko
2025-10-18 9:52 ` Hangbin Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aPHvunOUhX6iYnFi@fedora \
--to=liuhangbin@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.