From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, SJ Park <sj@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-riscv@lists.infradead.org, kernel-team@meta.com
Subject: Re: [PATCH v3] tools/mm: add hwpoison-panic tool
Date: Wed, 4 Nov 2026 16:34:21 +0100 [thread overview]
Message-ID: <c37d96d6-49af-4319-8ac5-2afd3ae8492a@kernel.org> (raw)
In-Reply-To: <autEaeyHvhi8vvSK@gmail.com>
On 11/4/26 15:43, Breno Leitao wrote:
> On Wed, Nov 04, 2026 at 03:35:16PM +0100, David Hildenbrand (Arm) wrote:
>> On 8/13/26 13:45, Breno Leitao wrote:
>>> Add a tool that enables the vm.panic_on_unrecoverable_memory_failure
>>> sysctl, picks a kernel-owned PFN and writes its physical address to
>>> hard_offline_page. Three page kinds are selectable with -k: rodata
>>> (default), slab or pgtable. In all cases the host should panic.
>>>
>>> Example:
>>>
>>> # ./hwpoison-panic -k slab --yes-panic-my-kernel
>>> injecting hwpoison at phys 0x100032000 (pfn 0x100032, kind=slab)
>>> expecting kernel panic: 'Memory failure: <pfn>: unrecoverable page'
>>>
>>> In dmesg, you will see:
>>>
>>> Memory failure: 0x100032: unhandlable page.
>>> Memory failure: 0x100032: recovery action for reserved kernel page: Ignored
>>> Kernel panic - not syncing: Memory failure: 0x100032: unrecoverable page
>>>
>>> This lives in tools/mm rather than selftests/mm because every successful
>>> run crashes the machine, which is not something to run from CI.
>>>
>>> The --yes-panic-my-kernel argument is required so an accidental
>>> invocation does not take the box down.
>>
>> This is not upstream yet, right?
>
> Right. :-(
>
>> Anything missing or is this good to go in?
>
> I would say this is good to go, David.
Agreed, nothing jumped at me and this is useful.
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
@Andrew will you pick this up?
--
Cheers,
David
prev parent reply other threads:[~2026-11-04 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 11:45 Breno Leitao
2026-08-13 12:07 ` Miaohe Lin
2026-08-14 3:18 ` SJ Park
2026-11-04 14:35 ` David Hildenbrand (Arm)
2026-11-04 14:43 ` Breno Leitao
2026-11-04 15:34 ` David Hildenbrand (Arm) [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=c37d96d6-49af-4319-8ac5-2afd3ae8492a@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nao.horiguchi@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=sj@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
all inboxes | Powered by JetHome®