From: Andrew Morton <akpm@linux-foundation.org>
To: "David S. Miller" <davem@davemloft.net>,
Pavel Emelyanov <xemul@openvz.org>
Cc: "bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
nigel@suspend2.net, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 9778] New: unregister_netdevice: waiting for [device] to become free
Date: Sat, 19 Jan 2008 16:58:02 -0800 [thread overview]
Message-ID: <20080119165802.2846a28e.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9778-10286@http.bugzilla.kernel.org/>
On Sat, 19 Jan 2008 12:20:28 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9778
>
> Summary: unregister_netdevice: waiting for [device] to become
> free
> Product: Networking
> Version: 2.5
> KernelVersion: 2.6.24-rc8
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: blocking
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: nigel@suspend2.net
>
>
> Latest working kernel version: 2.6.24-rc7
> Earliest failing kernel version: 2.6.24-rc8
> Distribution: Ubuntu Gutsy
> Hardware Environment: AMD64, Atheros 5212 chipset
> Software Environment: Fairly recent madwifi svn.
> Problem Description: Patch "[PATCH][NEIGH] Fix race between neigh_parms_release
> and neightbl_fill_parms" (9cd40029423701c376391da59d2c6469672b4bed) causes the
> error described in the subject line to occur when seeking to unload a device.
> Also seen by some of my TuxOnIce users with e1000 and ppp42.
>
> Steps to reproduce: Run a kernel with the above patch, bring up a (nonloopback)
> interface, seek to take it down.
>
ouch.
next parent reply other threads:[~2008-01-20 0:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9778-10286@http.bugzilla.kernel.org/>
2008-01-20 0:58 ` Andrew Morton [this message]
2008-01-20 10:30 ` [Bugme-new] [Bug 9778] New: unregister_netdevice: waiting for [device] to become free David Miller
2008-01-21 12:14 ` Evgeniy Polyakov
2008-01-21 12:36 ` David Miller
2008-01-21 14:36 ` Evgeniy Polyakov
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=20080119165802.2846a28e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nigel@suspend2.net \
--cc=xemul@openvz.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).