Linux USB
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219977] usb: dwc2: memory leak of hsotg->regset
Date: Mon, 16 Nov 2026 02:37:11 +0000	[thread overview]
Message-ID: <bug-219977-208809-fivi9EeG4U@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219977-208809@https.bugzilla.kernel.org/>

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

Wei Huang (daway320@163.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daway320@163.com

--- Comment #2 from Wei Huang (daway320@163.com) ---
Hi kakapapa2,

Good news - the fix for this issue has been merged into the mainline
kernel.

The patch was reviewed by the Synopsys DWC3 maintainer (Thinh
Nguyen) and merged via Greg Kroah-Hartman's USB tree during the
7.4 merge window:

    usb: dwc2: debugfs: fix memory leak of hsotg->regset
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8c7d5b1f34f0

The fix switches hsotg->regset from devm_kzalloc() to kzalloc() and
frees it explicitly in dwc2_debugfs_exit(), mirroring the equivalent
dwc3 fix (commit e6bdf8195b4a). The patch also carries a Cc: stable
tag, so it should be backported to supported stable series in due
course.

Once you get a chance to run a 7.4-rc or newer kernel (or a stable
release containing the backport), it would be great if you could
confirm the fix. If everything looks good, this bug can be closed
as RESOLVED CODE_FIX.

Thanks again for the clear report - pointing out the dwc3 precedent
made this straightforward to fix.

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

      parent reply	other threads:[~2026-11-16  2:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03  8:49 [Bug 219977] New: usb: dwc2: memory leak of hsotg->regset bugzilla-daemon
2026-08-10  7:10 ` [Bug 219977] " bugzilla-daemon
2026-11-16  2:37 ` 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-219977-208809-fivi9EeG4U@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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