netns: ip netns exec <name> kill doesn't make sense
It seems confusing netns with pidns.
Although 'ip netns exec' doesn't make sense,
'ip netns exec <netns> kill <pid>' itself success as expected.
But as side effects, dentry of /proc/<pid>/ns/net becomes young,
which increases the possibility to fail to delete netns. That's not good.
Reviewed: https:/ /review. openstack. org/25094 github. com/openstack/ quantum/ commit/ 4d72093de571c2a 12dc12c3761e3bc ec11ccf20e
Committed: http://
Submitter: Jenkins
Branch: master
commit 4d72093de571c2a 12dc12c3761e3bc ec11ccf20e
Author: Isaku Yamahata <email address hidden>
Date: Tue Mar 19 06:56:15 2013 +0900
netns: ip netns exec <name> kill doesn't make sense
It seems confusing netns with pidns.
Although 'ip netns exec' doesn't make sense,
'ip netns exec <netns> kill <pid>' itself success as expected.
But as side effects, dentry of /proc/<pid>/ns/net becomes young,
which increases the possibility to fail to delete netns. That's not good.
Fixes: Bug #1158589 f00bb1e707d39bf b65d043532b
Change-Id: I9aa717ccb86d8b
Signed-off-by: Isaku Yamahata <email address hidden>