All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Dave Hansen <dave.hansen@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: kmemleak detects leak in msr_build_context
Date: Wed, 12 Jan 2022 00:16:17 +0100	[thread overview]
Message-ID: <Yd4PwSBbIbg3TnNv@zn.tnic> (raw)
In-Reply-To: <41359b02-5f03-b822-9407-fb8d5ce44e70@molgen.mpg.de>

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

  reply	other threads:[~2022-01-11 23:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  7:49 kmemleak detects leak in msr_build_context Paul Menzel
2022-01-11 15:26 ` Dave Hansen
2022-01-11 21:05   ` Paul Menzel
2022-01-11 23:16     ` Borislav Petkov [this message]
2022-01-14 11:09       ` Catalin Marinas
2022-01-14 11:44     ` Catalin Marinas

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=Yd4PwSBbIbg3TnNv@zn.tnic \
    --to=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.