From: Catalin Marinas <catalin.marinas@arm.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
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
Subject: Re: kmemleak detects leak in msr_build_context
Date: Fri, 14 Jan 2022 11:09:49 +0000 [thread overview]
Message-ID: <YeFZ/cPoKPx4h1N0@arm.com> (raw)
In-Reply-To: <Yd4PwSBbIbg3TnNv@zn.tnic>
On Wed, Jan 12, 2022 at 12:16:17AM +0100, Borislav Petkov wrote:
> 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...
That's probably because slab_post_alloc_hook() doesn't get the original
kmalloc() size, so it uses the slab object size when calling the
kmemleak hook.
--
Catalin
next prev parent reply other threads:[~2022-01-14 11:09 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
2022-01-14 11:09 ` Catalin Marinas [this message]
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=YeFZ/cPoKPx4h1N0@arm.com \
--to=catalin.marinas@arm.com \
--cc=bp@alien8.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox