From: Radu Rendec <radu.rendec@gmail.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
Sabrina Dubroca <sd@queasysnail.net>,
Radu Rendec <radu.rendec@gmail.com>
Subject: [PATCH 0/1] macsec: reflect the master interface state
Date: Tue, 18 Sep 2018 20:16:11 -0400 [thread overview]
Message-ID: <20180919001612.2636-1-radu.rendec@gmail.com> (raw)
Hi everyone,
I came across an issue with macsec interfaces where they don't reflect
the master interface state. On one hand you cannot set the macsec
interface link state to up unless the master interface is already up,
but on the other hand, if the master interface goes down while the
macsec interface is already up, the macsec interface stays up.
This may also be problematic if macsec interfaces are used as bridge
ports (probably not very usual, but that is my use case anyway). In that
case the bridge has no idea of the link state of the real device, since
it only sees the macsec interface, which is always up.
I'm proposing the attached patch, which is heavily inspired from the
vlan (802.1q) driver. However, in the case of macsec, there is no
concept of "loose binding" and the state is always reflected.
I tested the patch on x86_64, but I guess it's pretty much architecture
independent.
Any comments or suggestions are welcome. Thanks!
Radu Rendec (1):
macsec: reflect the master interface state
drivers/net/macsec.c | 57 +++++++++++++++++++++++++++++++++++---------
1 file changed, 46 insertions(+), 11 deletions(-)
--
2.17.1
next reply other threads:[~2018-09-19 5:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 0:16 Radu Rendec [this message]
2018-09-19 0:16 ` [PATCH 1/1] macsec: reflect the master interface state Radu Rendec
2018-09-19 15:24 ` Sabrina Dubroca
2018-09-19 16:44 ` Radu Rendec
2018-10-01 12:52 ` Sabrina Dubroca
2018-10-28 21:14 ` Radu Rendec
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=20180919001612.2636-1-radu.rendec@gmail.com \
--to=radu.rendec@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).