From: Cosmin Ratiu <cratiu@nvidia.com>
To: "sd@queasysnail.net" <sd@queasysnail.net>
Cc: "edumazet@google.com" <edumazet@google.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
Dragos Tatulea <dtatulea@nvidia.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net] macsec: Support VLAN-filtering lower devices
Date: Mon, 12 Jan 2026 10:32:17 +0000 [thread overview]
Message-ID: <34305da7654365c3c8ade9cde07cb992f7270634.camel@nvidia.com> (raw)
In-Reply-To: <aWLWgrL8UYJISOsu@krikkit>
On Sat, 2026-01-10 at 23:45 +0100, Sabrina Dubroca wrote:
> 2026-01-09, 13:50:24 +0000, Cosmin Ratiu wrote:
>
> > Would you like to see any tweaks to the proposed patch?
>
> Well, updating the lower device's VLAN filters when not using offload
> is undesireable, so macsec_vlan_rx_{add,kill}_vid should check that
> offload is used, but then we'd have to remove/re-add then when
> offload
> is toggled after some vlan devices have been created on top of the
> macsec device. Keeping track of all the ids we've pushed down via
> macsec_vlan_rx_add_vid seems a bit unreasonable, but maybe we can
> call vlan_{get,drop}_rx_*_filter_info when we toggle macsec offload?
> (not sure if that will have the behavior we want)
>
Perhaps "undesirable" is too strong of a word. I would use "unneeded".
Having the encrypted VLANs in the lower dev HW filter can't do too much
harm, except maybe allowing some non-macsec packets with those vlans
when previously they wouldn't be allowed.
But remember what happened before the mentioned "Fixes" patch: the
lower device was put in promisc mode because it didn't advertise
IFF_UNICAST_FLT so it would have received all packets anyway.
So this fix is strictly better, simple enough that it can be understood
to be harmless.
The vlan_{get,drop}_rx_*_filter_info functions simply call device
notifiers when the VLAN filter flags change, they're not useful for
obtaining the list of VLANs. The upper devs keep track of those.
If I engineer the fix we're discussing here (which would make macsec
keep track of VLANs), it would be significantly more complicated, and
it belonging into net instead of net-next could be called into
question.
Cosmin.
next prev parent reply other threads:[~2026-01-12 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 10:47 [PATCH net] macsec: Support VLAN-filtering lower devices Cosmin Ratiu
2026-01-09 10:26 ` Sabrina Dubroca
2026-01-09 11:38 ` Cosmin Ratiu
2026-01-09 12:06 ` Sabrina Dubroca
2026-01-09 13:50 ` Cosmin Ratiu
2026-01-10 22:45 ` Sabrina Dubroca
2026-01-12 10:32 ` Cosmin Ratiu [this message]
2026-01-13 14:47 ` Sabrina Dubroca
2026-01-22 12:15 ` Cosmin Ratiu
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=34305da7654365c3c8ade9cde07cb992f7270634.camel@nvidia.com \
--to=cratiu@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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