mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "\"陈华才\"" <chenhc@lemote.com>
To: "Thomas Gleixner" <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: Avoid NULL OOPS in irq handling
Date: Wed, 30 Oct 2013 17:24:17 +0800	[thread overview]
Message-ID: <fd7ba5f27786bbd812c19dcd6c589eb2.squirrel@mail.lemote.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1310291402490.8257@ionos.tec.linutronix.de>

I use a Loongson-3(MIPS-series CPU) machine, there is a serial port
integrated in the CPU (but it iss buggy), and it use handle_percpu_irq()
as the irq handler. Maybe I should move the checking into
handle_percpu_irq()?

Huacai

> On Sat, 28 Sep 2013, Huacai Chen wrote:
>
>> Some devices (e.g. serial port) setup irq handler at dev open and free
>> it at dev close. So, sometimes there is no irqaction for a specific
>> irq. But some buggy devices may send irqs at any time. This patch avoid
>> the NULL OOPS when irqaction isn't registered.
>
> All callers except the real per cpu interrupts are checking whether
> there is a valid action before calling. And serial ports are not
> routed to real per cpu interrupts. Can you provide more detailed
> information about the problem you are trying to solve please?
>
> Thanks,
>
> 	tglx
>
>> Signed-off-by: Huacai Chen <chenhc@lemote.com>
>> ---
>>  kernel/irq/handle.c |    4 ++++
>>  1 files changed, 4 insertions(+), 0 deletions(-)
>>
>> diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c
>> index 131ca17..1c78e69 100644
>> --- a/kernel/irq/handle.c
>> +++ b/kernel/irq/handle.c
>> @@ -135,6 +135,9 @@ handle_irq_event_percpu(struct irq_desc *desc,
>> struct irqaction *action)
>>  	irqreturn_t retval = IRQ_NONE;
>>  	unsigned int flags = 0, irq = desc->irq_data.irq;
>>
>> +	if (!action)
>> +		goto out;
>> +
>>  	do {
>>  		irqreturn_t res;
>>
>> @@ -174,6 +177,7 @@ handle_irq_event_percpu(struct irq_desc *desc,
>> struct irqaction *action)
>>
>>  	add_interrupt_randomness(irq, flags);
>>
>> +out:
>>  	if (!noirqdebug)
>>  		note_interrupt(irq, desc, retval);
>>  	return retval;
>> --
>> 1.7.7.3
>>
>>
>



  reply	other threads:[~2013-10-30  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28  2:11 Huacai Chen
2013-10-29 13:07 ` Thomas Gleixner
2013-10-30  9:24   ` "陈华才" [this message]
2013-10-30 10:06     ` Thomas Gleixner
2013-10-30 13:02       ` "陈华才"

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=fd7ba5f27786bbd812c19dcd6c589eb2.squirrel@mail.lemote.com \
    --to=chenhc@lemote.com \
    --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 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®