linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Jiri Benc <jbenc@suse.cz>, John Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: [PATCH] mac80211: Update stop_queues kdoc
Date: Fri, 1 Jun 2007 11:29:12 +0200	[thread overview]
Message-ID: <200706011129.12432.mb@bu3sch.de> (raw)

This updates stop_queue(s) kdoc as currently there's
a undocumented dependency.

Stopping the queue from anywhere else than the ops->tx()
callback will result in a hard to debug deadlock and
system freeze (on UP).

Here's an example stacktrace that has been captured only
by special debugging patches to the PPC-decrementer to
detect this machine freeze.
http://bu3sch.de/misc/freeze1.jpg
http://bu3sch.de/misc/freeze2.jpg

Signed-off-by: Michael Buesch <mb@bu3sch.de>

Index: mac80211/include/net/mac80211.h
===================================================================
--- mac80211.orig/include/net/mac80211.h	2007-06-01 11:20:32.000000000 +0200
+++ mac80211/include/net/mac80211.h	2007-06-01 11:23:02.000000000 +0200
@@ -967,6 +967,10 @@ void ieee80211_wake_queue(struct ieee802
  * @queue: queue number (counted from zero).
  *
  * Drivers should use this function instead of netif_stop_queue.
+ *
+ * It's currently only safe to call this function from the
+ * ops->tx() callback. Calls from elsewhere will result in
+ * hard to debug deadlocks (freezes the system on UP).
  */
 void ieee80211_stop_queue(struct ieee80211_hw *hw, int queue);
 
@@ -983,6 +987,10 @@ void ieee80211_start_queues(struct ieee8
  * @hw: pointer as obtained from ieee80211_alloc_hw().
  *
  * Drivers should use this function instead of netif_stop_queue.
+ *
+ * It's currently only safe to call this function from the
+ * ops->tx() callback. Calls from elsewhere will result in
+ * hard to debug deadlocks (freezes the system on UP).
  */
 void ieee80211_stop_queues(struct ieee80211_hw *hw);
 


--

I'd still prefer someone fixes the issue. I don't understand
the code well enough to fix it.


-- 
Greetings Michael.

             reply	other threads:[~2007-06-01  9:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01  9:29 Michael Buesch [this message]
2007-06-01  9:48 ` [PATCH] mac80211: Update stop_queues kdoc Johannes Berg
2007-06-01  9:53   ` Michael Buesch
2007-06-01 11:55 ` Olivier Cornu
2007-06-01 20:42   ` Michael Buesch
2007-06-01 21:00     ` Olivier Cornu
2007-06-01 21:42       ` Michael Buesch
2007-06-01 21:53         ` Olivier Cornu
2007-06-02 13:17         ` Olivier Cornu
2007-06-02 13:37           ` Michael Buesch
2007-06-02 18:41             ` Olivier Cornu
2007-06-01 16:58 ` James Ketrenos
2007-06-01 19:04   ` Michael Wu
2007-06-01 17:32     ` James Ketrenos
2007-06-01 20:36       ` Michael Wu
2007-06-01 20:52         ` Michael Buesch
2007-06-01 20:41       ` Michael Buesch
2007-06-01 20:52       ` Olivier Cornu
2007-06-01 20:54         ` Michael Buesch

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=200706011129.12432.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=flamingice@sourmilk.net \
    --cc=jbenc@suse.cz \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).