linux-kernel - Re: [PATCH] usb: early: xhci-dbc: Fix early

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2025062803-paver-octane-e038@gregkh>
Date: Sat, 28 Jun 2025 16:47:17 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Lucas De Marchi <lucas.demarchi@...el.com>
Cc: linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: early: xhci-dbc: Fix early_ioremap leak

On Fri, Jun 27, 2025 at 02:47:47PM -0700, Lucas De Marchi wrote:
> Using the kernel param earlyprintk=xdbc,keep without proper hardware
> setup leads to this:
> 
> 	[ ] xhci_dbc:early_xdbc_parse_parameter: dbgp_num: 0
> 	...
> 	[ ] xhci_dbc:early_xdbc_setup_hardware: failed to setup the connection to host
> 	...
> 	[ ] calling  kmemleak_late_init+0x0/0xa0 @ 1
> 	[ ] kmemleak: Kernel memory leak detector initialized (mem pool available: 14919)
> 	[ ] kmemleak: Automatic memory scanning thread started
> 	[ ] initcall kmemleak_late_init+0x0/0xa0 returned 0 after 417 usecs
> 	[ ] calling  check_early_ioremap_leak+0x0/0x70 @ 1
> 	[ ] ------------[ cut here ]------------
> 	[ ] Debug warning: early ioremap leak of 1 areas detected.
> 	    please boot with early_ioremap_debug and report the dmesg.
> 	[ ] WARNING: CPU: 11 PID: 1 at mm/early_ioremap.c:90 check_early_ioremap_leak+0x4e/0x70
> 
> When early_xdbc_setup_hardware() fails, make sure to call
> early_iounmap() since xdbc_init() won't handle it.
> 
> Signed-off-by: Lucas De Marchi <lucas.demarchi@...el.com>
> ---
>  drivers/usb/early/xhci-dbc.c | 4 ++++
>  1 file changed, 4 insertions(+)

What commit id does this fix?

thanks,

greg k-h