[PATCH v6 0/2] kexec: keep the next kernel off hardware-poisoned pages
Breno Leitao
leitao at debian.org
Wed Aug 19 03:28:02 PDT 2026
On Wed, Aug 19, 2026 at 12:36:17PM +0300, Mike Rapoport wrote:
> On Wed, Aug 12, 2026 at 04:31:50AM -0700, Breno Leitao wrote:
> > Memory failures are common enough on large fleets that kexec regularly
> > lands the next kernel on a frame the memory failure subsystem has already
> > marked bad. Patch 2 teaches the segment placement to avoid those frames.
> >
> > Patch 1 is a prerequisite. locate_mem_hole_top_down() walks candidates
> > downwards without ever checking that the subtraction stays above zero, so
> > the walk can wrap and report success with a destination outside of RAM.
> > Patch 2 adds one more downward step to that loop, so the bug is fixed
> > first and both patches rely on the same bail-out.
>
> I queued this for v7.4, the patches will appear in the liveupdate tree
> after the merge window.
Thanks Mike.
I'll now get back to the most ambicious patchset that carries poisoned
page information over to the next kernel, so memory failure information
survive across kexec:
https://lore.kernel.org/all/20260717-hwpoison-kho-v1-0-9c5eda551998@debian.org/
More information about the kexec
mailing list