All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex,Shi" <alex.shi@intel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	davem@davemloft.net
Cc: "Chen, Tim C" <tim.c.chen@intel.com>,
	"Li, Shaohua" <shaohua.li@intel.com>
Subject: Re: 2.6.37-rc2 after KVM shutdown - unregister_netdevice: waiting for vmtst01eth0 to become free. Usage count = 1
Date: Tue, 23 Nov 2010 08:27:08 +0800	[thread overview]
Message-ID: <1290472028.16282.71.camel@debian> (raw)
In-Reply-To: <AANLkTi=kx3uzrf29K7U8BFt2oTA_Dtw=4r2LdWPFUKv7@mail.gmail.com>


Seems the problem fixing is still out of 37-rc3 kernel. It block our
network performance testing. I am glad to see the fixing patch in
upstream. 


> 
> On Thu, Nov 18, 2010 at 5:16 PM, Eric Dumazet <eric.dumazet@gmail.com>
> wrote:
>         Le jeudi 18 novembre 2010 à 07:28 +0100, Nikola Ciprich a
>         écrit :
>         > > Yep, this is a known problem, thanks !
>         > >
>         > > fix is there :
>         > >
>         > > http://patchwork.ozlabs.org/patch/71354/
>         > Thanks Eric, this indeed fixes the problem..
>         > I noticed the fix didn't make it to 2.6.37-rc2-git3 though,
>         > maybe it just got omited?
>         > anyways, thanks for help!
>         > n.
>         
>         
>         Its in David Miller net-2.6 tree (all pending network patches
>         for
>         current linux-2.6 version), so it'll be included next time
>         David push
>         its tree to Linus, dont worry ;)
>         
>         

> 



      parent reply	other threads:[~2010-11-23  0:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16  8:41 2.6.37-rc2 after KVM shutdown - unregister_netdevice: waiting for vmtst01eth0 to become free. Usage count = 1 Nikola Ciprich
2010-11-16  9:46 ` Eric Dumazet
2010-11-18  6:28   ` Nikola Ciprich
2010-11-18  9:16     ` Eric Dumazet
     [not found]       ` <AANLkTi=kx3uzrf29K7U8BFt2oTA_Dtw=4r2LdWPFUKv7@mail.gmail.com>
2010-11-23  0:27         ` Alex,Shi [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=1290472028.16282.71.camel@debian \
    --to=alex.shi@intel.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=tim.c.chen@intel.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.