Hrm, I went looking to see if I could help resolve, but I have to admit,
at first glance I don't get it. The commit diff:

$ git diff 7a324b3f0535ceb0f6676fa20ca2a7b6213008cb 
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 3da354af7a0a..ef009db512ee 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -406,7 +406,7 @@ static int hid_parser_global(struct hid_parser *parser, 
struct hid_item *item)
                parser->global.report_size = item_udata(item);
-               if (parser->global.report_size > 128) {
+               if (parser->global.report_size > 256) {
                        hid_err(parser->device, "invalid report_size %d\n",
                        return -1;

The increase from 128 to 256 should not create a scenario where the bug
can exist. If it was originally below 128 and not throwing an error,
then it should be below 256.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  hid-sensor-hub spamming dmesg in 4.20

Status in linux package in Ubuntu:

Bug description:
  Dmesg is a constant barrage of the same error:
  [  406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called 
with n (192) > 32! (kworker/5:1)

  This does not occur in 4.19 but does occur in all mainline 4.20
  releases including 4.20.13 (linux-image-unsigned-4.20.13-042013).
  Tested with both Ubuntu's included libinput 1.10 and an updated
  libinput 1.12.

  Hardware (from lspci) includes a synaptic touchpad. Having the xorg
  synaptic driver installed makes no difference.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to