public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: locking issue (hardirq+softirq+user)
Date: Wed, 20 Dec 2006 14:59:45 +0100	[thread overview]
Message-ID: <458941D1.7070301@gmail.com> (raw)
In-Reply-To: <1166622618.3365.1389.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:
> On Wed, 2006-12-20 at 14:35 +0100, Jiri Slaby wrote:
>> Hi!
>>
>> an user still gets NMI watchdog warning, that the machine deadlocked.
> 
> have you tried enabling LOCKDEP ?

No, only PROVE_LOCKING, I apply him to turn this on too.

>> isr() /* i.e. hardirq context */
>> {
>> spin_lock(&lock);
>> ...
>> spin_unlock(&lock);
>> }
> 
> this is ok if you are 100% sure that this never gets called in any other
> way

It holds. Only in request_irq isr function name occurs.

>> timer() /* i.e. softirq context */
>> {
>> unsigned int f;
>> spin_lock_irqsave(&lock, f) /* stack shows, that it locks here */
> 
> this is a bug, the flags are an "unsigned long" not "unsigned int"!
> It may do really bad stuff!

Aah, sorry, I misread the code, I saw flags, but it was port->flags;
board->flags, which is used in irq{save,restore} functions, is ulong.

thanks for the quick reply,
-- 
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

  reply	other threads:[~2006-12-20 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 13:35 locking issue (hardirq+softirq+user) Jiri Slaby
2006-12-20 13:50 ` Arjan van de Ven
2006-12-20 13:59   ` Jiri Slaby [this message]
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=458941D1.7070301@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=arjan@infradead.org \
    --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