[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a2e474ec-51f4-c006-b64a-8851d852621d@arm.com>
Date: Fri, 18 Jan 2019 19:12:25 +0000
From: Robin Murphy <robin.murphy@....com>
To: Marc Gonzalez <marc.w.gonzalez@...e.fr>,
Catalin Marinas <catalin.marinas@....com>
Cc: Mark Rutland <mark.rutland@....com>, Arnd Bergmann <arnd@...db.de>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Oscar Salvador <osalvador@...e.de>,
Wei Yang <richard.weiyang@...il.com>,
Michal Hocko <mhocko@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Sri Krishna chowdary <schowdary@...dia.com>,
Qian Cai <cai@....pw>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: kmemleak panic
On 2019-01-18 3:36 pm, Marc Gonzalez wrote:
> Unable to handle kernel paging request at virtual address ffffffc021e00000
I can't help but notice that you seem to get the same address in 4
different logs - if it really is that deterministic then that's quite
the boon for debugging (FWIW my first thought is that it looks a lot
like a phys_to_virt() of something bogus). I've never used kmemleak
myself, but looking at where it's crashing it appears to think that that
address is a valid object - if I'm reading the docs correctly then I
guess the "dump" command ought to be able to tell you where it thinks
that object came from.
Robin.
Powered by blists - more mailing lists