From: Lee Jones <lee.jones@linaro.org>
To: linux-kernel@vger.kernel.org, tglx@linutronix.de,
sameo@linux.intel.com, mingo@kernel.org, Julia.Lawall@lip6.fr,
hpa@zytor.com, rmk+kernel@arm.linux.org.uk
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:irq/urgent] mfd/asic3: Fix race in installing chained IRQ handler
Date: Wed, 1 Jul 2015 09:30:00 +0100 [thread overview]
Message-ID: <20150701083000.GI3210@x1> (raw)
In-Reply-To: <tip-c30e30478c74e5be2fa3bbe954084a31f0d60570@git.kernel.org>
On Fri, 26 Jun 2015, tip-bot for Thomas Gleixner wrote:
> Commit-ID: c30e30478c74e5be2fa3bbe954084a31f0d60570
> Gitweb: http://git.kernel.org/tip/c30e30478c74e5be2fa3bbe954084a31f0d60570
> Author: Thomas Gleixner <tglx@linutronix.de>
> AuthorDate: Sun, 21 Jun 2015 20:16:06 +0200
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitDate: Thu, 25 Jun 2015 11:56:52 +0200
>
> mfd/asic3: Fix race in installing chained IRQ handler
>
> Fix a race where a pending interrupt could be received and the handler
> called before the handler's data has been setup, by converting to
> irq_set_chained_handler_and_data().
>
> Search and conversion was done with coccinelle:
>
> @@
> expression E1, E2, E3;
> @@
> (
> -if (irq_set_chained_handler(E1, E3) != 0)
> - BUG();
> |
> -irq_set_chained_handler(E1, E3);
> )
> -irq_set_handler_data(E1, E2);
> +irq_set_chained_handler_and_data(E1, E3, E2);
>
> @@
> expression E1, E2, E3;
> @@
> (
> -if (irq_set_chained_handler(E1, E3) != 0)
> - BUG();
> ...
> |
> -irq_set_chained_handler(E1, E3);
> ...
> )
> -irq_set_handler_data(E1, E2);
> +irq_set_chained_handler_and_data(E1, E3, E2);
>
> Reported-by: Russell King <rmk+kernel@arm.linux.org.uk>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Julia Lawall <Julia.Lawall@lip6.fr>
> Cc: Samuel Ortiz <sameo@linux.intel.com>
> Cc: Lee Jones <lee.jones@linaro.org>
> ---
> drivers/mfd/asic3.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Applied to MFD -fixes.
> diff --git a/drivers/mfd/asic3.c b/drivers/mfd/asic3.c
> index 977bd3a..120df5c 100644
> --- a/drivers/mfd/asic3.c
> +++ b/drivers/mfd/asic3.c
> @@ -417,9 +417,8 @@ static int __init asic3_irq_probe(struct platform_device *pdev)
> asic3_write_register(asic, ASIC3_OFFSET(INTR, INT_MASK),
> ASIC3_INTMASK_GINTMASK);
>
> - irq_set_chained_handler(asic->irq_nr, asic3_irq_demux);
> + irq_set_chained_handler_and_data(asic->irq_nr, asic3_irq_demux, asic);
> irq_set_irq_type(asic->irq_nr, IRQ_TYPE_EDGE_RISING);
> - irq_set_handler_data(asic->irq_nr, asic);
>
> return 0;
> }
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next parent reply other threads:[~2015-07-01 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-c30e30478c74e5be2fa3bbe954084a31f0d60570@git.kernel.org>
2015-07-01 8:30 ` Lee Jones [this message]
2015-07-01 8:33 ` [tip:irq/urgent] mfd/asic3: Fix race in installing chained IRQ handler Thomas Gleixner
2015-07-01 14:07 ` Lee Jones
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=20150701083000.GI3210@x1 \
--to=lee.jones@linaro.org \
--cc=Julia.Lawall@lip6.fr \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=sameo@linux.intel.com \
--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