Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Bradley Morgan <include@grrlz.net>
Cc: Breno Leitao <leitao@debian.org>,
	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>
Subject: Re: [PATCH v6 0/2] kexec: keep the next kernel off hardware-poisoned pages
Date: Thu, 20 Aug 2026 09:33:58 +0300	[thread overview]
Message-ID: <aoaf1qNNbv40Mqmr@kernel.org> (raw)
In-Reply-To: <6CB4696E-03E3-42A0-9E3B-6BD1E143D5ED@grrlz.net>

On Wed, Aug 19, 2026 at 03:23:04PM +0100, Bradley Morgan wrote:
> On 19 August 2026 10:36:17 BST, Mike Rapoport <rppt@kernel.org> 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.
> > 
> 
> Ah, so it'll appear in a maintainers tree after MW?

Yes
 
> >> Signed-off-by: Breno Leitao <leitao@debian.org>
> >> ---
> >> Changes in v6:
> >> - Split the pre-existing top-down underflow out into its own patch, and
> >>   drop the "if (poison < kbuf->memsz)" guard from the hwpoison hunk now
> >>   that the loop bail-out covers it. (Mike Rapoport, Sashiko)
> >> - Reword the changelog: the MCE comes from reading the poison back, not
> >>   from the relocation copy writing it, and the placement paragraphs read
> >>   better split up. (Mike Rapoport)
> >> - Move cond_resched() after the struct page dereference, so the scan
> >does
> >>   not yield between pfn_to_online_page() and is_page_hwpoison().
> >>   (Pratyush Yadav, Sashiko)
> >> - Keep cond_resched() per pfn rather than batching it. (Kiryl Shutsemau,
> >>   Rik van Riel)
> >> - Link to v5:
> >https://patch.msgid.link/20260810-kexec_posioned-v5-1-95e1b5e2e656@debian.org
> >> 
> >> Changes in v5:
> >> - Return -EHWPOISON instead of -EADDRNOTAVAIL
> >> - Leverage is_page_hwpoison() instead of per-page check
> >> - Link to v4:
> >https://patch.msgid.link/20260807-kexec_posioned-v4-1-70d57f14625d@debian.org
> >> 
> >> Changes in v4:
> >> - Anchor the top-down hole finder on the first poisoned page in the
> >>   window and the bottom-up one on the last, so each jumps clear of the
> >>   poison in one step. New range_first_hwpoison(). (Kiryl Shutsemau)
> >> - Count a poisoned hugetlb folio in full: the flag lives on the folio,
> >>   not on the subpages, so the per-pfn scan missed poisoned tail pages.
> >>   (Kiryl Shutsemau)
> >> - Link to v3:
> >https://patch.msgid.link/20260803-kexec_posioned-v3-1-83aa6ede0351@debian.org
> >> 
> >> Changes in v3:
> >> - Return the address of the last poisoned page in the range, or
> >>   PHYS_ADDR_MAX when it is clean, instead of a bool plus an output
> >>   parameter. Renamed to range_last_hwpoison(). (Pratyush Yadav)
> >> - Add cond_resched() to the scan loop, as a segment can span half of
> >>   memory. (Sashiko)
> >> - Link to v2:
> >https://patch.msgid.link/20260730-kexec_posioned-v2-1-f92d18551f64@debian.org
> >> 
> >> Changes in v2:
> >> - Change from pfn_to_page() to pfn_to_online_page(). (Miaohe Lin)
> >> - Return the poisoned address once we find a hit, to avoid the O(n^2)
> >>   rescan. (Sashiko)
> >> - Link to v1:
> >https://patch.msgid.link/20260728-kexec_posioned-v1-1-160c81d180fe@debian.org
> >> 
> >> To: Andrew Morton <akpm@linux-foundation.org>
> >> To: David Hildenbrand <david@kernel.org>
> >> To: Lorenzo Stoakes <ljs@kernel.org>
> >> To: "Liam R. Howlett" <liam@infradead.org>
> >> To: Vlastimil Babka <vbabka@kernel.org>
> >> To: Mike Rapoport <rppt@kernel.org>
> >> To: Suren Baghdasaryan <surenb@google.com>
> >> To: Michal Hocko <mhocko@suse.com>
> >> To: Baoquan He <baoquan.he@linux.dev>
> >> To: Pasha Tatashin <pasha.tatashin@soleen.com>
> >> To: Pratyush Yadav <pratyush@kernel.org>
> >> To: Miaohe Lin <linmiaohe@huawei.com>
> >> To: Naoya Horiguchi <nao.horiguchi@gmail.com>
> >> Cc: linux-mm@kvack.org
> >> Cc: linux-kernel@vger.kernel.org
> >> Cc: kexec@lists.infradead.org
> >> Cc: rmikey@meta.com
> >> Cc: riel@surriel.com
> >> 
> >> ---
> >> Breno Leitao (2):
> >>       kexec_file: stop the top-down search before it underflows
> >>       kexec: keep the next kernel off hardware-poisoned pages
> >> 
> >>  include/linux/mm.h  | 14 ++++++++++++++
> >>  kernel/kexec_core.c | 10 ++++++++++
> >>  kernel/kexec_file.c | 20 +++++++++++++++++++-
> >>  mm/memory-failure.c | 40 ++++++++++++++++++++++++++++++++++++++++
> >>  4 files changed, 83 insertions(+), 1 deletion(-)
> >> ---
> >> base-commit: c5e32e86ca02b003f86e095d379b38148999293d
> >> change-id: 20260727-kexec_posioned-72bb0a4143a0
> >> 
> >> Best regards,
> >> --  
> >> Breno Leitao <leitao@debian.org>
> >> 
> >
> >
> 
> Thanks!

-- 
Sincerely yours,
Mike.


      reply	other threads:[~2026-08-20  6:34 UTC|newest]

Thread overview: 12+ 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
2026-08-19 14:23   ` Bradley Morgan
2026-08-20  6:33     ` Mike Rapoport [this message]

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=aoaf1qNNbv40Mqmr@kernel.org \
    --to=rppt@kernel.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=leitao@debian.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox