netdev - Re: [RFC net-next 3/5] net: dsa: mv88e6xxx: MQPRIO support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <DE4F4AC6-2783-4374-A4F8-3032B32DB848@padl.com>
Date: Sat, 27 Sep 2025 19:14:34 +0100
From: Luke Howard <lukeh@...l.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, vladimir.oltean@....com, kieran@...nda.com,
        jcschroeder@...il.com, Max Hunter <max@...tershome.org>
Subject: Re: [RFC net-next 3/5] net: dsa: mv88e6xxx: MQPRIO support

> https://docs.kernel.org/doc-guide/kernel-doc.html#how-to-format-kernel-doc-comments

Oddly though very files in the kernel seem to follow this (unless I’m missing something obvious).

linux$ git grep @arg1|wc
     13      96    1009

Anyway, happy to change.

> Having an open user space side helps get such an extra attribute
> added.
> 
> Would the kernel bridge have any use of this? It is normal to add a
> feature to the kernel, and then offload it to hardware.

Yes, it should probably be implemented for the kernel bridge.

I guess we need a new attribute or flag when adding a MDB or FDB entry, and also a way to indicate that a TC is SRP-managed. The kernel bridge could then be modified to reject or reclassify packets that are classified into a TC with the SRP flag set, unless a MDB/FDB entry exists for the DA that also has that flag set.