All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Threaded interrupt handlers broken?
Date: Sun, 16 Aug 2009 12:14:36 +0200	[thread overview]
Message-ID: <200908161214.37008.mb@bu3sch.de> (raw)
In-Reply-To: <200908161153.14081.mb@bu3sch.de>

On Sunday 16 August 2009 11:53:13 Michael Buesch wrote:
> Hi,
> 
> I was trying to use threaded interrupt handlers, but the code always crashes
> within irq_thread() with a "BUG: spinlock bad magic 00000000".
> The spinlock that's not properly initialized is from the wait_for_threads waitqueue.
> It crashes on line 526 (see below).
> The initialization of the waitqueue struct seems to depend on whether the IRQ is
> shared or not. I don't know if that's correct, but I patched it to unconditionally
> initialize the struct. That did not help.
> 
> Any ideas?
> 
> 
> 490 static int irq_thread(void *data)
> 491 {
> 492         struct sched_param param = { .sched_priority = MAX_USER_RT_PRIO/2, };
> 493         struct irqaction *action = data;
> 494         struct irq_desc *desc = irq_to_desc(action->irq);
> 495         int wake;
> 496 
> 497         sched_setscheduler(current, SCHED_FIFO, &param);
> 498         current->irqaction = action;
> 499 
> 500         while (!irq_wait_for_interrupt(action)) {
> 501 
> 502                 irq_thread_check_affinity(desc, action);
> 503 
> 504                 atomic_inc(&desc->threads_active);
> 505 
> 506                 spin_lock_irq(&desc->lock);
> 507                 if (unlikely(desc->status & IRQ_DISABLED)) {
> 508                         /*
> 509                          * CHECKME: We might need a dedicated
> 510                          * IRQ_THREAD_PENDING flag here, which
> 511                          * retriggers the thread in check_irq_resend()
> 512                          * but AFAICT IRQ_PENDING should be fine as it
> 513                          * retriggers the interrupt itself --- tglx
> 514                          */
> 515                         desc->status |= IRQ_PENDING;
> 516                         spin_unlock_irq(&desc->lock);
> 517                 } else {
> 518                         spin_unlock_irq(&desc->lock);
> 519 
> 520                         action->thread_fn(action->irq, action->dev_id);
> 521                 }
> 522 
> 523                 wake = atomic_dec_and_test(&desc->threads_active);

Is this test logic inverted? atomic_dec_and_test() means
(threads_active - 1) == 0
Shouldn't it be like this?
(threads_active - 1) != 0

> 524 
> 525                 if (wake && waitqueue_active(&desc->wait_for_threads))
> 526                         wake_up(&desc->wait_for_threads);                <<<<<<<<<<<<<<<<<<<<<<<<
> 527         }
> 528 
> 529         /*
> 530          * Clear irqaction. Otherwise exit_irq_thread() would make
> 531          * fuzz about an active irq thread going into nirvana.
> 532          */
> 533         current->irqaction = NULL;
> 534         return 0;
> 535 }
> 



-- 
Greetings, Michael.

  reply	other threads:[~2009-08-16 10:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-16  9:53 Threaded interrupt handlers broken? Michael Buesch
2009-08-16 10:14 ` Michael Buesch [this message]
2009-08-16 12:45   ` Michael Buesch
2009-08-16 13:22     ` Thomas Gleixner
2009-08-16 13:46       ` Michael Buesch
2009-08-16 14:25         ` Thomas Gleixner
2009-08-16 17:51           ` Michael Buesch
2009-08-16 20:05             ` Thomas Gleixner
2009-08-16 21:01               ` Michael Buesch
2009-08-16 21:28                 ` Thomas Gleixner
2009-08-17 10:23                   ` Michael Buesch
2009-08-17 10:56                     ` Thomas Gleixner
2009-08-17 11:03                       ` Thomas Gleixner
2009-08-17 11:12                         ` Thomas Gleixner
2009-08-17 11:37                           ` Michael Buesch
2009-08-17 12:14                             ` Thomas Gleixner
2009-08-17 12:30                               ` Michael Buesch
2009-09-04 18:55                                 ` Michael Buesch
2009-09-04 19:05                                   ` Michael Buesch
2009-09-04 19:35                                     ` Michael Buesch
2009-09-04 19:37                                     ` Sebastian Andrzej Siewior
2009-08-16 13:19 ` Thomas Gleixner

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=200908161214.37008.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.