From: Cosmin Ratiu <cratiu@nvidia.com>
To: "sd@queasysnail.net" <sd@queasysnail.net>
Cc: "pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
Dragos Tatulea <dtatulea@nvidia.com>,
"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: [PATCH net] macsec: Support VLAN-filtering lower devices
Date: Thu, 22 Jan 2026 12:15:37 +0000 [thread overview]
Message-ID: <cbd86da13416db43b018299bfe3a93707f301311.camel@nvidia.com> (raw)
In-Reply-To: <aWZa-6WUc3h2AboY@krikkit>
On Tue, 2026-01-13 at 15:47 +0100, Sabrina Dubroca wrote:
> 2026-01-12, 10:32:17 +0000, Cosmin Ratiu wrote:
> > 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.
>
> Well, if an admin has the filters working and suddenly starts seeing
> packets that should have been filtered out, they may get confused.
>
> > 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.
>
> Ok.
>
> > 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.
>
> But that notifier gets caught in vlan_device_event, which calls
> vlan_filter_push_vids. That iterates all existing vlans and pushes
> them into the real device. That's why I thought it might work here,
> but I haven't tried.
Looked over this, and I think it's exactly what's needed.
I'll get back with an updated patch hopefully soon.
> > 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.
>
> Sure, if we have to implement all that in macsec, I would agree to
> take the current patch, and do the tracking later in net-next. In
> that
> case, please just add a note to the commit message about the offload
> vs non-offload behavior we're discussing here.
>
> Either way, it would also be good to add some selftests.
Will add.
Cosmin.
prev parent reply other threads:[~2026-01-22 12:15 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
2026-01-13 14:47 ` Sabrina Dubroca
2026-01-22 12:15 ` Cosmin Ratiu [this message]
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=cbd86da13416db43b018299bfe3a93707f301311.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