Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Felipe Balbi <balbi@kernel.org>
To:     Mika Westerberg <mika.westerberg@linux.intel.com>,
        Paul Menzel <pmenzel@molgen.mpg.de>
Cc:     Greg KH <greg@kroah.com>, Mathias Nyman <mathias.nyman@intel.com>,
        linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: BUG: KASAN: use-after-free in xhci_trb_virt_to_dma.part.24+0x1c/0x80
In-Reply-To: <20200103110451.GJ465886@lahna.fi.intel.com>
References: <95b4bdb2-962f-561e-ac14-79cd44395915@molgen.mpg.de> <20180720095410.GA11904@kroah.com> <107dbdd1-4e45-836f-7f8f-85bc63374e4f@molgen.mpg.de> <30b069b5-63f6-dd9e-b323-668f06bff6cf@molgen.mpg.de> <20200103110451.GJ465886@lahna.fi.intel.com>
Date:   Thu, 09 Jan 2020 10:53:47 +0200
Message-ID: <875zhlt3hg.fsf@kernel.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
        micalg=pgp-sha256; protocol="application/pgp-signature"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Hi,

Mika Westerberg <mika.westerberg@linux.intel.com> 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?
>>=20
>> ```
>> 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=3Dxhci_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))

=2D-=20
balbi

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEElLzh7wn96CXwjh2IzL64meEamQYFAl4W6hsACgkQzL64meEa
mQahAw//eVR5E4c0CZ9GI782MazL/BmWTpoHqKhbEONjRiqeFy8tdytMt7Ea4j1g
VTo/hWfLp7JIR7TY6DL1OYHBTjjM/vWG5NNI5qzXKAZJ8pAc/33IWlUnhrF35sks
DTsB0H0IJdwvqDgcNGBCSwufVbaHbk7M65fxkjcmLGiYUJ/YaZn5qIHi/5/4OHff
PGuZhV8fvrYMAUyfyVnlks3rN+545nW2yaiQfuVGZEK+QGupMTgGZMYh7ZfkMnAh
l/uWczDQKLAuIu/NvRin+nZWSIvc5JJn8DbIlI3Y8e8J0oHUSV2Icfkou6TW/c7J
YB7rIr74QOfS6PqG1xvLtCO1wv/JWsBpbdwUV8F0nrbYp7AupN1QKhVaYMBukESP
9KJTEYYjG0RdYVwE3SnjSiMJXGnIwt/s7bcZN7kbeHPFPE3DdIJ2yVCK22JeN7fp
scts2s15m+FWb+bsPO1wve5rci7L5uDrUpq45fnPqIE/W0r5ffUXdYnEyKuLbMoJ
/e61PNRLrXL2ptSsYq7eu4HybBlJzFBj8t9tMDdg4YAuChjVUD1YIvOIcBPCq4L3
MbLW3CbG8AjFDHpWWMFK/F010lvemVDMuSEJFF2afc5ZuHK4915Urve1gncWB0CF
OsJW0wA+3YafO8ULyn+BTUEc13SBJsFRIW90ojcQDRrDCXsdP6c=
=152o
-----END PGP SIGNATURE-----
--=-=-=--