summaryrefslogtreecommitdiffstats
path: root/fs/coda
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2014-04-17 13:22:09 -0700
committerJiri Kosina <jkosina@suse.cz>2014-05-20 16:39:00 +0200
commit1b15d2e5b8077670b1e6a33250a0d9577efff4a5 (patch)
treece5ca1f217c59a604ea6378afc68710d65c4f5de /fs/coda
parent825747bb85634a2a7b7dce4e373831e211ab1644 (diff)
downloadlinux-stable-1b15d2e5b8077670b1e6a33250a0d9577efff4a5.tar.gz
linux-stable-1b15d2e5b8077670b1e6a33250a0d9577efff4a5.tar.bz2
linux-stable-1b15d2e5b8077670b1e6a33250a0d9577efff4a5.zip
HID: core: fix validation of report id 0
Some drivers use the first HID report in the list instead of using an index. In these cases, validation uses ID 0, which was supposed to mean "first known report". This fixes the problem, which was causing at least the lgff family of devices to stop working since hid_validate_values was being called with ID 0, but the devices used single numbered IDs for their reports: 0x05, 0x01, /* Usage Page (Desktop), */ 0x09, 0x05, /* Usage (Gamepad), */ 0xA1, 0x01, /* Collection (Application), */ 0xA1, 0x02, /* Collection (Logical), */ 0x85, 0x01, /* Report ID (1), */ ... Cc: stable@vger.kernel.org Reported-by: Simon Wood <simon@mungewell.org> Signed-off-by: Kees Cook <keescook@chromium.org> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'fs/coda')
0 files changed, 0 insertions, 0 deletions