From: Marek Vasut <marek.vasut@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 7/17] arch/arm/common: Add missing spin_unlock_irqrestore
Date: Wed, 26 May 2010 17:07:06 +0000 [thread overview]
Message-ID: <201005261907.06198.marek.vasut@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1005261756000.23743@ask.diku.dk>
Dne St 26. května 2010 17:56:14 Julia Lawall napsal(a):
> From: Julia Lawall <julia@diku.dk>
>
> Add a spin_unlock_irqrestore missing on the error path. Although the lock
> is destroyed with the rest of the sachip structure in the function
> __sa1111_remove, it still seems useful to restore the interrupt state.
>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> expression E1;
> @@
>
> * spin_lock_irqsave(E1,...);
> <+... when != E1
> if (...) {
> ... when != E1
> * return ...;
> }
> ...+>
> * spin_unlock_irqrestore(E1,...);
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
>
> ---
> Perhaps the unlock is now too early?
>
> arch/arm/common/sa1111.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/common/sa1111.c b/arch/arm/common/sa1111.c
> index a52a27c..59e38ff 100644
> --- a/arch/arm/common/sa1111.c
> +++ b/arch/arm/common/sa1111.c
> @@ -959,6 +959,7 @@ static int sa1111_resume(struct platform_device *dev)
> */
> id = sa1111_readl(sachip->base + SA1111_SKID);
> if ((id & SKID_ID_MASK) != SKID_SA1111_ID) {
> + spin_unlock_irqrestore(&sachip->lock, flags);
> __sa1111_remove(sachip);
> platform_set_drvdata(dev, NULL);
> kfree(save);
Why are "readl"s protected by spinlock anyway ? Can't we just move the locking
past the code above ?
I'm no sa1111 expert though, Russell ?
Cheers
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/17] arch/arm/common: Add missing spin_unlock_irqrestore
Date: Wed, 26 May 2010 19:07:06 +0200 [thread overview]
Message-ID: <201005261907.06198.marek.vasut@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1005261756000.23743@ask.diku.dk>
Dne St 26. kv?tna 2010 17:56:14 Julia Lawall napsal(a):
> From: Julia Lawall <julia@diku.dk>
>
> Add a spin_unlock_irqrestore missing on the error path. Although the lock
> is destroyed with the rest of the sachip structure in the function
> __sa1111_remove, it still seems useful to restore the interrupt state.
>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> expression E1;
> @@
>
> * spin_lock_irqsave(E1,...);
> <+... when != E1
> if (...) {
> ... when != E1
> * return ...;
> }
> ...+>
> * spin_unlock_irqrestore(E1,...);
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
>
> ---
> Perhaps the unlock is now too early?
>
> arch/arm/common/sa1111.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/common/sa1111.c b/arch/arm/common/sa1111.c
> index a52a27c..59e38ff 100644
> --- a/arch/arm/common/sa1111.c
> +++ b/arch/arm/common/sa1111.c
> @@ -959,6 +959,7 @@ static int sa1111_resume(struct platform_device *dev)
> */
> id = sa1111_readl(sachip->base + SA1111_SKID);
> if ((id & SKID_ID_MASK) != SKID_SA1111_ID) {
> + spin_unlock_irqrestore(&sachip->lock, flags);
> __sa1111_remove(sachip);
> platform_set_drvdata(dev, NULL);
> kfree(save);
Why are "readl"s protected by spinlock anyway ? Can't we just move the locking
past the code above ?
I'm no sa1111 expert though, Russell ?
Cheers
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marek.vasut@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Julia Lawall <julia@diku.dk>,
Russell King <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 7/17] arch/arm/common: Add missing spin_unlock_irqrestore
Date: Wed, 26 May 2010 19:07:06 +0200 [thread overview]
Message-ID: <201005261907.06198.marek.vasut@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1005261756000.23743@ask.diku.dk>
Dne St 26. května 2010 17:56:14 Julia Lawall napsal(a):
> From: Julia Lawall <julia@diku.dk>
>
> Add a spin_unlock_irqrestore missing on the error path. Although the lock
> is destroyed with the rest of the sachip structure in the function
> __sa1111_remove, it still seems useful to restore the interrupt state.
>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> expression E1;
> @@
>
> * spin_lock_irqsave(E1,...);
> <+... when != E1
> if (...) {
> ... when != E1
> * return ...;
> }
> ...+>
> * spin_unlock_irqrestore(E1,...);
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
>
> ---
> Perhaps the unlock is now too early?
>
> arch/arm/common/sa1111.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/common/sa1111.c b/arch/arm/common/sa1111.c
> index a52a27c..59e38ff 100644
> --- a/arch/arm/common/sa1111.c
> +++ b/arch/arm/common/sa1111.c
> @@ -959,6 +959,7 @@ static int sa1111_resume(struct platform_device *dev)
> */
> id = sa1111_readl(sachip->base + SA1111_SKID);
> if ((id & SKID_ID_MASK) != SKID_SA1111_ID) {
> + spin_unlock_irqrestore(&sachip->lock, flags);
> __sa1111_remove(sachip);
> platform_set_drvdata(dev, NULL);
> kfree(save);
Why are "readl"s protected by spinlock anyway ? Can't we just move the locking
past the code above ?
I'm no sa1111 expert though, Russell ?
Cheers
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2010-05-26 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 15:56 [PATCH 7/17] arch/arm/common: Add missing spin_unlock_irqrestore Julia Lawall
2010-05-26 15:56 ` Julia Lawall
2010-05-26 15:56 ` Julia Lawall
2010-05-26 17:07 ` Marek Vasut [this message]
2010-05-26 17:07 ` Marek Vasut
2010-05-26 17:07 ` Marek Vasut
2010-05-26 18:43 ` [PATCH 7/17] arch/arm/common: Add missing Russell King - ARM Linux
2010-05-26 18:43 ` [PATCH 7/17] arch/arm/common: Add missing spin_unlock_irqrestore Russell King - ARM Linux
2010-05-26 18:43 ` Russell King - ARM Linux
2010-05-26 19:13 ` Marek Vasut
2010-05-26 19:13 ` Marek Vasut
2010-05-26 19:13 ` Marek Vasut
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=201005261907.06198.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.