Hi, Peter wrote a fuzzing uinput program[1] to check on libinput, and the result is that the kernel fails more often than libinput :) These 2 patches allow to fix the early failures. I marked them as stable as I believe eventhough not many people discovered those and reported them, they should still be fixed in current kernels. The fuzzing process still manages to crash the kernel, bu I have the feeling those crashes are now related to some races between other userspace process that attempt to handle the spurious events injected in those random devices. For instance, the KEY_BLUETOOTH or RF_KILL seem to manage to mess up my network driver. Cheers, Benjamin [1] https://github.com/whot/fuzzydevice Benjamin Tissoires (2): input - leds: do not iterate over non initialized leds input - leds: fix input_led_disconnect path drivers/input/input-leds.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) -- 2.14.3 -- 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
