Update statedump to 3.17 nsproxy locking
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 21 Aug 2014 14:53:12 +0000 (10:53 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 21 Aug 2014 14:53:12 +0000 (10:53 -0400)
commit4ba1f53c5aebb4433fedc25d65af010274985043
tree760853df1fd5ab5e2449d4791a74ba4bacdf4009
parentd3de7f1468be0b18145ff85b3c1a7c7fb1d48c15
Update statedump to 3.17 nsproxy locking

This Linux upstream commit introduces locking strategy back and forth:

commit 728dba3a39c66b3d8ac889ddbe38b5b1c264aec3
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Mon Feb 3 19:13:49 2014 -0800

    namespaces: Use task_lock and not rcu to protect nsproxy

Use the task lock starting from kernel 3.17 rather than RCU to access
the task nsproxy.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
lttng-statedump-impl.c
This page took 0.027755 seconds and 4 git commands to generate.