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: <20230424182554.642bc0fc@rorschach.local.home> Date: Mon, 24 Apr 2023 18:25:54 -0400 From: Steven Rostedt <rostedt@...dmis.org> To: Vladimir Oltean <vladimir.oltean@....com> Cc: Masami Hiramatsu <mhiramat@...nel.org>, Andrew Lunn <andrew@...n.ch>, 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 Fri, 21 Apr 2023 15:47:08 +0300 Vladimir Oltean <vladimir.oltean@....com> wrote: > On Fri, Apr 21, 2023 at 09:38:50PM +0900, Masami Hiramatsu wrote: > > If the subsystem maintainers are OK for including this, it is OK. > > But basically, since the event is exposed to userland and you may keep > > these events maintained, you should carefully add the events. > > If those are only for debugging (after debug, it will not be used > > frequently), can you consider to use kprobe events? > > 'perf probe' command will also help you to trace local variables and > > structure members as like gdb does. > > Thanks for taking a look. I haven't looked at kprobe events. I also > wasn't planning on maintaining these assuming stable UABI terms, just > for debugging. What are some user space consumers that expect the UABI > to be stable, and what is it about the trace events that can/can't change? Ideally, tooling will use the libtraceevent library[1] to parse the events. In that case, if an event is used by tooling, you'll need to keep around the fields that are used by the tooling. -- Steve [1] https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/
Powered by blists - more mailing lists