linux-kernel - Re: [PATCH 1/1] LEDS: leds-input, fix sleep inside atomic

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 16 Jun 2010 13:46:46 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Samuel Thibault <samuel.thibault@...-lyon.org>
Cc:	Jiri Slaby <jslaby@...e.cz>, rpurdie@...ys.net,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
	jirislaby@...il.com, Alessandro Zummo <a.zummo@...ertech.it>
Subject: Re: [PATCH 1/1] LEDS: leds-input, fix sleep inside atomic

On Sun, 6 Jun 2010 01:45:06 +0200
Samuel Thibault <samuel.thibault@...-lyon.org> wrote:

> Jiri Slaby, le Sat 05 Jun 2010 23:12:22 +0200, a __crit :
> > Fix this by changing the spinlock to mutex as it is used only in
> > input_handler->connect and ->disconnect and it is safe to sleep
> > there.
> 
> Right. in a previous patch it was also used in interrupt context, but
> now it should be safe indeed.
> 
> Andrew, please fold it into the leds-input patch.

hm, I did, nine days ago;

btw, leds-route-kbd-leds-through-the-generic-leds-layer.patch is still
in the "stuck" state coz Alessandro said he'd test it ;)

I think I'll start pestering Richard with it anyway.

--
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/