summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorChristian Brauner <christian.brauner@ubuntu.com>2018-02-07 13:53:20 +0100
committerDavid S. Miller <davem@davemloft.net>2018-02-08 14:33:20 -0500
commit4ff66cae7f10b65b028dc3bdaaad9cc2989ef6ae (patch)
tree18b63a85d9a6bbcfcb3674e0c57e684f8a671104 /drivers
parent762c330d670e3d4b795cf7a8d761866fdd1eef49 (diff)
downloadop-kernel-dev-4ff66cae7f10b65b028dc3bdaaad9cc2989ef6ae.zip
op-kernel-dev-4ff66cae7f10b65b028dc3bdaaad9cc2989ef6ae.tar.gz
rtnetlink: require unique netns identifier
Since we've added support for IFLA_IF_NETNSID for RTM_{DEL,GET,SET,NEW}LINK it is possible for userspace to send us requests with three different properties to identify a target network namespace. This affects at least RTM_{NEW,SET}LINK. Each of them could potentially refer to a different network namespace which is confusing. For legacy reasons the kernel will pick the IFLA_NET_NS_PID property first and then look for the IFLA_NET_NS_FD property but there is no reason to extend this type of behavior to network namespace ids. The regression potential is quite minimal since the rtnetlink requests in question either won't allow IFLA_IF_NETNSID requests before 4.16 is out (RTM_{NEW,SET}LINK) or don't support IFLA_NET_NS_{PID,FD} (RTM_{DEL,GET}LINK) in the first place. Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com> Acked-by: Jiri Benc <jbenc@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud