From: Borislav Petkov <bp@alien8.de>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: AMD uncore kmemleak
Date: Wed, 9 Nov 2022 11:52:20 +0100 [thread overview]
Message-ID: <Y2uGZL1ou+JGu2mh@zn.tnic> (raw)
Hey,
Peter said you liked this stuff so here it is. :-)
On one of my test boxes (Carrizo laptop - that's an Excavator core) I
see the below. It happens with 6.1-rc1.
I booted latest -rc4 + tip/master and it is gone so something has
changed in the meantime or this particular version doesn't fire...
Anyway, we thought you should know in case you want to dig deeper.
Thx.
cat /sys/kernel/debug/kmemleak
unreferenced object 0xffff888101a3d3a0 (size 32):
comm "swapper/0", pid 1, jiffies 4294892455 (age 294.968s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<000000002f5fe849>] __kmalloc_node+0x5f/0x180
[<00000000066a1fb1>] amd_uncore_cpu_up_prepare+0xc7/0x240
[<000000005fa7fab5>] cpuhp_invoke_callback+0xf8/0x460
[<00000000d4b0952e>] cpuhp_issue_call+0x118/0x190
[<000000008cb1592a>] __cpuhp_setup_state_cpuslocked+0xee/0x2a0
[<0000000007534fa6>] __cpuhp_setup_state+0x76/0x100
[<00000000d8277f50>] amd_uncore_init+0x275/0x336
[<000000004af336cd>] do_one_initcall+0x44/0x200
[<0000000040cb5caf>] kernel_init_freeable+0x198/0x1e4
[<000000008b0e9fae>] kernel_init+0x16/0x120
[<00000000459bcaeb>] ret_from_fork+0x22/0x30
unreferenced object 0xffff888101a3d240 (size 32):
comm "swapper/0", pid 1, jiffies 4294892455 (age 294.968s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<000000002f5fe849>] __kmalloc_node+0x5f/0x180
[<00000000066a1fb1>] amd_uncore_cpu_up_prepare+0xc7/0x240
[<000000005fa7fab5>] cpuhp_invoke_callback+0xf8/0x460
[<00000000d4b0952e>] cpuhp_issue_call+0x118/0x190
[<000000008cb1592a>] __cpuhp_setup_state_cpuslocked+0xee/0x2a0
[<0000000007534fa6>] __cpuhp_setup_state+0x76/0x100
[<00000000d8277f50>] amd_uncore_init+0x275/0x336
[<000000004af336cd>] do_one_initcall+0x44/0x200
[<0000000040cb5caf>] kernel_init_freeable+0x198/0x1e4
[<000000008b0e9fae>] kernel_init+0x16/0x120
[<00000000459bcaeb>] ret_from_fork+0x22/0x30
unreferenced object 0xffff888101a3d4a0 (size 32):
comm "swapper/0", pid 1, jiffies 4294892455 (age 294.968s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<000000002f5fe849>] __kmalloc_node+0x5f/0x180
[<00000000066a1fb1>] amd_uncore_cpu_up_prepare+0xc7/0x240
[<000000005fa7fab5>] cpuhp_invoke_callback+0xf8/0x460
[<00000000d4b0952e>] cpuhp_issue_call+0x118/0x190
[<000000008cb1592a>] __cpuhp_setup_state_cpuslocked+0xee/0x2a0
[<0000000007534fa6>] __cpuhp_setup_state+0x76/0x100
[<00000000d8277f50>] amd_uncore_init+0x275/0x336
[<000000004af336cd>] do_one_initcall+0x44/0x200
[<0000000040cb5caf>] kernel_init_freeable+0x198/0x1e4
[<000000008b0e9fae>] kernel_init+0x16/0x120
[<00000000459bcaeb>] ret_from_fork+0x22/0x30
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2022-11-09 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 10:52 Borislav Petkov [this message]
2022-11-09 11:03 ` Ravi Bangoria
2022-11-09 11:09 ` Borislav Petkov
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=Y2uGZL1ou+JGu2mh@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ravi.bangoria@amd.com \
--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
all inboxes | Powered by JetHome®