ip netns exec <netns> kill <pid> doesn't make sense

[Isaku Yamahata]

There are several code which executes
ip netns exec <netns> kill <pid>

Since pidns is different from netns, it doesn't make sense. Just kill <pid> works.
As side effects, 'ip netns exec' referes /var/run/netns/<netns> which is bind-mounted to
/proc/<pid>/ns/net. It makes the corresponding dentry young, which increases the possibility
to fail to delete netns. That's bad.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/25094

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/25094
Committed: http://github.com/openstack/quantum/commit/4d72093de571c2a12dc12c3761e3bcec11ccf20e
Submitter: Jenkins
Branch: master

commit 4d72093de571c2a12dc12c3761e3bcec11ccf20e
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
    Change-Id: I9aa717ccb86d8bf00bb1e707d39bfb65d043532b
    Signed-off-by: Isaku Yamahata <email address hidden>