linux-kernel - Re: [PATCH RFT 1/2] gpio: gpio-ml-ioh: Use spinlock for register access protection

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdYsFC+3+1P2sfab3viDUkkEXUgwOO6i2CUexkrA_K0X5g@mail.gmail.com>
Date:	Wed, 15 Aug 2012 00:18:47 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Axel Lin <axel.lin@...il.com>
Cc:	linux-kernel@...r.kernel.org, Feng Tang <feng.tang@...el.com>,
	Tomoya MORINAGA <tomoya.rohm@...il.com>,
	Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH RFT 1/2] gpio: gpio-ml-ioh: Use spinlock for register
 access protection

On Sun, Jul 29, 2012 at 4:54 AM, Axel Lin <axel.lin@...il.com> wrote:

> gpio_chip.can_sleep is 0, but current code uses mutex in ioh_gpio_set,
> ioh_gpio_get and ioh_gpio_direction_input functions.
> Thus those functions are not callable from interrupt context.
> This patch converts mutex into spinlock.
>
> Signed-off-by: Axel Lin <axel.lin@...il.com>

Applied to my devel branch for the next merge window, it doesn't
seem like a regression to me atleast.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/