linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 210015] page allocation failure in usb_hub_wq hub_event when adding HID device
Date: Mon, 09 Nov 2020 22:00:47 +0000	[thread overview]
Message-ID: <bug-210015-208809-h6DViiZeQ5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210015-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=210015

Dmitry Torokhov (dmitry.torokhov@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dmitry.torokhov@gmail.com

--- Comment #5 from Dmitry Torokhov (dmitry.torokhov@gmail.com) ---
32 pages for a single field suggests that there is a garbage in the descriptor
and blindly converting to kvmalloc_array() is indeed simply papering over the
problem.

I suggest you post hid report descriptor and maybe instrument
hid-core.c::hid_register_field() to see what number of usages and values it is
being asjed to allocate.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2020-11-09 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03  8:39 [Bug 210015] New: page allocation failure in usb_hub_wq hub_event when adding HID device bugzilla-daemon
2020-11-03  9:02 ` [Bug 210015] " bugzilla-daemon
2020-11-03 17:53 ` bugzilla-daemon
2020-11-03 18:07 ` bugzilla-daemon
2020-11-04  8:34 ` bugzilla-daemon
2020-11-09 22:00 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-210015-208809-h6DViiZeQ5@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).