From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>,
Mathias Nyman <mathias.nyman@intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>,
Alan Stern <stern@rowland.harvard.edu>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: BUG: drivers/usb/host/xhci: memleak in alloc from xhci_disable_usb3_lpm_timeout()
Date: Mon, 27 Mar 2023 12:41:34 +0300 [thread overview]
Message-ID: <b86fcdbd-f1c6-846f-838f-b7679ec4e2b4@linux.intel.com> (raw)
In-Reply-To: <651c0500-2b84-d938-fdc2-45e92b322b38@alu.unizg.hr>
On 25.3.2023 13.33, Mirsad Goran Todorovac wrote:
> On 25. 03. 2023. 12:27, Mirsad Goran Todorovac wrote:
>> Hi all!
>>
>> Here are again the good news and the bad news:
>>
>> BAD: another kernel memory leak detected (one more to hunt down and fix)
>> GOOD: another kernel memory leak detected (one less unaccounted for)
>>
>> I tried to make some fun, but maintainers are busy folks, so let's get down
>> to business:
>>
>> ---
>> Nine (9) new systemd-udevd kernel memory leaks occurred (unable to reproduce).
>>
>> The platform is Ubuntu 22.10 with (relatively recent) systemd 251.4-1ubuntu7.1
>> on LENOVO_MT_82H8_BU_idea_FM_IdeaPad 3 15ITL6 with BIOS GGCN51WW from 11/16/2022.
>>
>> The symptom (/sys/kernel/debug/kmemleak output):
>>
>> unreferenced object 0xffff909698ff9280 (size 64):
>> comm "systemd-udevd", pid 436, jiffies 4294893239 (age 6287.088s)
>> hex dump (first 32 bytes):
>> e0 51 bb 99 96 90 ff ff 00 00 00 00 00 00 00 00 .Q..............
>> 40 5b bb 99 96 90 ff ff 00 00 00 00 00 00 00 00 @[..............
>> backtrace:
>> [<ffffffffb29de94c>] slab_post_alloc_hook+0x8c/0x320
>> [<ffffffffb29e5107>] __kmem_cache_alloc_node+0x1c7/0x2b0
>> [<ffffffffb2962f3b>] kmalloc_node_trace+0x2b/0xa0
>> [<ffffffffb31af2ec>] xhci_alloc_command+0x7c/0x1b0
>> [<ffffffffb31af451>] xhci_alloc_command_with_ctx+0x21/0x70
>> [<ffffffffb31a8a3e>] xhci_change_max_exit_latency+0x2e/0x1c0>> [<ffffffffb31a8c5b>] xhci_disable_usb3_lpm_timeout+0x7b/0xb0
>> [<ffffffffb31457a7>] usb_disable_link_state+0x57/0xe0
Thanks for the report.
I think I found the leak, and wrote a patch for it.
Any chance you could test it with the same setup?
https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/commit/?h=for-usb-linus&id=8bacee588602ed74cc22aaf4c56b796300e5a943
Thanks
-Mathias
next prev parent reply other threads:[~2023-03-27 9:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 11:27 BUG: drivers/usb/host/xhci: memleak in alloc from xhci_disable_usb3_lpm_timeout() Mirsad Goran Todorovac
2023-03-25 11:33 ` Mirsad Goran Todorovac
2023-03-27 9:41 ` Mathias Nyman [this message]
2023-03-27 9:50 ` [PATCH] xhci: Free the command allocated for setting LPM if we return early Mathias Nyman
2023-03-27 11:51 ` Greg KH
2023-03-27 13:31 ` Mathias Nyman
2023-03-27 15:46 ` Mirsad Goran Todorovac
2023-03-27 22:25 ` Mirsad Goran Todorovac
2023-03-28 7:57 ` Mathias Nyman
2023-04-03 9:20 ` Mirsad Goran Todorovac
2023-03-27 12:04 ` BUG: drivers/usb/host/xhci: memleak in alloc from xhci_disable_usb3_lpm_timeout() Mirsad Goran Todorovac
2023-03-27 22:07 ` BUG: BISECTED: " Mirsad Goran Todorovac
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=b86fcdbd-f1c6-846f-838f-b7679ec4e2b4@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=stern@rowland.harvard.edu \
--cc=ubuntu-devel-discuss@lists.ubuntu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox