From: Jakub Kicinski <kuba@kernel.org>
To: torvalds@linux-foundation.org
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com,
Catalin Marinas <catalin.marinas@arm.com>,
Guo Weikang <guoweikang.kernel@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] Networking for v6.13-rc7
Date: Thu, 16 Jan 2025 19:38:21 -0800 [thread overview]
Message-ID: <20250116193821.2e12e728@kernel.org> (raw)
In-Reply-To: <173646486752.1541533.15419405499323104668.pr-tracker-bot@kernel.org>
On Thu, 09 Jan 2025 23:21:07 +0000 pr-tracker-bot@kernel.org wrote:
> The pull request you sent on Thu, 9 Jan 2025 10:29:53 -0800:
>
> > git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git tags/net-6.13-rc7
>
> has been merged into torvalds/linux.git:
> https://git.kernel.org/torvalds/c/c77cd47cee041bc1664b8e5fcd23036e5aab8e2a
Hi Linus!
After 76d5d4c53e68 ("mm/kmemleak: fix percpu memory leak detection
failure") we get this on every instance of our testing VMs:
unreferenced object 0x00042aa0 (size 64):
comm "swapper/0", pid 0, jiffies 4294667296
hex dump (first 32 bytes on cpu 2):
00 00 00 00 00 00 00 00 00 00 06 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 0):
pcpu_alloc_noprof+0x4ad/0xab0
setup_zone_pageset+0x30/0x290
setup_per_cpu_pageset+0x6a/0x1f0
start_kernel+0x2a4/0x410
x86_64_start_reservations+0x18/0x30
x86_64_start_kernel+0xba/0x110
common_startup_64+0x12c/0x138
unreferenced object 0x00042b00 (size 320):
comm "swapper/0", pid 0, jiffies 4294667296
hex dump (first 32 bytes on cpu 2):
00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .....N..........
ff ff ff ff ff ff ff ff c0 74 78 98 ff ff ff ff .........tx.....
backtrace (crc 0):
pcpu_alloc_noprof+0x4ad/0xab0
setup_zone_pageset+0x6e/0x290
setup_per_cpu_pageset+0x6a/0x1f0
start_kernel+0x2a4/0x410
x86_64_start_reservations+0x18/0x30
x86_64_start_kernel+0xba/0x110
common_startup_64+0x12c/0x138
unreferenced object 0x00042dc0 (size 48):
comm "swapper/0", pid 0, jiffies 4294667296
hex dump (first 32 bytes on cpu 2):
18 07 01 0b f3 00 00 ea 00 00 00 00 00 00 00 00 ................
00 00 09 09 17 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 0):
pcpu_alloc_noprof+0x4ad/0xab0
setup_per_cpu_pageset+0xd2/0x1f0
start_kernel+0x2a4/0x410
x86_64_start_reservations+0x18/0x30
x86_64_start_kernel+0xba/0x110
common_startup_64+0x12c/0x138
This is unlikely to be important, but I'm not getting any hits on lore
so I figured better safe than sorry...
next prev parent reply other threads:[~2025-01-17 3:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 18:29 [GIT PULL] Networking for v6.13-rc7 Jakub Kicinski
2025-01-09 23:21 ` pr-tracker-bot
2025-01-17 3:38 ` Jakub Kicinski [this message]
2025-01-18 13:45 ` Catalin Marinas
2025-01-20 14:51 ` Catalin Marinas
2025-01-20 17:45 ` Jakub Kicinski
2025-01-21 11:09 ` Catalin Marinas
2025-01-21 15:42 ` Jakub Kicinski
2025-01-21 20:46 ` Catalin Marinas
2025-01-23 17:11 ` Matthieu Baerts
2025-01-24 18:07 ` Andrea Righi
2025-01-27 14:27 ` Catalin Marinas
2025-01-27 17:39 ` Matthieu Baerts
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=20250116193821.2e12e728@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=guoweikang.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=torvalds@linux-foundation.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.