[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f077e15a-c924-fb4f-8fa1-229bad67c2ae@gmail.com>
Date: Fri, 9 Dec 2022 16:07:55 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Vladimir Oltean <vladimir.oltean@....com>, netdev@...r.kernel.org
Cc: Andrew Lunn <andrew@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
"Hans J. Schultz" <netdev@...io-technology.com>,
Saeed Mahameed <saeed@...nel.org>
Subject: Re: [PATCH v2 net-next 4/4] net: dsa: mv88e6xxx: replace VTU
violation prints with trace points
On 12/9/22 09:28, Vladimir Oltean wrote:
> It is possible to trigger these VTU violation messages very easily,
> it's only necessary to send packets with an unknown VLAN ID to a port
> that belongs to a VLAN-aware bridge.
>
> Do a similar thing as for ATU violation messages, and hide them in the
> kernel's trace buffer.
>
> New usage model:
>
> $ trace-cmd list | grep mv88e6xxx
> mv88e6xxx
> mv88e6xxx:mv88e6xxx_vtu_miss_violation
> mv88e6xxx:mv88e6xxx_vtu_member_violation
> $ trace-cmd report
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>
Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
--
Florian
Powered by blists - more mailing lists