netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: shaw@vranix.com
To: "Michael Chan" <mchan@broadcom.com>
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>,
	shawvrana@gmail.com, netdev@vger.kernel.org,
	"Auke Kok" <auke-jan.h.kok@intel.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: e1000_down and tx_timeout worker race cleaning the transmit buffers
Date: Thu, 20 Apr 2006 20:05:53 -0700	[thread overview]
Message-ID: <200604202005.53504.shaw@vranix.com> (raw)
In-Reply-To: <1145578214.3195.6.camel@rh4>

[-- Attachment #1: Type: text/plain, Size: 602 bytes --]

I've replied to this once before, but haven't seen my last two emails on the 
list, so I'm sending again with different settings.  Sorry for the noise.

On Thursday 20 April 2006 17:10, Michael Chan wrote:
> In tg3_remove_one(), we call flush_scheduled_work() in case the
> reset_task is still pending. Here, it is safe to call
> flush_scheduled_work() because we're not holding the rtnl. Again, when
> it runs, nothing bad will happen because it will see netif_running() ==
> 0.

I'll bite!  Here's a patch to add a call to flush_scheduled_work() in 
e1000_down.  It's against 2.6.16.9.

Thanks,
Shaw

[-- Attachment #2: e1000_flush_in_close.patch --]
[-- Type: text/x-diff, Size: 614 bytes --]

diff -u -uprN -X linux-2.6.16.9/Documentation/dontdiff linux-2.6.16.9/drivers/net/e1000/e1000_main.c linux-2.6.16.9-patch/drivers/net/e1000/e1000_main.c
--- linux-2.6.16.9/drivers/net/e1000/e1000_main.c	2006-04-18 23:10:14.000000000 -0700
+++ linux-2.6.16.9-patch/drivers/net/e1000/e1000_main.c	2006-04-20 19:36:55.000000000 -0700
@@ -538,6 +538,7 @@ e1000_down(struct e1000_adapter *adapter
 	del_timer_sync(&adapter->tx_fifo_stall_timer);
 	del_timer_sync(&adapter->watchdog_timer);
 	del_timer_sync(&adapter->phy_info_timer);
+	flush_scheduled_work();	
 
 #ifdef CONFIG_E1000_NAPI
 	netif_poll_disable(netdev);

      parent reply	other threads:[~2006-04-21  3:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200604201035.00100.shaw@vranix.com>
2006-04-20 23:36 ` e1000_down and tx_timeout worker race cleaning the transmit buffers Herbert Xu
2006-04-20 23:51   ` Herbert Xu
2006-04-20 22:36     ` Michael Chan
2006-04-21  1:27       ` Herbert Xu
2006-04-21  1:33         ` Herbert Xu
2006-04-21  0:10           ` Michael Chan
2006-04-21  2:37             ` Herbert Xu
2006-04-21  2:40               ` Herbert Xu
2006-04-21  1:24                 ` Michael Chan
2006-04-21 13:27                   ` Andy Gospodarek
2006-04-21 15:28                     ` Michael Chan
2006-04-21 20:01                       ` Andy Gospodarek
2006-04-21 19:00                         ` Michael Chan
2006-04-21 20:46                           ` Andy Gospodarek
2006-04-27  0:14                             ` Shaw
2006-04-27  4:55                               ` Auke Kok
2006-04-29 21:57                                 ` Shaw Vrana
2006-04-21  2:42             ` Shaw Vrana
2006-04-21  1:33               ` Michael Chan
2006-04-21  3:05             ` shaw [this message]

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=200604202005.53504.shaw@vranix.com \
    --to=shaw@vranix.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=shawvrana@gmail.com \
    /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).