On Mon, Sep 09, 2013 at 01:01:41PM +0200, Peter Zijlstra wrote:
> On Tue, Sep 03, 2013 at 04:22:33PM +0200, Emmanuel Deloget wrote:
> > The issue (if this is really an issue) lies in kernel/sched/debug.c,
> > function proc_sched_show_task(). The code says [1]:
> >
> > SEQ_printf(m, "%s (%d, #t
Hello,
On 09/09/2013 13:01, Peter Zijlstra wrote:
> On Tue, Sep 03, 2013 at 04:22:33PM +0200, Emmanuel Deloget wrote:
>> The issue (if this is really an issue) lies in kernel/sched/debug.c,
>> function proc_sched_show_task(). The code says [1]:
>>
>> SEQ_printf(m, "%s (%d, #threads: %d)\n", p-
On Tue, Sep 03, 2013 at 04:22:33PM +0200, Emmanuel Deloget wrote:
> The issue (if this is really an issue) lies in kernel/sched/debug.c,
> function proc_sched_show_task(). The code says [1]:
>
> SEQ_printf(m, "%s (%d, #threads: %d)\n", p->comm, p->pid,
> get_nr_threads(
Hello,
(please CC me when answering this mail ; and sorry for my borken
English).
I noticed that when a process is executed in a PID namespace it can
still find his real PID by parsing /proc/$PID_IN_NS/sched.
(in this example I created a new PID namespace and ran /bin/bash at
PID 1)
# uname -
4 matches
Mail list logo