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
| ||
|
Message-ID: <20230412095534.dh2iitmi3j5i74sv@skbuf> Date: Wed, 12 Apr 2023 12:55:34 +0300 From: Vladimir Oltean <vladimir.oltean@....com> To: Andrew Lunn <andrew@...n.ch>, Steven Rostedt <rostedt@...dmis.org>, Masami Hiramatsu <mhiramat@...nel.org> Cc: netdev@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Florian Fainelli <f.fainelli@...il.com> Subject: Re: [PATCH net-next 0/2] DSA trace events On Wed, Apr 12, 2023 at 02:48:35AM +0200, Andrew Lunn wrote: > On Fri, Apr 07, 2023 at 05:14:49PM +0300, Vladimir Oltean wrote: > > This series introduces the "dsa" trace event class, with the following > > events: > > > > $ trace-cmd list | grep dsa > > dsa > > dsa:dsa_fdb_add_hw > > dsa:dsa_mdb_add_hw > > dsa:dsa_fdb_del_hw > > dsa:dsa_mdb_del_hw > > dsa:dsa_fdb_add_bump > > dsa:dsa_mdb_add_bump > > dsa:dsa_fdb_del_drop > > dsa:dsa_mdb_del_drop > > dsa:dsa_fdb_del_not_found > > dsa:dsa_mdb_del_not_found > > dsa:dsa_lag_fdb_add_hw > > dsa:dsa_lag_fdb_add_bump > > dsa:dsa_lag_fdb_del_hw > > dsa:dsa_lag_fdb_del_drop > > dsa:dsa_lag_fdb_del_not_found > > dsa:dsa_vlan_add_hw > > dsa:dsa_vlan_del_hw > > dsa:dsa_vlan_add_bump > > dsa:dsa_vlan_del_drop > > dsa:dsa_vlan_del_not_found > > > > These are useful to debug refcounting issues on CPU and DSA ports, where > > entries may remain lingering, or may be removed too soon, depending on > > bugs in higher layers of the network stack. > > Hi Vladimir > > I don't know anything about trace points. Should you Cc: > > Steven Rostedt <rostedt@...dmis.org> (maintainer:TRACING) > Masami Hiramatsu <mhiramat@...nel.org> (maintainer:TRACING) > > to get some feedback from people who do? > > Andrew I suppose I could. Hi Steven, Masami, would you mind taking a look and letting me know if the trace API was used reasonably? The patches were merged as: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=9538ebce88ffa074202d592d468521995cb1e714 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=02020bd70fa6abcb1c2a8525ce7c1500dd4f44a8 but I can make incremental changes if necessary.
Powered by blists - more mailing lists