Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Russell King - ARM Linux writes: > On Thu, May 10, 2018 at 01:39:18PM -0600, Mathieu Poirier wrote: >> Hi Russell, >> >> On 10 May 2018 at 02:40, Russell King - ARM Linux >> wrote: >> > This does not leak information from other namespaces because

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Russell King - ARM Linux writes: > On Thu, May 10, 2018 at 01:39:18PM -0600, Mathieu Poirier wrote: >> Hi Russell, >> >> On 10 May 2018 at 02:40, Russell King - ARM Linux >> wrote: >> > This does not leak information from other namespaces because of the >> > uniqueness of the global PID.

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

On Thu, May 10, 2018 at 01:39:18PM -0600, Mathieu Poirier wrote: > Hi Russell, > > On 10 May 2018 at 02:40, Russell King - ARM Linux > wrote: > > This does not leak information from other namespaces because of the > > uniqueness of the global PID. However, what it does

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

On Thu, May 10, 2018 at 01:39:18PM -0600, Mathieu Poirier wrote: > Hi Russell, > > On 10 May 2018 at 02:40, Russell King - ARM Linux > wrote: > > This does not leak information from other namespaces because of the > > uniqueness of the global PID. However, what it does leak is the value > > of

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

On 10 May 2018 at 02:40, Russell King - ARM Linux wrote: > On Wed, May 09, 2018 at 09:35:07PM -0500, Eric W. Biederman wrote: >> Mathieu Poirier writes: >> >> > On Tue, May 08, 2018 at 11:59:38PM -0500, Eric W. Biederman wrote: >> >> Kim

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

On 10 May 2018 at 02:40, Russell King - ARM Linux wrote: > On Wed, May 09, 2018 at 09:35:07PM -0500, Eric W. Biederman wrote: >> Mathieu Poirier writes: >> >> > On Tue, May 08, 2018 at 11:59:38PM -0500, Eric W. Biederman wrote: >> >> Kim Phillips writes: >> >> >> >> > This patch is in the

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

On Wed, May 09, 2018 at 09:35:07PM -0500, Eric W. Biederman wrote: > Mathieu Poirier writes: > > > On Tue, May 08, 2018 at 11:59:38PM -0500, Eric W. Biederman wrote: > >> Kim Phillips writes: > >> > >> > This patch is in the context of allowing

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

On Wed, May 09, 2018 at 09:35:07PM -0500, Eric W. Biederman wrote: > Mathieu Poirier writes: > > > On Tue, May 08, 2018 at 11:59:38PM -0500, Eric W. Biederman wrote: > >> Kim Phillips writes: > >> > >> > This patch is in the context of allowing the Coresight h/w > >> > trace driver suite to be

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Mathieu Poirier writes: > On Tue, May 08, 2018 at 11:59:38PM -0500, Eric W. Biederman wrote: >> Kim Phillips writes: >> >> > This patch is in the context of allowing the Coresight h/w >> > trace driver suite to be loaded as modules. Coresight

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Mathieu Poirier writes: > On Tue, May 08, 2018 at 11:59:38PM -0500, Eric W. Biederman wrote: >> Kim Phillips writes: >> >> > This patch is in the context of allowing the Coresight h/w >> > trace driver suite to be loaded as modules. Coresight uses >> > find_task_by_vpid when running in direct

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

On Tue, May 08, 2018 at 11:59:38PM -0500, Eric W. Biederman wrote: > Kim Phillips writes: > > > This patch is in the context of allowing the Coresight h/w > > trace driver suite to be loaded as modules. Coresight uses > > find_task_by_vpid when running in direct capture

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

On Tue, May 08, 2018 at 11:59:38PM -0500, Eric W. Biederman wrote: > Kim Phillips writes: > > > This patch is in the context of allowing the Coresight h/w > > trace driver suite to be loaded as modules. Coresight uses > > find_task_by_vpid when running in direct capture mode (via sysfs) > >

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Hi Eric, On 09/05/18 05:59, Eric W. Biederman wrote: Kim Phillips writes: This patch is in the context of allowing the Coresight h/w trace driver suite to be loaded as modules. Coresight uses find_task_by_vpid when running in direct capture mode (via sysfs) when

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Hi Eric, On 09/05/18 05:59, Eric W. Biederman wrote: Kim Phillips writes: This patch is in the context of allowing the Coresight h/w trace driver suite to be loaded as modules. Coresight uses find_task_by_vpid when running in direct capture mode (via sysfs) when getting/setting the context

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Kim Phillips writes: > This patch is in the context of allowing the Coresight h/w > trace driver suite to be loaded as modules. Coresight uses > find_task_by_vpid when running in direct capture mode (via sysfs) > when getting/setting the context ID comparator to trigger on

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Kim Phillips writes: > This patch is in the context of allowing the Coresight h/w > trace driver suite to be loaded as modules. Coresight uses > find_task_by_vpid when running in direct capture mode (via sysfs) > when getting/setting the context ID comparator to trigger on >

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Kim Phillips writes: > This patch is in the context of allowing the Coresight h/w > trace driver suite to be loaded as modules. Coresight uses > find_task_by_vpid when running in direct capture mode (via sysfs) > when getting/setting the context ID comparator to trigger on

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Kim Phillips writes: > This patch is in the context of allowing the Coresight h/w > trace driver suite to be loaded as modules. Coresight uses > find_task_by_vpid when running in direct capture mode (via sysfs) > when getting/setting the context ID comparator to trigger on >