[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161110172807.GH24351@calimero.vinschen.de>
Date: Thu, 10 Nov 2016 18:28:07 +0100
From: Corinna Vinschen <vinschen@...hat.com>
To: Hisashi T Fujinaka <htodd@...fifty.com>
Cc: Alexander Duyck <alexander.duyck@...il.com>,
Netdev <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Cao jin <caoj.fnst@...fujitsu.com>,
intel-wired-lan <intel-wired-lan@...ts.osuosl.org>,
Izumi, Taku/泉 拓
<izumi.taku@...fujitsu.com>
Subject: Re: [Intel-wired-lan] [PATCH] igb: use igb_adapter->io_addr instead
of e1000_hw->hw_addr
On Nov 10 05:48, Hisashi T Fujinaka wrote:
> On Thu, 10 Nov 2016, Corinna Vinschen wrote:
> > On Nov 8 11:33, Alexander Duyck wrote:
> ...
> > > The question I would have is what is reading the device when it is in
> > > this state. The watchdog and any other functions that would read the
> > > device should be disabled.
> > >
> > > One possibility could be a race between a call to igb_close and the
> > > igb_suspend function. We have seen some of those pop up recently on
> > > ixgbe and it looks like igb has the same bug. We should probably be
> > > using the rtnl_lock to guarantee that netif_device_detach and the call
> > > to __igb_close are completed before igb_close could possibly be called
> > > by the network stack.
> >
> > Do you have a pointer to the related ixgbe patch, by any chance?
> ...
> Here's the initial patch for igb I have, but it's on hold awaiting more
> changes in ixgbe regarding AER.
Thanks a lot!
Corinna
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists