From: David Miller <davem@davemloft.net>
To: mikem@ring3k.org
Cc: shemminger@vyatta.com, netdev@vger.kernel.org, flyboy@gmail.com,
dhazelton@enter.net, mbreuer@majjas.com,
"netdev@vger.kernel.org"@ogre.sisk.pl
Subject: Re: [PATCH] sky2: Lock transmit queue while disabling device
Date: Wed, 06 Jan 2010 20:27:01 -0800 (PST) [thread overview]
Message-ID: <20100106.202701.161194890.davem@davemloft.net> (raw)
In-Reply-To: <4B3C8323.1080301@ring3k.org>
From: Mike McCormack <mikem@ring3k.org>
Date: Thu, 31 Dec 2009 19:55:31 +0900
>
> netif_device_detach() does not take the tx_lock, so it's
> possible that a call to sky2_xmit_frame is still in
> progress after netif_device_detach() is complete.
>
> Take netif_tx_lock() to make sure all transmits have
> stopped while we're disabling the devices and that
> no other CPU is still transmitting a frame after
> we've disabling the device.
>
> Proposed fix for "sky2 panic under load" reported by Berck E. Nash.
>
> Signed-off-by: Mike McCormack <mikem@ring3k.org>
Applied to net-next-2.6
Stephen has asked for some further refinements, once that is
all sorted we can think about backporting this to net-2.6
and -stable if necessary.
Thanks.
next prev parent reply other threads:[~2010-01-07 4:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 10:55 [PATCH] sky2: Lock transmit queue while disabling device Mike McCormack
2009-12-31 15:58 ` Michael Breuer
2009-12-31 16:15 ` Daniel Hazelton
2009-12-31 16:33 ` Berck Nash
2009-12-31 18:51 ` Jarek Poplawski
2009-12-31 23:51 ` Mike McCormack
2010-01-01 3:06 ` Berck E. Nash
2010-01-01 6:42 ` Stephen Hemminger
2010-01-01 18:31 ` Jarek Poplawski
2010-01-04 2:44 ` Berck E. Nash
2010-01-04 13:49 ` [PATCH] sky2: Fix oops in sky2_xmit_frame() after TX timeout Jarek Poplawski
2010-01-04 18:26 ` Stephen Hemminger
2010-01-04 18:48 ` [PATCH v2] " Jarek Poplawski
2010-01-07 4:27 ` David Miller [this message]
2010-01-07 6:35 ` [PATCH] sky2: Lock transmit queue while disabling device Jarek Poplawski
2010-01-07 8:01 ` David Miller
2010-01-07 8:15 ` Jarek Poplawski
2010-01-07 8:19 ` David Miller
2010-01-07 13:48 ` Stephen Hemminger
2010-01-07 18:08 ` Stephen Hemminger
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=20100106.202701.161194890.davem@davemloft.net \
--to=davem@davemloft.net \
--cc="netdev@vger.kernel.org"@ogre.sisk.pl \
--cc=dhazelton@enter.net \
--cc=flyboy@gmail.com \
--cc=mbreuer@majjas.com \
--cc=mikem@ring3k.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).