aboutsummaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorJiri Kosina <jkosina@suse.cz>2011-10-28 12:15:02 -0400
committerJiri Kosina <jkosina@suse.cz>2011-11-16 09:00:31 -0500
commit6da7066906e977d42104a859c490f5f9a300488c (patch)
treea3dd189b80691d307840697da5cc68e6a75edfff /drivers
parente46e927b9b7e8d95526e69322855243882b7e1a3 (diff)
HID: ignore absolute values which don't fit between logical min and max
Linux should ignore values outside logical min/max range, as they are not meaningful. This is what at least some of other OSes do, and it also makes sense (currently the value gets misinterpreted larger up the stack). Reported-by: Denilson Figueiredo de Sá <denilsonsa@gmail.com> Tested-by: Denilson Figueiredo de Sá <denilsonsa@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/hid/hid-input.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
index f333139d1a4..b7b0d55c0ed 100644
--- a/drivers/hid/hid-input.c
+++ b/drivers/hid/hid-input.c
@@ -822,6 +822,13 @@ void hidinput_hid_event(struct hid_device *hid, struct hid_field *field, struct
822 return; 822 return;
823 } 823 }
824 824
825 /* Ignore absolute values that are out of bounds */
826 if ((usage->type == EV_ABS && (value < field->logical_minimum ||
827 value > field->logical_maximum))) {
828 dbg_hid("Ignoring out-of-range value %x\n", value);
829 return;
830 }
831
825 /* report the usage code as scancode if the key status has changed */ 832 /* report the usage code as scancode if the key status has changed */
826 if (usage->type == EV_KEY && !!test_bit(usage->code, input->key) != value) 833 if (usage->type == EV_KEY && !!test_bit(usage->code, input->key) != value)
827 input_event(input, EV_MSC, MSC_SCAN, usage->hid); 834 input_event(input, EV_MSC, MSC_SCAN, usage->hid);