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-next>] [day] [month] [year] [list]
Date:   Thu, 17 Nov 2022 09:59:46 -0800
From:   Ian Rogers <irogers@...gle.com>
To:     Arnaldo Carvalho de Melo <acme@...nel.org>,
        Steven Rostedt <rostedt@...gle.com>
Cc:     Namhyung Kim <namhyung@...nel.org>, Jiri Olsa <jolsa@...nel.org>,
        Adrian Hunter <adrian.hunter@...el.com>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-perf-users <linux-perf-users@...r.kernel.org>,
        Linux Trace Devel <linux-trace-devel@...r.kernel.org>
Subject: Remove traceevent from tools/lib

Hi,

Arnaldo raised defaulting BUiLD_BPF_SKEL in the perf tool build:
https://lore.kernel.org/lkml/Y3Yy5DFEoCEBv%2FQi@kernel.org/

The recent build clean up:
https://lore.kernel.org/lkml/20221109184914.1357295-1-irogers@google.com/
https://lore.kernel.org/lkml/20221116224631.207631-1-irogers@google.com/

Means that perf is cleanly(ish) separated from libraries in tools/lib.
traceevent in tools/lib is out of date (~2years - version 1.1.0 whilst
the latest is 1.6.3 [1]) . Should we delete traceevent from tools/lib
and just make LIBTRACEEVENT_DYNAMIC the only supported perf build
option? I guess this may break old distributions that may not have
libtraceevent, but even so I'm not sure that should motivate not
cleaning this up (if they are building perf they can build
libtraceevent).

Thanks,
Ian

[1] https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/tree/Makefile

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ