From: Grant Likely <grant.likely@linaro.org>
To: Chen Gang <gang.chen@asianux.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel/irq/irqdomain.c: before use 'irq_data', need check it whether valid.
Date: Wed, 05 Jun 2013 23:41:47 +0100 [thread overview]
Message-ID: <20130605224147.584263E10E4@localhost> (raw)
In-Reply-To: <519219D5.6010907@asianux.com>
On Tue, 14 May 2013 19:02:45 +0800, Chen Gang <gang.chen@asianux.com> wrote:
>
> Since irq_data may be NULL, if so, we WARN_ON(), and continue, 'hwirq'
> which related with 'irq_data' has to initialize later, or it will cause
> issue.
>
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
Applied, thanks.
g.
> ---
> kernel/irq/irqdomain.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
> index af804b5..61abbfa 100644
> --- a/kernel/irq/irqdomain.c
> +++ b/kernel/irq/irqdomain.c
> @@ -400,11 +400,12 @@ static void irq_domain_disassociate_many(struct irq_domain *domain,
> while (count--) {
> int irq = irq_base + count;
> struct irq_data *irq_data = irq_get_irq_data(irq);
> - irq_hw_number_t hwirq = irq_data->hwirq;
> + irq_hw_number_t hwirq;
>
> if (WARN_ON(!irq_data || irq_data->domain != domain))
> continue;
>
> + hwirq = irq_data->hwirq;
> irq_set_status_flags(irq, IRQ_NOREQUEST);
>
> /* remove chip and handler */
> --
> 1.7.7.6
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.
next prev parent reply other threads:[~2013-06-05 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 11:02 [PATCH] kernel/irq/irqdomain.c: before use 'irq_data', need check it whether valid Chen Gang
2013-06-05 22:41 ` Grant Likely [this message]
2013-06-06 8:39 ` Chen Gang
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=20130605224147.584263E10E4@localhost \
--to=grant.likely@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=gang.chen@asianux.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