From: Benjamin Tissoires <bentiss@kernel.org>
To: "Günther Noack" <gnoack@google.com>
Cc: Jiri Kosina <jikos@kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] HID: Fix some memory leaks in drivers/hid
Date: Tue, 17 Feb 2026 19:36:46 +0100 [thread overview]
Message-ID: <aZS0OAaSPhX2pJ6l@plouf> (raw)
In-Reply-To: <20260217160125.1097578-1-gnoack@google.com>
On Feb 17 2026, Günther Noack wrote:
> Hello!
>
> These patches fix a few memory leaks in HID report descriptor fixups.
>
> FWIW, a good ad-hoc way to look for usages of allocation functions in
> these is:
>
> awk '/static.*report_fixup.*/,/^}/ { print FILENAME, $0 }' drivers/hid/hid-*.c \
> | grep -E '(malloc|kzalloc|kcalloc|kmemdup)'
>
> The devm_* variants are safe in this context, because they tie the
> allocated memory to the lifetime of the driver.
No. Look at hid_close_report() in drivers/hid/hid-core.c.
HID still hasn't fully migrated to devm, so as a rule of thumb, if you
change a kzalloc into a devm_kzalloc, you are getting into troubles
unless you fix the all the kfree path.
>
> For transparency, I generated these commits with Gemini-CLI,
> starting with this prompt:
>
> We are working in the Linux kernel. In the HID drivers in
> `drivers/hid/hid-*.c`, the `report_fixup` driver hook is a function
> that gets a byte buffer (with size) as input and that may modify that
> byte buffer, and optionally return a pointer to a new byte buffer and
> update the size. The returned value is *not* memory-managed by the
> caller though and will not be freed subsequently. When the
If the memory is *not* managed, why would gemini converts kzalloc into
devm variants without changing the kfree paths????
> `report_fixup` implementation allocates a new buffer and returns that,
> that will not get freed by the caller.
This is wrong. See hid_close_report(): if the new rdesc (after fixup)
differs from the one initially set, there is an explicit call to
kfree().
-> there is no memleak AFAICT, and your prompt is wrong.
Cheers,
Benjamin
> Validate this assessment and
> fix up all HID drivers where that mistake is made.
>
> (and then a little bit of additional nudging for the details).
>
> —Günther
>
>
> Günther Noack (3):
> HID: apple: avoid memory leak in apple_report_fixup()
> HID: magicmouse: avoid memory leak in magicmouse_report_fixup()
> HID: asus: avoid memory leak in asus_report_fixup()
>
> drivers/hid/hid-apple.c | 4 +---
> drivers/hid/hid-asus.c | 15 +++++++++++----
> drivers/hid/hid-magicmouse.c | 4 +---
> 3 files changed, 13 insertions(+), 10 deletions(-)
>
> --
> 2.53.0.335.g19a08e0c02-goog
>
next prev parent reply other threads:[~2026-02-17 18:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 16:01 [PATCH 0/3] HID: Fix some memory leaks in drivers/hid Günther Noack
2026-02-17 16:01 ` [PATCH 1/3] HID: apple: avoid memory leak in apple_report_fixup() Günther Noack
2026-02-17 18:22 ` Benjamin Tissoires
2026-02-17 19:42 ` Günther Noack
2026-02-18 19:04 ` Benjamin Tissoires
2026-02-19 15:47 ` Günther Noack
2026-02-17 16:01 ` [PATCH 2/3] HID: magicmouse: avoid memory leak in magicmouse_report_fixup() Günther Noack
2026-02-17 16:01 ` [PATCH 3/3] HID: asus: avoid memory leak in asus_report_fixup() Günther Noack
2026-02-17 18:31 ` Benjamin Tissoires
2026-02-17 19:51 ` Günther Noack
2026-02-17 18:36 ` Benjamin Tissoires [this message]
2026-02-17 20:08 ` [PATCH 0/3] HID: Fix some memory leaks in drivers/hid Günther Noack
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=aZS0OAaSPhX2pJ6l@plouf \
--to=bentiss@kernel.org \
--cc=gnoack@google.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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