From: Thomas Gleixner <tglx@linutronix.de>
To: Yong Zhang <yong.zhang@windriver.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] IRQ: Fix oneshot irq race between irq_finalize_oneshot and handle_level_irq
Date: Wed, 10 Mar 2010 08:56:22 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1003100848380.22855@localhost.localdomain> (raw)
In-Reply-To: <20100310032102.GA2090@windriver.com>
On Wed, 10 Mar 2010, Yong Zhang wrote:
> On Wed, Mar 10, 2010 at 12:22:12AM +0100, Thomas Gleixner wrote:
> > B1;2005;0cOn Tue, 9 Mar 2010, Lars-Peter Clausen wrote:
> > >
> > > - desc->status |= IRQ_INPROGRESS;
> > > + desc->status |= IRQ_INPROGRESS | IRQ_ONESHOT_INPROGRESS;
> > > raw_spin_unlock(&desc->lock);
> >
> > That keeps the IRQ_ONESHOT_INPROGRESS dangling for non ONESHOT
> > interrupts. Not a big deal, but not pretty either.
> >
> > The race between the thread and the irq handler exists indeed on SMP,
> > but I think there are more fundamental issues about the state which
> > need to be addressed.
> >
> > The first thing is that we do not mark the status MASKED when we
> > actually mask the interrupt in mask_ack_irq().
> >
> > That conditional MASKED after running the primary handler is really
> > horrible - I already ranted in private at the moron who committed that
> > crime :)
> >
> > So the following patch fixes that and the SMP race scenario:
>
> Hi Thomas,
>
> How about the following patch(maybe a little ugly). I think it will
> resolve your concerns.
No it does not, but you are right that it's ugly. And it is patently
wrong as well.
> diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
> index d70394f..23b79c6 100644
> --- a/kernel/irq/chip.c
> +++ b/kernel/irq/chip.c
> @@ -461,9 +461,24 @@ handle_level_irq(unsigned int irq, struct irq_desc *desc)
> raw_spin_lock(&desc->lock);
> mask_ack_irq(desc, irq);
>
> - if (unlikely(desc->status & IRQ_INPROGRESS))
> - goto out_unlock;
> + /*
> + * if we are in oneshot mode and the irq thread is running on
> + * another cpu, just return because the irq thread will unmask
> + * the irq
> + */
> + if (unlikely(desc->status & IRQ_ONESHOT)) {
> + if (unlikely(desc->status & (IRQ_INPROGRESS | IRQ_MASKED)
> + == IRQ_INPROGRESS | IRQ_MASKED))
> + goto out_unlock;
> + }
> + else {
> + if (unlikely(desc->status & IRQ_INPROGRESS))
> + goto out_unlock;
> + }
In case of IRQ_SHOT and IRQ_INPROGRESS and the other CPU having
unmasked the interrupt already you are reentering the handler which
is a nono.
Thanks,
tglx
next prev parent reply other threads:[~2010-03-10 7:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 23:57 Lars-Peter Clausen
2010-03-09 7:58 ` Thomas Gleixner
2010-03-09 8:08 ` Yong Zhang
2010-03-09 16:59 ` Valdis.Kletnieks
2010-03-09 18:10 ` Thomas Gleixner
2010-03-09 22:48 ` Lars-Peter Clausen
2010-03-09 23:32 ` Thomas Gleixner
2010-03-09 23:22 ` Thomas Gleixner
2010-03-10 3:21 ` Yong Zhang
2010-03-10 7:56 ` Thomas Gleixner [this message]
2010-03-11 2:55 ` Yong Zhang
2010-03-11 8:41 ` Thomas Gleixner
2010-03-11 9:13 ` Yong Zhang
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=alpine.LFD.2.00.1003100848380.22855@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yong.zhang@windriver.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
all inboxes | Powered by JetHome®