netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	enrico.scholz@informatik.tu-chemnitz.de
Subject: Re: [Bugme-new] [Bug 12743] New: Oops when renaming interfaces added to a bridge
Date: Fri, 20 Feb 2009 09:45:19 -0800	[thread overview]
Message-ID: <20090220094519.d8ad0496.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-12743-10286@http.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Fri, 20 Feb 2009 04:01:27 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=12743
> 
>            Summary: Oops when renaming interfaces added to a bridge
>            Product: Networking
>            Version: 2.5
>      KernelVersion: 2.6.27.18
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>         AssignedTo: acme@ghostprotocols.net
>         ReportedBy: enrico.scholz@informatik.tu-chemnitz.de
> 
> 
> Distribution: custom 
> Hardware Environment: ARM PXA320
> [reproduced on Fedora 10 with 2.6.27.15-170.2.24.fc10.x86_64 too]
> 
> Problem Description:
> 
> When renaming an interface which was added to a bridge, its name won't
> be changed in the bridge setup.  Adding another interface which was
> created later with the original name,  kernel oopses
> 
> A 'find /sys -name dummy*' between step 4 and 5 reports
> 
> /sys/devices/virtual/net/br0/brif/dummy0
> /sys/devices/virtual/net/dummy100
> /sys/bus/i2c/drivers/dummy
> /sys/class/net/dummy100
> 
> 
> Although it is only a WARNING, system goes havoc because whole
> networking stack seems to be unusable then.
> 
> 
> 
> Steps to reproduce:
> 
> 1. brctl addbr br0
> 
> 2. modprobe -o d0 dummy
> 3. brctl addif br0 dummy0
> 
> 4. ifrename -i dummy0 -n dummy100
> 
> 5. modprobe -o d1 dummy
> 6. brctl addif br0 dummy0
> 
> 
> device dummy0 entered promiscuous mode
> ------------[ cut here ]------------
> WARNING: at fs/sysfs/dir.c:463 sysfs_add_one+0x34/0x48()
> ....
> 
> 


       reply	other threads:[~2009-02-20 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12743-10286@http.bugzilla.kernel.org/>
2009-02-20 17:45 ` Andrew Morton [this message]
2009-02-21 13:06   ` [Bugme-new] [Bug 12743] New: Oops when renaming interfaces added to a bridge Herbert Xu

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=20090220094519.d8ad0496.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=enrico.scholz@informatik.tu-chemnitz.de \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).