summaryrefslogtreecommitdiff
path: root/net/core/lwtunnel.c
diff options
context:
space:
mode:
authorChristian Brauner <christianvanbrauner@gmail.com>2018-01-24 17:26:33 +0300
committerDavid S. Miller <davem@davemloft.net>2018-01-29 19:31:06 +0300
commitc310bfcb6e1be993629c5747accf8e1c65fbb255 (patch)
tree93a5c9e71fcb0c60b662d81e1a4b7b215d39d21f /net/core/lwtunnel.c
parent7c4f63ba824302492985553018881455982241d6 (diff)
downloadlinux-c310bfcb6e1be993629c5747accf8e1c65fbb255.tar.xz
rtnetlink: enable IFLA_IF_NETNSID for RTM_SETLINK
- Backwards Compatibility: If userspace wants to determine whether RTM_SETLINK supports the IFLA_IF_NETNSID property they should first send an RTM_GETLINK request with IFLA_IF_NETNSID on lo. If either EACCESS is returned or the reply does not include IFLA_IF_NETNSID userspace should assume that IFLA_IF_NETNSID is not supported on this kernel. If the reply does contain an IFLA_IF_NETNSID property userspace can send an RTM_SETLINK with a IFLA_IF_NETNSID property. If they receive EOPNOTSUPP then the kernel does not support the IFLA_IF_NETNSID property with RTM_SETLINK. Userpace should then fallback to other means. To retain backwards compatibility the kernel will first check whether a IFLA_NET_NS_PID or IFLA_NET_NS_FD property has been passed. If either one is found it will be used to identify the target network namespace. This implies that users who do not care whether their running kernel supports IFLA_IF_NETNSID with RTM_SETLINK can pass both IFLA_NET_NS_{FD,PID} and IFLA_IF_NETNSID referring to the same network namespace. - Security: Callers must have CAP_NET_ADMIN in the owning user namespace of the target network namespace. Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/core/lwtunnel.c')
0 files changed, 0 insertions, 0 deletions