From: mathieu.poirier@linaro.org (Mathieu Poirier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] coresight: Don't use contextID with PID namespaces
Date: Tue, 15 May 2018 11:13:34 -0600 [thread overview]
Message-ID: <1526404417-32507-1-git-send-email-mathieu.poirier@linaro.org> (raw)
Since the in-kernel value of a PID differs from what is seen from
PID namespaces, using contextID tracing with PID namespaces makes the
feature confusing to use and potentially subject to leaking out internal
kernel information.
This set returns an error if contextID and PID namespaces are used in
conjunction and gets rid of the vpid-to-pid translation function as it
is no longer needed.
Thanks,
Mathieu
Mathieu Poirier (3):
coresight: etm3x: Don't use contextID with PID namespaces
coresight: etm4x: Don't use contextID with PID namespaces
coresight: Remove function coresight_vpid_to_pid()
drivers/hwtracing/coresight/coresight-etm.h | 3 --
.../hwtracing/coresight/coresight-etm3x-sysfs.c | 43 +++++++++++++++++---
drivers/hwtracing/coresight/coresight-etm3x.c | 4 +-
.../hwtracing/coresight/coresight-etm4x-sysfs.c | 47 +++++++++++++++++-----
drivers/hwtracing/coresight/coresight-etm4x.h | 3 --
include/linux/coresight.h | 20 ---------
6 files changed, 76 insertions(+), 44 deletions(-)
--
2.7.4
next reply other threads:[~2018-05-15 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 17:13 Mathieu Poirier [this message]
2018-05-15 17:13 ` [PATCH 1/3] coresight: etm3x: Don't use contextID with PID namespaces Mathieu Poirier
2018-05-15 17:13 ` [PATCH 2/3] coresight: etm4x: " Mathieu Poirier
2018-05-15 17:13 ` [PATCH 3/3] coresight: Remove function coresight_vpid_to_pid() Mathieu Poirier
2018-05-16 17:44 ` [PATCH 0/3] coresight: Don't use contextID with PID namespaces Kim Phillips
2018-05-17 1:12 ` Eric W. Biederman
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=1526404417-32507-1-git-send-email-mathieu.poirier@linaro.org \
--to=mathieu.poirier@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).