From: Ivo van Doorn <ivdoorn@gmail.com>
To: rt2400-devel@lists.sourceforge.net
Cc: Luca Tettamanti <kronos.it@gmail.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [Rt2400-devel] [BUG] rt2x00: inconsistent lock state
Date: Sun, 5 Aug 2007 22:46:43 +0200 [thread overview]
Message-ID: <200708052246.43203.IvDoorn@gmail.com> (raw)
In-Reply-To: <20070805194554.GA17141@dreamland.darkstar.lan>
Hi,
> If I'm reading the state bits and the message correcly dev_base_lock was
> aquired for write with IRQ enabled (via register_netdevice), but lockep also
> saw it aquired for read *in* IRQ (hardirq) context (rt2x00 code path, via
> rt2x00lib_beacondone -> ieee80211_beacon_get); this means that a deadlock can
> occur if we take an interrupt while the lock is already held.
> So either the lock must be IRQ-safe (_irq() / _irq_save()) or rt2x00 must not
> take it in interrupt context.
This has already been fixed in rt2x00.git
I am still working on resolving some other issues,
but the rt2x00 2.0.7 release will contain the fix for this.
Ivo
prev parent reply other threads:[~2007-08-05 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 19:45 [BUG] rt2x00: inconsistent lock state Luca Tettamanti
2007-08-05 19:45 ` Luca Tettamanti
2007-08-05 20:46 ` Ivo van Doorn [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=200708052246.43203.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=kronos.it@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.