From: Christian Brauner <christian.brauner@canonical.com>
To: David Miller <davem@davemloft.net>
Cc: christian.brauner@ubuntu.com, netdev@vger.kernel.org,
ebiederm@xmission.com, dsahern@gmail.com, fw@strlen.de,
daniel@iogearbox.net, lucien.xin@gmail.com,
mschiffer@universe-factory.net, jakub.kicinski@netronome.com,
vyasevich@gmail.com, linux-kernel@vger.kernel.org,
jbenc@redhat.com, w.bumiller@proxmox.com,
nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next 1/1] rtnetlink: enable IFLA_IF_NETNSID for RTM_NEWLINK
Date: Wed, 31 Jan 2018 17:20:49 +0100 [thread overview]
Message-ID: <20180131162048.iy67tccusgceajgw@gmail.com> (raw)
In-Reply-To: <20180131.103044.1805785714040464628.davem@davemloft.net>
On Wed, Jan 31, 2018 at 10:30:44AM -0500, David Miller wrote:
> From: Christian Brauner <christian.brauner@ubuntu.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@ubuntu.com>
>
> Applied.
Thanks!
prev parent reply other threads:[~2018-01-31 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 17:07 [PATCH net-next 0/1] " Christian Brauner
2018-01-29 17:07 ` [PATCH net-next 1/1] " Christian Brauner
2018-01-30 15:49 ` kbuild test robot
2018-01-30 16:13 ` kbuild test robot
2018-01-30 16:26 ` Christian Brauner
2018-01-31 15:30 ` David Miller
2018-01-31 16:20 ` Christian Brauner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180131162048.iy67tccusgceajgw@gmail.com \
--to=christian.brauner@canonical.com \
--cc=christian.brauner@ubuntu.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=ebiederm@xmission.com \
--cc=fw@strlen.de \
--cc=jakub.kicinski@netronome.com \
--cc=jbenc@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=mschiffer@universe-factory.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=vyasevich@gmail.com \
--cc=w.bumiller@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome