Fix: use proper pid_ns in the process statedump
authorMichael Jeanson <mjeanson@efficios.com>
Wed, 21 Feb 2018 21:36:17 +0000 (16:36 -0500)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Wed, 21 Feb 2018 21:42:55 +0000 (16:42 -0500)
commit887bcdac230a9081d5088bde59725edab93b8fb7
treed26dfd528c052f61e4e336ff39190eca6ebb05f9
parent8a71de6c7995151de4dc8d7274bd4a5e1a2f4f9d
Fix: use proper pid_ns in the process statedump

The pid_ns we currently use from the nsproxy struct is not the task's
pid_ns but the one that children of this task will use.

As stated in include/linux/nsproxy.h :

  The pid namespace is an exception -- it's accessed using
  task_active_pid_ns.  The pid namespace here is the
  namespace that children will use.

While it will be the same most of the time, it will report incorrect
information in some situations. Plus it has the side effect of
simplifying the code and removing kernel version checks.

Signed-off-by: Michael Jeanson <mjeanson@efficios.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
lttng-statedump-impl.c
wrapper/nsproxy.h [deleted file]
This page took 0.025538 seconds and 4 git commands to generate.