All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 David Hildenbrand <david@kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	 "Liam R. Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	 Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	 Baoquan He <baoquan.he@linux.dev>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	 Pratyush Yadav <pratyush@kernel.org>,
	Miaohe Lin <linmiaohe@huawei.com>,
	 Naoya Horiguchi <nao.horiguchi@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 kexec@lists.infradead.org, rmikey@meta.com, riel@surriel.com,
	kernel-team@meta.com,  Kiryl Shutsemau <kas@kernel.org>,
	Bradley Morgan <include@grrlz.net>
Subject: Re: [PATCH v6 0/2] kexec: keep the next kernel off hardware-poisoned pages
Date: Wed, 19 Aug 2026 03:28:02 -0700	[thread overview]
Message-ID: <aoWEmbTWYU7wSQWb@gmail.com> (raw)
In-Reply-To: <aoV5EfBtlWcyf51E@kernel.org>

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/


  reply	other threads:[~2026-08-19 10:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 11:31 [PATCH v6 0/2] kexec: keep the next kernel off hardware-poisoned pages Breno Leitao
2026-08-12 11:31 ` [PATCH v6 1/2] kexec_file: stop the top-down search before it underflows Breno Leitao
2026-08-12 15:06   ` Bradley Morgan
2026-08-12 11:31 ` [PATCH v6 2/2] kexec: keep the next kernel off hardware-poisoned pages Breno Leitao
2026-08-18 12:15   ` Miaohe Lin
2026-08-12 11:36 ` [PATCH v6 0/2] " Bradley Morgan
2026-08-12 12:07   ` Breno Leitao
2026-08-12 12:11     ` Bradley Morgan
2026-08-19  9:36 ` Mike Rapoport
2026-08-19 10:28   ` Breno Leitao [this message]
2026-08-19 14:23   ` Bradley Morgan

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=aoWEmbTWYU7wSQWb@gmail.com \
    --to=leitao@debian.org \
    --cc=akpm@linux-foundation.org \
    --cc=baoquan.he@linux.dev \
    --cc=david@kernel.org \
    --cc=include@grrlz.net \
    --cc=kas@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=kexec@lists.infradead.org \
    --cc=liam@infradead.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=nao.horiguchi@gmail.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=riel@surriel.com \
    --cc=rmikey@meta.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@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 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.