netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Chris Stromsoe <cbs@cts.ucla.edu>
Cc: netdev@vger.kernel.org
Subject: Re: skge- "soft lockup on CPU#0" with mtu=9000 (2.6.20.1 + web100 patch)
Date: Thu, 8 Mar 2007 11:34:27 -0800	[thread overview]
Message-ID: <20070308113427.6344a7f6@freekitty> (raw)
In-Reply-To: <Pine.LNX.4.64.0703081101390.21717@potato.cts.ucla.edu>


[SKGE]: Fix deadlock in skge_tx_timeout

dev_watchdog() already holds the device lock, don't take it again in
skge_tx_clean().

Signed-off-by: Patrick McHardy <kaber@trash.net>

---
commit 0b1cfafa6f6b8a168d5811d1f65cf540942c52b1
tree 4d3f252d6618adfe812e9da95cd496bb798e7c7b
parent 1ca949299260aa49eeba34ff912e2321c8b1f647
author Patrick McHardy <kaber@trash.net> Sat, 24 Feb 2007 20:05:39 +0100
committer Patrick McHardy <kaber@trash.net> Sat, 24 Feb 2007 20:05:39 +0100

 drivers/net/skge.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/skge.c b/drivers/net/skge.c
index e482e7f..4a948c2 100644
--- a/drivers/net/skge.c
+++ b/drivers/net/skge.c
@@ -2575,7 +2575,9 @@ static int skge_down(struct net_device *
 	skge_led(skge, LED_MODE_OFF);
 
 	netif_poll_disable(dev);
+	netif_tx_lock_bh(dev);
 	skge_tx_clean(dev);
+	netif_tx_unlock_bh(dev);
 	skge_rx_clean(skge);
 
 	kfree(skge->rx_ring.start);
@@ -2720,7 +2722,6 @@ static void skge_tx_clean(struct net_dev
 	struct skge_port *skge = netdev_priv(dev);
 	struct skge_element *e;
 
-	netif_tx_lock_bh(dev);
 	for (e = skge->tx_ring.to_clean; e != skge->tx_ring.to_use; e = e->next) {
 		struct skge_tx_desc *td = e->desc;
 		skge_tx_free(skge, e, td->control);
@@ -2729,7 +2730,6 @@ static void skge_tx_clean(struct net_dev
 
 	skge->tx_ring.to_clean = e;
 	netif_wake_queue(dev);
-	netif_tx_unlock_bh(dev);
 }
 
 static void skge_tx_timeout(struct net_device *dev)


--------------010402080104080400040104--
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-03-08 19:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 19:20 skge- "soft lockup on CPU#0" with mtu=9000 (2.6.20.1 + web100 patch) Chris Stromsoe
2007-03-08 19:34 ` Stephen Hemminger [this message]
2007-03-08 21:31   ` Chris Stromsoe
2007-03-08 21:48     ` Stephen Hemminger
2007-03-08 22:23       ` Chris Stromsoe
2007-03-08 23:04         ` Jay Vosburgh
2007-03-08 23:13           ` Chris Stromsoe
2007-03-12 22:09             ` Chris Stromsoe
2007-03-12 22:16               ` [PATCH] skge: set mac address bonding fix Stephen Hemminger
2007-03-12 22:39                 ` Chris Stromsoe
2007-03-12 23:18                   ` Stephen Hemminger
2007-03-13  0:37                     ` Chris Stromsoe
2007-03-15 14:35                 ` Jeff Garzik
2007-05-08 22:28               ` skge- "soft lockup on CPU#0" with mtu=9000 (2.6.20.1 + web100 patch) Chris Stromsoe
2007-05-09  0:06                 ` Chris Stromsoe
2007-03-08 21:37 ` Jay Vosburgh

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=20070308113427.6344a7f6@freekitty \
    --to=shemminger@linux-foundation.org \
    --cc=cbs@cts.ucla.edu \
    --cc=netdev@vger.kernel.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).