From: Brendan Gregg <brendan.d.gregg@gmail.com>
To: "linux-perf-use." <linux-perf-users@vger.kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>
Subject: perf segfault in docker container
Date: Thu, 9 Jun 2016 14:14:11 -0700 [thread overview]
Message-ID: <CAE40pdfWpz6rreOCMJCs1P8WXfOXO_B5zZoeOyC_5usYGp8xRQ@mail.gmail.com> (raw)
G'Day,
Default docker container, in Linux 4.7-rc2, with latest perf from perf/core:
docker# ./perf record -F 99 -a
Segmentation fault
The segfault is in perf_event__synthesize_kernel_mmap(). I know
symbol__read_kptr_restrict() has been updated recently to fix similar
segfaults, hence getting perf/core.
I think the problem is this:
docker# id
uid=0(root) gid=0(root) groups=0(root)
docker# cat /proc/sys/kernel/kptr_restrict
1
(I'd previously set "echo -1 > /proc/sys/kernel/perf_event_paranoid")
The current (May 24) code has, symbol__read_kptr_restrict():
if (fgets(line, sizeof(line), fp) != NULL)
value = (geteuid() != 0) ?
(atoi(line) != 0) :
(atoi(line) == 2);
assumes that if euid is 0 && kptr_restrict isn't 2, then we're aren't
restricted. But we are. Maybe the code should check for CAP_SYS_ADMIN,
instead of euid == 0?
Brendan
next reply other threads:[~2016-06-09 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 21:14 Brendan Gregg [this message]
2016-06-10 10:28 ` perf segfault in docker container Aravinda Prasad
2016-06-21 22:32 ` Brendan Gregg
2016-06-21 22:43 ` Brendan Gregg
2016-06-22 21:35 ` Aravinda Prasad
2016-06-10 20:15 ` Arnaldo Carvalho de Melo
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=CAE40pdfWpz6rreOCMJCs1P8WXfOXO_B5zZoeOyC_5usYGp8xRQ@mail.gmail.com \
--to=brendan.d.gregg@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=wangnan0@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.