From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH v2] mm: Fix memblock_free_late() when using deferred struct page
Date: Fri, 20 Feb 2026 16:12:35 +1100 [thread overview]
Message-ID: <e6bee1f5a32b8164b66381d353d8182078619dbf.camel@kernel.crashing.org> (raw)
In-Reply-To: <aZbjCFqlqdFwKSHR@kernel.org>
Ugh ... backport to 6.12.68:
(sorry, no more logs, it's from the large scale testsuite, a couple of
hits out of 1450 tests but all run with "quiet" on the command line).
260 [ 0.014444] ACPI: SPCR: [Firmware Bug]: Unexpected SPCR Access Width. Defaulting to byte size
261 [ 1.015737] BUG: kernel NULL pointer dereference, address: 0000000000000000
262 [ 1.016238] #PF: supervisor read access in kernel mode
263 [ 1.016651] #PF: error_code(0x0000) - not-present page
264 [ 1.017070] PGD 0 P4D 0
265 [ 1.017274] Oops: Oops: 0000 [#1] PREEMPT SMP PTI
266 [ 1.017664] CPU: 23 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.68-94.123.amzn2023.x86_64 #1
267 [ 1.018384] Hardware name: Amazon EC2 c5n.metal/Not Specified, BIOS 1.0 10/16/2017
268 [ 1.019011] RIP: 0010:efi_free_boot_services_memory+0xd/0x60
269 [ 1.019472] Code: 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 8b 2d 2b a2 39 00 <48> 8b 45 00 48 85 c0 74 31 48 8b 75 08 31 c9 ba ff ff ff ff 48 83
270 [ 1.021033] RSP: 0000:ffffcfcd40037e00 EFLAGS: 00010246
271 [ 1.021461] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
272 [ 1.022059] RDX: 0000000000000000 RSI: 0000000000000202 RDI: ffffffffafa663d0
273 [ 1.022637] RBP: 0000000000000000 R08: 000001158a8b1d80 R09: 000001158a8b1d80
274 [ 1.023222] R10: 0000000000000012 R11: fefefefefefefeff R12: ffff8a8a5f142a00
275 [ 1.023813] R13: 0000000000000139 R14: 0000000000000000 R15: 0000000000000000
276 [ 1.024399] FS: 0000000000000000(0000) GS:ffff8a8a5ee80000(0000) knlGS:0000000000000000
277 [ 1.025064] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
278 [ 1.025513] CR2: 0000000000000000 CR3: 0000000683c34001 CR4: 00000000007706f0
279 [ 1.025513] PKRU: 55555554
280 [ 1.025513] Call Trace:
281 [ 1.025513] <TASK>
282 [ 1.025513] ? __pfx_efi_free_boot_services_memory+0x10/0x10
283 [ 1.025513] do_one_initcall+0x41/0x300
284 [ 1.025513] do_initcalls+0xac/0x130
285 [ 1.025513] kernel_init_freeable+0x256/0x310
286 [ 1.025513] ? __pfx_kernel_init+0x10/0x10
287 [ 1.025513] kernel_init+0x16/0x1c0
288 [ 1.025513] ret_from_fork+0x2d/0x50
289 [ 1.025513] ? __pfx_kernel_init+0x10/0x10
290 [ 1.025513] ret_from_fork_asm+0x1a/0x30
291 [ 1.025513] </TASK>
292 [ 1.025513] Modules linked in:
293 [ 1.025513] CR2: 0000000000000000
294 [ 1.025513] ---[ end trace 0000000000000000 ]---
295 [ 1.025513] RIP: 0010:efi_free_boot_services_memory+0xd/0x60
296 [ 1.025513] Code: 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 8b 2d 2b a2 39 00 <48> 8b 45 00 48 85 c0 74 31 48 8b 75 08 31 c9 ba ff ff ff ff 48 83
297 [ 1.025513] RSP: 0000:ffffcfcd40037e00 EFLAGS: 00010246
298 [ 1.025513] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
299 [ 1.025513] RDX: 0000000000000000 RSI: 0000000000000202 RDI: ffffffffafa663d0
300 [ 1.025513] RBP: 0000000000000000 R08: 000001158a8b1d80 R09: 000001158a8b1d80
301 [ 1.025513] R10: 0000000000000012 R11: fefefefefefefeff R12: ffff8a8a5f142a00
302 [ 1.025513] R13: 0000000000000139 R14: 0000000000000000 R15: 0000000000000000
303 [ 1.025513] FS: 0000000000000000(0000) GS:ffff8a8a5ee80000(0000) knlGS:0000000000000000
304 [ 1.025513] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
305 [ 1.025513] CR2: 0000000000000000 CR3: 0000000683c34001 CR4: 00000000007706f0
306 [ 1.025513] PKRU: 55555554
307 [ 1.025513] Kernel panic - not syncing: Fatal exception
308 [ 1.025513] Kernel Offset: 0x2c000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
309 [ 1.025513] ---[ end Kernel panic - not syncing: Fatal exception ]---
next prev parent reply other threads:[~2026-02-20 5:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 8:02 [PATCH] " Benjamin Herrenschmidt
2026-02-03 18:40 ` Mike Rapoport
2026-02-03 19:53 ` Benjamin Herrenschmidt
2026-02-04 7:39 ` Mike Rapoport
2026-02-04 9:02 ` Benjamin Herrenschmidt
2026-02-06 10:33 ` Mike Rapoport
2026-02-10 1:04 ` Benjamin Herrenschmidt
2026-02-10 2:10 ` Benjamin Herrenschmidt
2026-02-10 6:17 ` Benjamin Herrenschmidt
2026-02-10 8:34 ` Benjamin Herrenschmidt
2026-02-10 14:32 ` Mike Rapoport
2026-02-10 23:23 ` Benjamin Herrenschmidt
2026-02-11 5:20 ` Mike Rapoport
2026-02-16 5:34 ` Benjamin Herrenschmidt
2026-02-16 6:51 ` Benjamin Herrenschmidt
2026-02-16 4:53 ` Benjamin Herrenschmidt
2026-02-16 15:28 ` Mike Rapoport
2026-02-16 10:36 ` Alexander Potapenko
2026-02-17 8:28 ` [PATCH v2] " Benjamin Herrenschmidt
2026-02-17 12:32 ` Mike Rapoport
2026-02-17 22:00 ` Benjamin Herrenschmidt
2026-02-17 21:47 ` Benjamin Herrenschmidt
2026-02-18 0:15 ` Benjamin Herrenschmidt
2026-02-18 8:05 ` Mike Rapoport
2026-02-19 2:48 ` Benjamin Herrenschmidt
2026-02-19 10:16 ` Mike Rapoport
2026-02-19 22:46 ` Benjamin Herrenschmidt
2026-02-20 4:57 ` Benjamin Herrenschmidt
2026-02-20 9:09 ` Mike Rapoport
2026-02-20 9:00 ` Mike Rapoport
2026-02-20 5:12 ` Benjamin Herrenschmidt [this message]
2026-02-20 5:15 ` Benjamin Herrenschmidt
2026-02-20 5:47 ` Benjamin Herrenschmidt
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=e6bee1f5a32b8164b66381d353d8182078619dbf.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linux-mm@kvack.org \
--cc=rppt@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