[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070614060738.GA10095@localdomain>
Date: Thu, 14 Jun 2007 09:07:38 +0300
From: Dan Aloni <da-x@...atomic.org>
To: Stephen Hemminger <shemminger@...ux-foundation.org>
Cc: Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Fix race condition about network device name allocation
On Wed, Jun 13, 2007 at 09:36:31AM -0700, Stephen Hemminger wrote:
> On Wed, 13 Jun 2007 12:45:21 +0300
> Dan Aloni <da-x@...atomic.org> wrote:
>
> > On Mon, May 14, 2007 at 08:58:40AM -0700, Stephen Hemminger wrote:
> > > Kenji Kaneshige found this race between device removal and
> > > registration. On unregister it is possible for the old device to
> > > exist, because sysfs file is still open. A new device with 'eth%d'
> > > will select the same name, but sysfs kobject register will fial.
> > >
> > > The following changes the shutdown order slightly. It hold a removes the sysfs
> > > entries earlier (on unregister_netdevice), but holds a kobject reference.
> > > Then when todo runs the actual last put free happens.
> > >
> > > Signed-off-by: Stephen Hemminger <shemminger@...ux-foundation.org>
> >
> > That patch breaks the bonding driver. After reverting it I avoid this crash:
> >
>[..]
> >
>
> I assume this happens when bonded slave device is removed?
Yes, it's just a simple removal via sysfs.
> Which kernel version?
2.6.21.5
--
Dan Aloni
XIV LTD, http://www.xivstorage.com
da-x (at) monatomic.org, dan (at) xiv.co.il
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists