From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Тхай Кирилл" <tkhai@yandex.ru>
Cc: Herton Ronaldo Krzesinski <herton@mandriva.com.br>,
Hin-Tak Leung <htl10@users.sourceforge.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH]rtl8187:fixed kernel panic on module unload
Date: Mon, 30 Nov 2009 11:25:19 -0600 [thread overview]
Message-ID: <4B13FFFF.4050801@lwfinger.net> (raw)
In-Reply-To: <63741259601663@webmail119.yandex.ru>
On 11/30/2009 11:21 AM, Тхай Кирилл wrote:
> From: Tkhai Kirill <tkhai@yandex.ru>
>
> rtl8187: fix kernel panic on module unload (BUG in rtl8187_leds_exit())
> Signed-off-by: Tkhai Kirill <tkhai@yandex.ru>
> ---
> The function rtl8187_leds_exit must not return until all LED's works
> in device workqueue have completed or cancelled. Otherwise, we can get
> the folowing:
> wq = create_singlethread_workqueue("phyX");
>
> INIT_DELAYED_WORK(&work, work_func);
> queue_delayed_work(wq, &work, HZ/20);
>
> destroy_workqueue(wq);
>
> =======>kernel panic
> On current vanila driver code (when running on SMP systems), panic happens
> almost every time. My patch for version 2.6.31 (and 2.6.31.6 too):
>
> --- a/drivers/net/wireless/rtl818x/rtl8187_leds.c.orig 2009-11-26 22:26:45.000000000 +0300
> +++ b/drivers/net/wireless/rtl818x/rtl8187_leds.c 2009-11-28 18:22:26.659785533 +0300
> @@ -36,9 +36,6 @@ static void led_turn_on(struct work_stru
> if (priv->mode == NL80211_IFTYPE_UNSPECIFIED)
> return ;
>
> - /* Skip if the LED is not registered. */
> - if (!led->dev)
> - return;
> mutex_lock(&priv->conf_mutex);
> switch (led->ledpin) {
> case LED_PIN_GPIO0:
> @@ -74,9 +71,6 @@ static void led_turn_off(struct work_str
> if (priv->mode == NL80211_IFTYPE_UNSPECIFIED)
> return ;
>
> - /* Skip if the LED is not registered. */
> - if (!led->dev)
> - return;
> mutex_lock(&priv->conf_mutex);
> switch (led->ledpin) {
> case LED_PIN_GPIO0:
> @@ -208,12 +202,12 @@ void rtl8187_leds_exit(struct ieee80211_
> {
> struct rtl8187_priv *priv = dev->priv;
>
> - /* turn the LED off before exiting */
> - queue_delayed_work(dev->workqueue, &priv->led_off, 0);
> - cancel_delayed_work_sync(&priv->led_off);
> - cancel_delayed_work_sync(&priv->led_on);
> rtl8187_unregister_led(&priv->led_rx);
> rtl8187_unregister_led(&priv->led_tx);
> + cancel_delayed_work_sync(&priv->led_on);
> + /* turn the LED off before exiting */
> + queue_delayed_work(dev->workqueue, &priv->led_off, 0);
> + flush_workqueue(dev->workqueue);
> }
> #endif /* def CONFIG_RTL8187_LED */
Have you applied the fix in mainline commit
37b12dd2b07b4d7dc222a5f7f88b25cec532b2aa? It should have fixed this problem.
Larry
next prev parent reply other threads:[~2009-11-30 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 17:21 [PATCH]rtl8187:fixed kernel panic on module unload Тхай Кирилл
2009-11-30 17:25 ` Larry Finger [this message]
2009-12-01 8:31 ` Hin-Tak Leung
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=4B13FFFF.4050801@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=herton@mandriva.com.br \
--cc=htl10@users.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tkhai@yandex.ru \
/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).