From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: davem@davemloft.net, jasowang@redhat.com, edumazet@google.com,
xiyou.wangcong@gmail.com, willemb@google.com,
peterpenkov96@gmail.com, linyu.yuan@alcatel-sbell.com.cn,
kstewart@linuxfoundation.org, aviadye@mellanox.com,
gregkh@linuxfoundation.org, ktkhai@virtuozzo.com,
davejwatson@fb.com, netdev@vger.kernel.org
Subject: [PATCH net-next v2 0/3] Add ioctl() SIOCGSKNS cmd to allow obtaining net ns of tun device
Date: Wed, 14 Feb 2018 16:39:45 +0300 [thread overview]
Message-ID: <151861548493.9376.6162694167471967.stgit@localhost.localdomain> (raw)
Currently, it's not possible to get or check net namespace,
which was used to create tun socket. User may have two tun
devices with the same names in different nets, and there
is no way to differ them each other.
The patchset adds support for ioctl() cmd SIOCGSKNS for tun
devices. It will allow people to obtain net namespace file
descriptor like we allow to do that for sockets in general.
v2: Add new patch [2/3] to export open_related_ns().
---
Kirill Tkhai (3):
net: Make extern and export get_net_ns()
net: Export open_related_ns()
tun: Add ioctl() SIOCGSKNS cmd to allow obtaining net ns of tun device
drivers/net/tun.c | 16 ++++++++++++++--
fs/nsfs.c | 1 +
include/linux/socket.h | 2 ++
net/socket.c | 3 ++-
4 files changed, 19 insertions(+), 3 deletions(-)
next reply other threads:[~2018-02-14 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 13:39 Kirill Tkhai [this message]
2018-02-14 13:39 ` [PATCH net-next v2 1/3] net: Make extern and export get_net_ns() Kirill Tkhai
2018-02-14 13:40 ` [PATCH net-next v2 2/3] net: Export open_related_ns() Kirill Tkhai
2018-02-14 13:40 ` [PATCH net-next v2 3/3] tun: Add ioctl() SIOCGSKNS cmd to allow obtaining net ns of tun device Kirill Tkhai
2018-02-15 20:35 ` [PATCH net-next v2 0/3] " David Miller
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=151861548493.9376.6162694167471967.stgit@localhost.localdomain \
--to=ktkhai@virtuozzo.com \
--cc=aviadye@mellanox.com \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kstewart@linuxfoundation.org \
--cc=linyu.yuan@alcatel-sbell.com.cn \
--cc=netdev@vger.kernel.org \
--cc=peterpenkov96@gmail.com \
--cc=willemb@google.com \
--cc=xiyou.wangcong@gmail.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