From: ebiederm@xmission.com (Eric W. Biederman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] coresight: Don't use contextID with PID namespaces
Date: Wed, 16 May 2018 20:12:26 -0500 [thread overview]
Message-ID: <87po1vjdad.fsf@xmission.com> (raw)
In-Reply-To: <1526404417-32507-1-git-send-email-mathieu.poirier@linaro.org> (Mathieu Poirier's message of "Tue, 15 May 2018 11:13:34 -0600")
Mathieu Poirier <mathieu.poirier@linaro.org> writes:
> 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.
I looked the file can only be written by root. So limiting things to
the initial pid namespace seems like the right solutions. Especially as
the trace stream will include the global pid and be available to the
tracer.
This sounds like a simple code with a minimal chance of breaking
userspace.
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
prev parent reply other threads:[~2018-05-17 1:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 17:13 [PATCH 0/3] coresight: Don't use contextID with PID namespaces Mathieu Poirier
2018-05-15 17:13 ` [PATCH 1/3] coresight: etm3x: " 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 [this message]
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=87po1vjdad.fsf@xmission.com \
--to=ebiederm@xmission.com \
--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 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.