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  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:   Sun, 5 Jan 2020 22:18:14 +0900
From:   Masami Hiramatsu <>
To:     Steven Rostedt <>
Cc:     Sudip Mukherjee <>,
        Ingo Molnar <>,
        Arnaldo Carvalho de Melo <>,
        Jiri Olsa <>,
        Namhyung Kim <>,
        Linux Trace Devel <>,
        LKML <>,
        Linus Torvalds <>
Subject: Re: [RFC] tools lib traceevent: How to do library versioning being
 in the Linux kernel source?

On Fri, 3 Jan 2020 18:12:42 -0500
Steven Rostedt <> wrote:

> On Fri, 3 Jan 2020 21:17:43 +0900
> Masami Hiramatsu <> wrote:
> > +1. It sounds reasonable to move the main part of libtraceevent out
> > of kernel tree. BTW, the plugins seems depending on the kernel. Maybe
> > we can provide it under
> > /lib/modules/<kversion>/shared/libtraceevent/plugins/ ? :)
> They really shouldn't be. They should be able to be used between
> different versions of the kernel. Which plugins do you see an issue
> with?

I meant tools/lib/traceevent/plugins.
It seems that those plugins provide equivarent codes of some macros
or values in event formats. In that case, when a new kernel modifies
the event definitions, I think some of those needs to be updated too.
Or, would those events be considered as a stable ABI?

Thank you,

Masami Hiramatsu <>

Powered by blists - more mailing lists