Thread (43 messages) 43 messages, 6 authors, 2010-10-14

Re: [2/8] IR: make sure we register the input device when it is safe to do so.

From: Jarod Wilson <hidden>
Date: 2010-10-14 19:31:22
Also in: linux-media

On Mon, Sep 06, 2010 at 09:26:07PM -0000, Maxim Levitsky wrote:
As soon as input device is registered, it might be accessed (and it is)
This can trigger a hardware interrupt that can access
not yet initialized ir->raw, (by sending a sample)

This can be reproduced by holding down a remote button and reloading the module.
And this always crashes the systems where hardware decides to send an interrupt
right at the moment it is enabled.

Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
Another one I thought I'd acked, but I don't see the ack in patchwork, so
it may have been from an earlier/superseded version...

Finally got my head wrapped around this one too, and I do see the
problem, and this fix looks good to me.

Acked-by: Jarod Wilson <redacted>

-- 
Jarod Wilson
jarod@redhat.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help