linux-kernel - Re: [RFC] tools lib traceevent: How to do library versioning being in the Linux kernel source?

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]

Message-ID: <20200106162623.GA11285@kernel.org>
Date:   Mon, 6 Jan 2020 13:26:23 -0300
From:   Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To:     Jiri Olsa <jolsa@...hat.com>
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        Sudip Mukherjee <sudipm.mukherjee@...il.com>,
        Ingo Molnar <mingo@...nel.org>,
        Namhyung Kim <namhyung@...nel.org>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Linux Trace Devel <linux-trace-devel@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
        users@...ux.kernel.org
Subject: Re: [RFC] tools lib traceevent: How to do library versioning being
 in the Linux kernel source?

Em Mon, Jan 06, 2020 at 04:19:02PM +0100, Jiri Olsa escreveu:
> On Fri, Jan 03, 2020 at 06:16:14PM -0500, Steven Rostedt wrote:
> > 
> > [ Added Konstantin and kernel.org users mailing list ]
> > 
> > On Fri, 3 Jan 2020 14:36:40 +0100
> > Jiri Olsa <jolsa@...hat.com> wrote:
> > 
> > > On Thu, Jan 02, 2020 at 06:58:53PM -0500, Steven Rostedt wrote:
> > > > On Fri, 3 Jan 2020 00:49:50 +0100
> > > > Jiri Olsa <jolsa@...hat.com> wrote:
> > > >   
> > > > > > Should we move libtraceevent into a stand alone git repo (on
> > > > > > kernel.org), that can have tags and branches specifically for it? We
> > > > > > can keep a copy in the Linux source tree for perf to use till it    
> > > > > 
> > > > > so libbpf 'moved' for this reason to github repo,
> > > > > but keeping the kernel as the true/first source,
> > > > > and updating github repo when release is ready
> > > > > 
> > > > > libbpf github repo is then source for fedora (and others)
> > > > > package  
> > > > 
> > > > Ah, so perhaps I should follow this? I could keep it a kernel.org repo
> > > > (as I rather have it there anyway).  
> > > 
> > > sounds good, and if it works out, we'll follow you with libperf :-)
> > > 
> > > if you want to check on the libbpf:
> > >   https://github.com/libbpf/libbpf
> > > 
> > > there might be some syncs scripts worth checking
> > 
> > I wonder if there should be a:
> > 
> >   git://git.kernel.org/pub/scm/utils/lib/
> > 
> > directory to have:
> > 
> >   git://git.kernel.org/pub/scm/utils/lib/traceevent/
> >   git://git.kernel.org/pub/scm/utils/lib/libbpf/
> >   git://git.kernel.org/pub/scm/utils/lib/libperf/
> 
> we could loose the 'lib' and just have:
> 
>     git://git.kernel.org/pub/scm/utils/lib/perf/

So, we have:

https://www.kernel.org/pub/linux/kernel/tools/perf/

trying to mimic the kernel sources tree structure, so perhaps we could
have:

https://www.kernel.org/pub/linux/kernel/tools/lib/{perf,traceevent}/

To continue that directory tree mirror?

> > That could hold the libraries that are tight to the kernel?

> I don't think libbpf will change now after they are settled in github,
> but we could consider this for libperf
> 
> jirka

-- 

- Arnaldo