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@xxxxxxxxx> 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 <jarod@xxxxxxxxxx> -- Jarod Wilson jarod@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
