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:43:15 +0000 (16:43 -0500)
commitaba7d7fc4ec0cf2828ed50b22d6171074635e856
tree4a6513b99e49b9fbfb3ede3c677cc53f5aa0885d
parent6ffbd2c763bc17c061306e065bf738a880c0ac58
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.025927 seconds and 4 git commands to generate.