From: Rodolfo Giometti <giometti@enneenne.com>
To: netdev@vger.kernel.org
Cc: Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Stephen Hemminger <shemminger@osdl.org>,
Flavio Leitner <fbl@redhat.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Allow non "disabled" state for !netif_oper_up() links
Date: Wed, 9 Nov 2022 16:24:09 +0100 [thread overview]
Message-ID: <20221109152410.3572632-1-giometti@enneenne.com> (raw)
This patch allows non "disabled" state even if the link is UP and runnign
but with no carrier.
I'm trying to implement a new MRP daemon in userspace and when a MRM detects
that one of its ring connections has no carrier, the normative states that
such link shall be set as BLOCKED (or LISTENING for Linux bridges). Current
code blocks this operation.
I think kernel code should implement mechanisms and not policies!
Rodolfo Giometti
---
br_netlink.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
next reply other threads:[~2022-11-09 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 15:24 Rodolfo Giometti [this message]
2022-11-09 15:24 ` [PATCH] net br_netlink.c:y allow non "disabled" state for !netif_oper_up() links Rodolfo Giometti
2022-11-09 17:34 ` Andrew Lunn
2022-11-09 18:19 ` Rodolfo Giometti
2022-11-09 18:46 ` Andrew Lunn
2022-11-11 9:43 ` Rodolfo Giometti
2022-11-11 13:09 ` Andrew Lunn
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=20221109152410.3572632-1-giometti@enneenne.com \
--to=giometti@enneenne.com \
--cc=davem@davemloft.net \
--cc=fbl@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=shemminger@osdl.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 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).