netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
	netdev <netdev@vger.kernel.org>
Subject: Re: Cannot delete a bridge using 'ip' netlink interface
Date: Sat, 08 Oct 2011 01:22:40 +0400	[thread overview]
Message-ID: <4E8F6DA0.80006@msgid.tls.msk.ru> (raw)
In-Reply-To: <4E8F62F7.4080408@msgid.tls.msk.ru>

On 08.10.2011 00:37, Michael Tokarev wrote:
> On 06.10.2011 21:18, Sridhar Samudrala wrote:
>> On a linux 3.1.0-rc9 system using the latest iproute2, i tried
>> creating a bridge and deleting it with an attached interface. 
>>
>> Here is the sequence of steps i tried
>> ip link add br0 type bridge
>> ip link set dev eth1 master br0
>> ip link set br0 up
>> ip link del br0
>>
>> The last command hangs with the following kernel messages
>> kernel:unregister_netdevice: waiting for br0 to become free. Usage count = 1
> 
> Note that the same thing happens when one tries to rmmod bridge
> while it is in use.  I'm trying your patch to see if that helps... ;)

..And with the patch sent in this thread, bridge module can be
removed and inserted again with proper cleanup.

So you can add my

Tested-Off-By: Michael Tokarev <mjt@tls.msk.ru>

too, if necessary :)

Thanks,

/mjt

      reply	other threads:[~2011-10-07 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 17:18 Cannot delete a bridge using 'ip' netlink interface Sridhar Samudrala
2011-10-06 21:19 ` [PATCH] bridge: fix hang on removal of bridge via netlink Stephen Hemminger
2011-10-06 23:02   ` Sridhar Samudrala
2011-10-19  3:24     ` David Miller
2011-10-07 20:37 ` Cannot delete a bridge using 'ip' netlink interface Michael Tokarev
2011-10-07 21:22   ` Michael Tokarev [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=4E8F6DA0.80006@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=sri@us.ibm.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).