From: Ignacy Gawedzki <ignacy.gawedzki@green-communications.fr>
To: netdev@vger.kernel.org
Subject: VLAN creation may lead to deadlock.
Date: Fri, 13 Feb 2015 13:02:17 +0100 [thread overview]
Message-ID: <20150213120217.GA6198@zenon.in.qult.net> (raw)
Hi,
I stumbled upon the following annoying situation: supposing eth0 is some
interface that is currently DOWN, the following command
ip link add link eth0 name eth0.1 up type vlan id 1
never returns and the kernel printks the following lines every few seconds
unregister_netdevice: waiting for eth0.1 to become free. Usage count = 2
I understand that the kernel should prevent me from creating a VLAN interface
that's initially up when loose-binding is off and the master interface is down
(and indeed there is absolutely no problem when loose-binding is on), but the
unregistering of the currently-being-registered device should not block like
that. It appears there are too few dev_puts compared to dev_holds in there.
Regards,
Ignacy
--
Ignacy Gawędzki
R&D Engineer
Green Communications
next reply other threads:[~2015-02-13 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 12:02 Ignacy Gawedzki [this message]
2015-02-13 19:54 ` VLAN creation may lead to deadlock Cong Wang
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=20150213120217.GA6198@zenon.in.qult.net \
--to=ignacy.gawedzki@green-communications.fr \
--cc=netdev@vger.kernel.org \
/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