netdev - Re: [PATCH net 1/4] docs: net: dsa: document the tagger-owned storage mechanism

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] [thread-next>] [day] [month] [year] [list]

Date: Fri, 8 Dec 2023 23:15:09 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>, 
	Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, 
	Andrew Lunn <andrew@...n.ch>, Florian Fainelli <f.fainelli@...il.com>, 
	Luiz Angelo Daros de Luca <luizluca@...il.com>, Alvin Šipraga <alsi@...g-olufsen.dk>, 
	Madhuri Sripada <madhuri.sripada@...rochip.com>, Marcin Wojtas <mw@...ihalf.com>, 
	Tobias Waldekranz <tobias@...dekranz.com>, Arun Ramadoss <arun.ramadoss@...rochip.com>, 
	"Russell King (Oracle)" <rmk+kernel@...linux.org.uk>, Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH net 1/4] docs: net: dsa: document the tagger-owned storage mechanism

On Fri, Dec 8, 2023 at 8:36 PM Vladimir Oltean <vladimir.oltean@....com> wrote:

> Introduced 2 years ago in commit dc452a471dba ("net: dsa: introduce
> tagger-owned storage for private and shared data"), the tagger-owned
> storage mechanism has recently sparked some discussions which denote a
> general lack of developer understanding / awareness of it. There was
> also a bug in the ksz switch driver which indicates the same thing.
>
> Admittedly, it is also not obvious to see the design constraints that
> led to the creation of such a complicated mechanism.
>
> Here are some paragraphs that explain what it's about.
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>

Clear and to the point.
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>

Yours,
Linus Walleij