Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Einar EL Lueck <ELELUECK@de.ibm.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	Frank Blaschka <Frank.Blaschka@de.ibm.com>
Subject: Re: Fw: oops during unregister_netdevice interface enslaved to bond - regression
Date: Tue, 10 May 2011 15:03:33 +0200	[thread overview]
Message-ID: <1305032613.2614.26.camel@edumazet-laptop> (raw)
In-Reply-To: <1305017959.2614.13.camel@edumazet-laptop>

Le mardi 10 mai 2011 à 10:59 +0200, Eric Dumazet a écrit :
> Le mardi 10 mai 2011 à 10:54 +0200, Eric Dumazet a écrit :
> 
> > I am currently working on this stuff [adding even more batching and
> > probably bugs as well ], so instead of revert I'll try to find a way to
> > fix this.
> > 
> > If you already have a script to reproduce the bug on virtual devices on
> > x86 (not on s390 machines I dont have ;) ), I'll appreciate having a
> > copy of it.
> > 
> > Thanks for the reminder.
> 
> BTW make sure latest linux-2.6 still exhibits the problem, we fixed some
> things after original Octavian commit
> 
> List of commits :
> 
> commit ceaaec98ad99859ac90ac6863ad0a6cd075d8e0e
> net: deinit automatic LIST_HEAD
> 
> commit f87e6f47933e3ebeced9bb12615e830a72cedce4 
> net: dont leave active on stack LIST_HEAD 
> 
> 

OK I trigger the bug on linux-2.6 with :

modprobe bonding
ip link add testa type veth peer name testb
ifconfig bond0 up
ifenslave bond0 testa
ip link del testa

I'll cook a patch, stay tuned :)



  reply	other threads:[~2011-05-10 13:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  8:17 Fw: oops during unregister_netdevice interface enslaved to bond - regression Einar EL Lueck
2011-05-10  8:54 ` Eric Dumazet
2011-05-10  8:59   ` Eric Dumazet
2011-05-10 13:03     ` Eric Dumazet [this message]
2011-05-10 13:14   ` Frank Blaschka
2011-05-10 13:36     ` Eric Dumazet
2011-05-10 14:20       ` Frank Blaschka
2011-05-10 19:26       ` David Miller
2011-05-10 19:25 ` David Miller

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=1305032613.2614.26.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=ELELUECK@de.ibm.com \
    --cc=Frank.Blaschka@de.ibm.com \
    --cc=davem@davemloft.net \
    --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