From: Jiri Slaby <jirislaby@gmail.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: locking issue (hardirq+softirq+user)
Date: Wed, 20 Dec 2006 14:35:24 +0100 [thread overview]
Message-ID: <45893C1C.60305@gmail.com> (raw)
Hi!
an user still gets NMI watchdog warning, that the machine deadlocked.
The code is something like this:
DEFINE_SPINLOCK(lock);
isr() /* i.e. hardirq context */
{
spin_lock(&lock);
...
spin_unlock(&lock);
}
timer() /* i.e. softirq context */
{
unsigned int f;
spin_lock_irqsave(&lock, f) /* stack shows, that it locks here */
...
spin_unlock_irqrestore(&lock, f)
...
mod_timer();
}
tty_open_or_whatever() /* i.e. user context */
{
unsigned int f;
spin_lock_irqsave(&lock, f)
...
spin_unlock_irqrestore(&lock, f)
}
init()
{
mod_timer();
request_irq();
register_that_open_with_something();
}
What's the correct locking approach in this situation? Is that correct (I tried
to go through Rusty Russel's guide to locking, but I didn't get it in this
case)? There were many spin_lock recursions in the driver
(drivers/char/isicom.c), which I removed, but it still deadlocks on SMP.
thanks,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
next reply other threads:[~2006-12-20 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 13:35 Jiri Slaby [this message]
2006-12-20 13:50 ` locking issue (hardirq+softirq+user) Arjan van de Ven
2006-12-20 13:59 ` Jiri Slaby
2006-12-20 22:28 ` linux-os (Dick Johnson)
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=45893C1C.60305@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@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