From: Jakub Kicinski <kuba@kernel.org>
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: Jan Vaclav <jvaclav@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net/hsr: add interlink to fill_info output
Date: Fri, 17 Oct 2025 15:17:33 -0700 [thread overview]
Message-ID: <20251017151733.785c138a@kernel.org> (raw)
In-Reply-To: <6f9742f5-8889-449d-8354-572d2f8a711b@suse.de>
On Fri, 17 Oct 2025 12:17:21 +0200 Fernando Fernandez Mancera wrote:
> On 10/17/25 12:57 AM, Jakub Kicinski wrote:
> > On Wed, 15 Oct 2025 12:10:02 +0200 Jan Vaclav wrote:
> >> Currently, it is possible to configure the interlink port, but no
> >> way to read it back from userspace.
> >>
> >> Add it to the output of hsr_fill_info(), so it can be read from
> >> userspace, for example:
> >>
> >> $ ip -d link show hsr0 12: hsr0: <BROADCAST,MULTICAST> mtu ... ...
> >> hsr slave1 veth0 slave2 veth1 interlink veth2 ...
> >
> > Not entirely cleat at a glance how this driver deals with the slaves
> > or interlink being in a different netns, but I guess that's a pre-
> > existing problem..
> >
>
> FTR, I just did a quick round of testing and it handles it correctly.
> When moving a port to a different netns it notifies NETDEV_UNREGISTER -
> net/hsr/hsr_main.c handles the notification removing the port from the
> list. If the port list is empty, removes the hsr link.
>
> All good or at least as I would expect.
Did you try to make the slave/interlink be in a different namespace
when HSR interface is created? It should be possible with the right
combination of NEWLINK attributes, and that's the config I was
particularly concerned about..
next prev parent reply other threads:[~2025-10-17 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 10:10 [PATCH net-next] net/hsr: add interlink to fill_info output Jan Vaclav
2025-10-15 11:15 ` Fernando Fernandez Mancera
2025-10-16 22:57 ` Jakub Kicinski
2025-10-17 10:17 ` Fernando Fernandez Mancera
2025-10-17 22:17 ` Jakub Kicinski [this message]
2025-10-18 10:10 ` Fernando Fernandez Mancera
2025-10-16 23:00 ` patchwork-bot+netdevbpf
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=20251017151733.785c138a@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=jvaclav@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).