[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180131162048.iy67tccusgceajgw@gmail.com>
Date: Wed, 31 Jan 2018 17:20:49 +0100
From: Christian Brauner <christian.brauner@...onical.com>
To: David Miller <davem@...emloft.net>
Cc: christian.brauner@...ntu.com, netdev@...r.kernel.org,
ebiederm@...ssion.com, dsahern@...il.com, fw@...len.de,
daniel@...earbox.net, lucien.xin@...il.com,
mschiffer@...verse-factory.net, jakub.kicinski@...ronome.com,
vyasevich@...il.com, linux-kernel@...r.kernel.org,
jbenc@...hat.com, w.bumiller@...xmox.com, nicolas.dichtel@...nd.com
Subject: Re: [PATCH net-next 1/1] rtnetlink: enable IFLA_IF_NETNSID for
RTM_NEWLINK
On Wed, Jan 31, 2018 at 10:30:44AM -0500, David Miller wrote:
> From: Christian Brauner <christian.brauner@...ntu.com>
> Date: Mon, 29 Jan 2018 18:07:20 +0100
>
> > - Backwards Compatibility:
> > If userspace wants to determine whether RTM_NEWLINK 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_NEWLINK with a IFLA_IF_NETNSID property. If they receive
> > EOPNOTSUPP then the kernel does not support the IFLA_IF_NETNSID property
> > with RTM_NEWLINK. Userpace should then fallback to other means.
> >
> > - Security:
> > Callers must have CAP_NET_ADMIN in the owning user namespace of the
> > target network namespace.
> >
> > Signed-off-by: Christian Brauner <christian.brauner@...ntu.com>
>
> Applied.
Thanks!
Powered by blists - more mailing lists