From: David Miller <davem@davemloft.net>
To: ktkhai@virtuozzo.com
Cc: 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, davejwatson@fb.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/3] Add ioctl() SIOCGSKNS cmd to allow obtaining net ns of tun device
Date: Thu, 15 Feb 2018 15:35:32 -0500 (EST) [thread overview]
Message-ID: <20180215.153532.1034078541331191429.davem@davemloft.net> (raw)
In-Reply-To: <151861548493.9376.6162694167471967.stgit@localhost.localdomain>
From: Kirill Tkhai <ktkhai@virtuozzo.com>
Date: Wed, 14 Feb 2018 16:39:45 +0300
> 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().
Series applied, thanks.
prev parent reply other threads:[~2018-02-15 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 13:39 [PATCH net-next v2 0/3] Add ioctl() SIOCGSKNS cmd to allow obtaining net ns of tun device Kirill Tkhai
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 ` David Miller [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=20180215.153532.1034078541331191429.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aviadye@mellanox.com \
--cc=davejwatson@fb.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kstewart@linuxfoundation.org \
--cc=ktkhai@virtuozzo.com \
--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;
as well as URLs for NNTP newsgroup(s).