aboutsummaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorChristian Brauner <christian@brauner.io>2018-09-04 21:53:49 +0200
committerDavid S. Miller <davem@davemloft.net>2018-09-05 22:27:11 -0700
commitd38071455ffb553ffa9f63d3c8e6af13c42da512 (patch)
tree5d24b0f6b7f9393e54843836e33a7b047d88d1bd /fs
parentif_addr: add IFA_TARGET_NETNSID (diff)
downloadlinux-dev-d38071455ffb553ffa9f63d3c8e6af13c42da512.tar.xz
linux-dev-d38071455ffb553ffa9f63d3c8e6af13c42da512.zip
ipv4: enable IFA_TARGET_NETNSID for RTM_GETADDR
- Backwards Compatibility: If userspace wants to determine whether ipv4 RTM_GETADDR requests support the new IFA_TARGET_NETNSID property it should verify that the reply includes the IFA_TARGET_NETNSID property. If it does not userspace should assume that IFA_TARGET_NETNSID is not supported for ipv4 RTM_GETADDR requests on this kernel. - From what I gather from current userspace tools that make use of RTM_GETADDR requests some of them pass down struct ifinfomsg when they should actually pass down struct ifaddrmsg. To not break existing tools that pass down the wrong struct we will do the same as for RTM_GETLINK | NLM_F_DUMP requests and not error out when the nlmsg_parse() fails. - Security: Callers must have CAP_NET_ADMIN in the owning user namespace of the target network namespace. Signed-off-by: Christian Brauner <christian@brauner.io> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions