Hi, Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> writes: > On Thu, Jan 02, 2020 at 03:10:14PM +0100, Paul Menzel wrote: >> Mika, as you fixed the other leak, any idea, how to continue from the >> kmemleak log below? >> >> ``` >> unreferenced object 0xffff8c207a1e1408 (size 8): >> comm "systemd-udevd", pid 183, jiffies 4294667978 (age 752.292s) >> hex dump (first 8 bytes): >> 34 01 05 00 00 00 00 00 4....... >> backtrace: >> [<00000000aea7b46d>] xhci_mem_init+0xcfa/0xec0 [xhci_hcd] > > There are probably better ways for doing this but you can use objdump > for example: > > $ objdump -l --prefix-addresses -j .text --disassemble=xhci_mem_init drivers/usb/host/xhci-hcd.ko > > then find the offset xhci_mem_init+0xcfa. It should show you the line > numbers as well if you have compiled your kernel with debug info. This > should be close to the line that allocated the memory that was leaked. addr2line helps here. So does gdb (gdb vmlinux l *(xhci_mem_init+0xcfa)) -- balbi
Attachment:
signature.asc
Description: PGP signature
