From: Kevin Hilman <khilman@deeprootsystems.com>
To: Daniel Walker <dwalker@fifo99.com>
Cc: linux-omap@vger.kernel.org, Julia Lawall <julia@diku.dk>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] arm: omap: iovmm: add missing mutex_unlock
Date: Mon, 28 Sep 2009 09:51:05 -0700 [thread overview]
Message-ID: <87ws3j3tdy.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1254001039-27976-1-git-send-email-dwalker@fifo99.com> (Daniel Walker's message of "Sat\, 26 Sep 2009 14\:37\:19 -0700")
Daniel Walker <dwalker@fifo99.com> writes:
> I was using Coccinelle with the mutex_unlock semantic patch, and it
> unconvered this problem. It appears to be a valid missing unlock issue.
> This change should correct it by moving the unlock below the label.
>
> This patch is against the mainline kernel.
>
> Cc: Julia Lawall <julia@diku.dk>
> Cc: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Daniel Walker <dwalker@fifo99.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
> ---
> arch/arm/plat-omap/iovmm.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/plat-omap/iovmm.c b/arch/arm/plat-omap/iovmm.c
> index 57f7122..9b6cb90 100644
> --- a/arch/arm/plat-omap/iovmm.c
> +++ b/arch/arm/plat-omap/iovmm.c
> @@ -363,8 +363,9 @@ void *da_to_va(struct iommu *obj, u32 da)
> goto out;
> }
> va = area->va;
> - mutex_unlock(&obj->mmap_lock);
> out:
> + mutex_unlock(&obj->mmap_lock);
> +
> return va;
> }
> EXPORT_SYMBOL_GPL(da_to_va);
> --
> 1.6.0.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-09-28 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 21:37 [PATCH] arm: omap: iovmm: add missing mutex_unlock Daniel Walker
2009-09-28 16:51 ` Kevin Hilman [this message]
2009-10-02 21:55 ` [APPLIED] " Tony Lindgren
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=87ws3j3tdy.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=dwalker@fifo99.com \
--cc=julia@diku.dk \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 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.