From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Jiri Olsa <jolsa@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
James Morris <jmorris@namei.org>
Subject: RE: [PATCH 1/3] perf: Add capability-related utilities
Date: Wed, 7 Aug 2019 03:58:33 +0000 [thread overview]
Message-ID: <cad08a5b8706443eb43d9c3ec13e1ad0@usma1ex-dag1mb6.msg.corp.akamai.com> (raw)
In-Reply-To: <20190717234652.GJ3624@kernel.org>
On Wed, July 17 at 2019 7:47 PM Arnaldo Carvalho de Melo wrote:
> Em Wed, Jul 17, 2019 at 06:05:51PM -0300, Arnaldo Carvalho de Melo
> escreveu:
> > Em Tue, Jul 16, 2019 at 10:46:43AM +0200, Jiri Olsa escreveu:
> > > On Tue, Jul 02, 2019 at 08:10:03PM -0400, Igor Lubashev wrote:
> > > > Add utilities to help checking capabilities of the running process.
> > > > Make perf link with libcap.
> > > >
> > > > Signed-off-by: Igor Lubashev <ilubashe@akamai.com>
> > > > ---
> > > > tools/perf/Makefile.config | 2 +-
> > > > tools/perf/util/Build | 1 +
> > > > tools/perf/util/cap.c | 24 ++++++++++++++++++++++++
> > > > tools/perf/util/cap.h | 10 ++++++++++
> > > > tools/perf/util/event.h | 1 +
> > > > tools/perf/util/python-ext-sources | 1 +
> > > > tools/perf/util/util.c | 9 +++++++++
> > > > 7 files changed, 47 insertions(+), 1 deletion(-) create mode
> > > > 100644 tools/perf/util/cap.c create mode 100644
> > > > tools/perf/util/cap.h
> > > >
> > > > diff --git a/tools/perf/Makefile.config
> > > > b/tools/perf/Makefile.config index 85fbcd265351..21470a50ed39
> > > > 100644
> > > > --- a/tools/perf/Makefile.config
> > > > +++ b/tools/perf/Makefile.config
> > > > @@ -259,7 +259,7 @@ CXXFLAGS += -Wno-strict-aliasing # adding
> > > > assembler files missing the .GNU-stack linker note.
> > > > LDFLAGS += -Wl,-z,noexecstack
> > > >
> > > > -EXTLIBS = -lpthread -lrt -lm -ldl
> > > > +EXTLIBS = -lpthread -lrt -lm -ldl -lcap
> > >
> > > I wonder we should detect libcap or it's everywhere.. Arnaldo's
> > > compile test suite might tell
> >
> > I'll add this tentatively and try to build it in my test suite.
>
> So, not even in my notebook this worked straight away:
>
> CC /tmp/build/perf/util/cap.o
> CC /tmp/build/perf/util/config.o
> In file included from util/cap.c:5:
> util/cap.h:6:10: fatal error: sys/capability.h: No such file or directory
> 6 | #include <sys/capability.h>
> | ^~~~~~~~~~~~~~~~~~
> compilation terminated.
> mv: cannot stat '/tmp/build/perf/util/.cap.o.tmp': No such file or directory
>
>
> I had to first do:
>
> dnf install libcap-devel
>
> So we need to have a feature test and fail if that is not installed, i.e. libcap
> becomes a hard req for building perf, which I think is reasonable, one more
> shouldn't hurt, right?
>
> With all the features enabled:
>
> [acme@quaco perf]$ ldd ~/bin/perf
> linux-vdso.so.1 (0x00007ffe7278a000)
> libunwind-x86_64.so.8 => /lib64/libunwind-x86_64.so.8
> (0x00007f7be52f1000)
> libunwind.so.8 => /lib64/libunwind.so.8 (0x00007f7be52d7000)
> liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f7be52ae000)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7be528d000)
> librt.so.1 => /lib64/librt.so.1 (0x00007f7be5283000)
> libm.so.6 => /lib64/libm.so.6 (0x00007f7be513d000)
> libdl.so.2 => /lib64/libdl.so.2 (0x00007f7be5135000)
> libcap.so.2 => /lib64/libcap.so.2 (0x00007f7be512e000)
> libelf.so.1 => /lib64/libelf.so.1 (0x00007f7be5113000)
> libdw.so.1 => /lib64/libdw.so.1 (0x00007f7be50c0000)
> libslang.so.2 => /lib64/libslang.so.2 (0x00007f7be4de8000)
> libperl.so.5.28 => /lib64/libperl.so.5.28 (0x00007f7be4ac2000)
> libc.so.6 => /lib64/libc.so.6 (0x00007f7be48fa000)
> libpython2.7.so.1.0 => /lib64/libpython2.7.so.1.0
> (0x00007f7be4690000)
> libz.so.1 => /lib64/libz.so.1 (0x00007f7be4676000)
> libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f7be45d1000)
> libnuma.so.1 => /lib64/libnuma.so.1 (0x00007f7be45c3000)
> libbabeltrace-ctf.so.1 => /lib64/libbabeltrace-ctf.so.1
> (0x00007f7be456d000)
> libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f7be4551000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f7be5331000)
> libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f7be453d000)
> libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007f7be4502000)
> libutil.so.1 => /lib64/libutil.so.1 (0x00007f7be44fd000)
> libbabeltrace.so.1 => /lib64/libbabeltrace.so.1
> (0x00007f7be44ed000)
> libpopt.so.0 => /lib64/libpopt.so.0 (0x00007f7be44dd000)
> libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f7be44d3000)
> libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0
> (0x00007f7be44cd000)
> libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f7be43a9000)
> libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f7be4335000)
> [acme@quaco perf]$
>
> ;-)
>
> So, please check tools/build/feature/ and check how this is done and add a
> test and the warning in tools/perf/Makefile.config so that we get an error
> message stating that libcap-dev or libcap-devel should be installed.
I have just posted v2 of the series (https://lkml.kernel.org/lkml/cover.1565146171.git.ilubashe@akamai.com).
Instead of making libcap is "hard req", I made it as "soft" one. We can still build a useful tool w/o libcap. It will just have to assume that perf is running with no capabilities, since we cannot query them.
Many thanks for the pointers on how to go about build feature checking.
- Igor
next prev parent reply other threads:[~2019-08-07 3:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 0:10 [PATCH 0/3] perf: Use capabilities instead of uid and euid Igor Lubashev
2019-07-03 0:10 ` [PATCH 1/3] perf: Add capability-related utilities Igor Lubashev
2019-07-16 8:46 ` Jiri Olsa
2019-07-17 21:05 ` Arnaldo Carvalho de Melo
2019-07-17 23:46 ` Arnaldo Carvalho de Melo
2019-07-17 23:48 ` Arnaldo Carvalho de Melo
2019-07-18 21:00 ` Lubashev, Igor
2019-08-07 3:58 ` Lubashev, Igor [this message]
2019-07-03 0:10 ` [PATCH 2/3] perf: Use CAP_SYS_ADMIN with perf_event_paranoid checks Igor Lubashev
2019-07-16 8:47 ` Jiri Olsa
2019-07-16 17:01 ` Lubashev, Igor
2019-07-17 7:10 ` Jiri Olsa
2019-07-17 18:33 ` Lubashev, Igor
2019-07-03 0:10 ` [PATCH 3/3] perf: Use CAP_SYSLOG with kptr_restrict checks Igor Lubashev
2019-07-16 10:51 ` [PATCH 0/3] perf: Use capabilities instead of uid and euid Alexey Budankov
2019-07-17 18:15 ` [PATCH 4/3] perf: Use CAP_SYS_ADMIN instead of euid==0 with ftrace Igor Lubashev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cad08a5b8706443eb43d9c3ec13e1ad0@usma1ex-dag1mb6.msg.corp.akamai.com \
--to=ilubashe@akamai.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=jmorris@namei.org \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).