diff options
| author | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-08-31 14:20:07 +0300 |
|---|---|---|
| committer | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-08-31 14:20:07 +0300 |
| commit | c7add4fee3fe444835e2127c9b41d1f633d5036b (patch) | |
| tree | 8d2359abbc6c329964dca23ad94eb62dac823d26 /scripts/Makefile.thinlto | |
| parent | cee9395acd8043be0644b25c34bfa86623f2b935 (diff) | |
| parent | c5c9a4e14bfa7163ef77c95272c7949ae1501134 (diff) | |
| download | linux-next-c7add4fee3fe444835e2127c9b41d1f633d5036b.tar.gz linux-next-c7add4fee3fe444835e2127c9b41d1f633d5036b.zip | |
Merge patch series "kexec: keep the next kernel off hardware-poisoned pages"
Breno Leitao <leitao@debian.org> says:
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.
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
