[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yd4PwSBbIbg3TnNv@zn.tnic>
Date: Wed, 12 Jan 2022 00:16:17 +0100
From: Borislav Petkov <bp@...en8.de>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: Dave Hansen <dave.hansen@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
Catalin Marinas <catalin.marinas@....com>
Subject: Re: kmemleak detects leak in msr_build_context
On Tue, Jan 11, 2022 at 10:05:43PM +0100, Paul Menzel wrote:
> [ 0.672475] smpboot: CPU0: AMD A6-6400K APU with Radeon(tm) HD Graphics (family: 0x15, model: 0x13, stepping: 0x1)
I have a similar box to yours:
[ 0.382127] smpboot: CPU0: AMD PRO A12-8800B R7, 12 Compute Cores 4C+8G (family: 0x15, model: 0x60, stepping: 0x1)
...
[ 0.974044] x86/pm: family 0x15 cpu detected, MSR saving is needed during suspending.
well, Bulldozer-based at least, and booting with kmemleak enabled is fine:
$ cat /sys/kernel/debug/kmemleak
$
I wonder whether you have something else applied and forgotten along
with all those random printks I'm seeing in dmesg...
Also,
unreferenced object 0xffff8914823de500 (size 64):
^^^^^^^^
That's strange too - sizeof(struct saved_msr) is 40 and not 64 so that
looks weird...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists