All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: early: xhci-dbc: Fix early_ioremap leak
Date: Sat, 28 Jun 2025 16:47:17 +0200	[thread overview]
Message-ID: <2025062803-paver-octane-e038@gregkh> (raw)
In-Reply-To: <20250627-xdbc-v1-1-43cc8c317b1b@intel.com>

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@intel.com>
> ---
>  drivers/usb/early/xhci-dbc.c | 4 ++++
>  1 file changed, 4 insertions(+)

What commit id does this fix?

thanks,

greg k-h

  reply	other threads:[~2025-06-28 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 21:47 [PATCH] usb: early: xhci-dbc: Fix early_ioremap leak Lucas De Marchi
2025-06-28 14:47 ` Greg Kroah-Hartman [this message]
2025-06-30 13:48   ` Lucas De Marchi

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=2025062803-paver-octane-e038@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.