From: Harald Welte <laforge@gnumonks.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: loosing netdevices with namespaces and unshare?
Date: Thu, 1 Jun 2017 09:00:31 +0200 [thread overview]
Message-ID: <20170601070031.mdycexartsu33fyd@nataraja> (raw)
In-Reply-To: <87a85si5f2.fsf@xmission.com>
Hi Eric,
On Thu, Jun 01, 2017 at 01:32:49AM -0500, Eric W. Biederman wrote:
> If a network device does not implement rntl_link_ops it is returned to
> the initial network namespace. Anything else will loose physical
> devices.
Thanks a lot for your statement. This is a big relief, my line of
thinking thus is confirmed: We shall not loose physical devices.
> Only for pure software based devices do we delete them. Perhaps your
> sub interface implements rtnl_link_ops? Either that or something is
> still holding a reference to your network namespace, which would prevent
> the network device from being returned.
My question is how to debug this further? Monitoring
/proc/*/ns/net* showed that the ID of the namespace is gone after
terminating my processes in the namespace. Short of adding printk() or
playing with kprobes: to the related kernel code, how can I track the
reference count or get an idea who might hold references?
Regards,
Harald
--
- Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
next prev parent reply other threads:[~2017-06-01 7:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 22:07 loosing netdevices with namespaces and unshare? Harald Welte
2017-05-30 23:18 ` Cong Wang
2017-05-31 12:27 ` Harald Welte
2017-05-31 17:44 ` Cong Wang
2017-05-31 18:11 ` Harald Welte
2017-05-31 22:40 ` Cong Wang
2017-05-31 23:13 ` Harald Welte
2017-06-01 6:32 ` Eric W. Biederman
2017-06-01 7:00 ` Harald Welte [this message]
2017-06-01 7:48 ` Eric W. Biederman
2017-06-02 23:25 ` Cong Wang
2017-06-03 10:53 ` Eric W. Biederman
2017-05-30 23:41 ` David Ahern
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=20170601070031.mdycexartsu33fyd@nataraja \
--to=laforge@gnumonks.org \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.