All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Breno Leitao <leitao@debian.org>
Cc: Miaohe Lin <linmiaohe@huawei.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org, kernel-team@meta.com,
	David Hildenbrand <david@kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
	Naoya Horiguchi <nao.horiguchi@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	lance.yang@linux.dev, Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH v10 6/6] selftests/mm: add hwpoison-panic destructive test
Date: Tue, 28 Jul 2026 12:20:16 -0700	[thread overview]
Message-ID: <20260728122016.30752d36c3b3c3af231efa9d@linux-foundation.org> (raw)
In-Reply-To: <amh1nZVVaaZSGD3M@gmail.com>

On Tue, 28 Jul 2026 02:29:39 -0700 Breno Leitao <leitao@debian.org> wrote:

> On Tue, Jul 28, 2026 at 04:57:13PM +0800, Miaohe Lin wrote:
> > On 2026/7/28 12:24, Andrew Morton wrote:
> > > On Thu, 9 Jul 2026 11:34:05 +0800 Miaohe Lin <linmiaohe@huawei.com> wrote:
> > > 
> > >>> The script is intentionally NOT wired into run_vmtests.sh: every
> > >>> successful run panics the kernel, which is incompatible with the
> > >>> sequential "run each category in the same VM" model that
> > >>> run_vmtests.sh assumes.  It is also not registered as a TEST_PROGS /
> > >>> ksft_* wrapper so a default kselftest run does not opt itself into
> > >>> a panic.  The script is meant to be executed manually inside a
> > >>> disposable VM (e.g. virtme-ng), one variant per VM boot, and
> > >>> requires RUN_DESTRUCTIVE=1 in the environment as a safety net.
> > >>>
> > >>> Signed-off-by: Breno Leitao <leitao@debian.org>
> > >>
> > >> With Mike's comment addressed:
> > >>
> > >> Acked-by: Miaohe Lin <linmiaohe@huawei.com>
> > > 
> > > As I understand it, Breno would prefer not to rewrite the selftest in C
> > > at this time.  IOW, we stick with the bash version for now and add
> > > "convert this to C" to the todo list, OK?
> > 
> > Sure. Should I make this change or should we wait until Breno has time to do it?
> 
> Apologies for the delay. This is on my TODO list, and I'll prioritize it.
> 
> Just to confirm: the feature is already in mm-next without the selftest, so I
> only need to submit the C version of the test, correct?

The bash script is still there, no known issues.

We have the thing and tests are useful.  I'd say retain it until the
rewrite-in-C happens?

  reply	other threads:[~2026-07-28 19:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 12:46 [PATCH v10 0/6] mm/memory-failure: add panic option for unrecoverable pages Breno Leitao
2026-06-30 12:46 ` [PATCH v10 1/6] mm/memory-failure: drop dead error_states[] entry for reserved pages Breno Leitao
2026-06-30 12:46 ` [PATCH v10 2/6] mm/memory-failure: surface unhandlable kernel pages as -ENOTRECOVERABLE Breno Leitao
2026-07-06 12:22   ` Miaohe Lin
2026-06-30 12:46 ` [PATCH v10 3/6] mm/memory-failure: report MF_MSG_KERNEL for unrecoverable kernel pages Breno Leitao
2026-06-30 12:46 ` [PATCH v10 4/6] mm/memory-failure: add panic option for unrecoverable pages Breno Leitao
2026-06-30 12:46 ` [PATCH v10 5/6] Documentation: document panic_on_unrecoverable_memory_failure sysctl Breno Leitao
2026-07-09  3:18   ` Miaohe Lin
2026-06-30 12:46 ` [PATCH v10 6/6] selftests/mm: add hwpoison-panic destructive test Breno Leitao
2026-07-04  9:31   ` Mike Rapoport
2026-07-06 16:14     ` Breno Leitao
2026-07-06 16:23       ` Mike Rapoport
2026-07-09  3:34   ` Miaohe Lin
2026-07-28  4:24     ` Andrew Morton
2026-07-28  8:57       ` Miaohe Lin
2026-07-28  9:29         ` Breno Leitao
2026-07-28 19:20           ` Andrew Morton [this message]
2026-07-28 19:21             ` David Hildenbrand (Arm)
2026-07-28 22:07               ` Breno Leitao
2026-07-28  9:35       ` David Hildenbrand (Arm)
2026-06-30 20:55 ` [PATCH v10 0/6] mm/memory-failure: add panic option for unrecoverable pages Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2026-06-26 15:33 Breno Leitao
2026-06-26 15:33 ` [PATCH v10 6/6] selftests/mm: add hwpoison-panic destructive test Breno Leitao
2026-06-27  7:52   ` Mike Rapoport
2026-06-29 15:50     ` Breno Leitao

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=20260728122016.30752d36c3b3c3af231efa9d@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=lance.yang@linux.dev \
    --cc=leitao@debian.org \
    --cc=liam@infradead.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=mhocko@suse.com \
    --cc=nao.horiguchi@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=rppt@kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.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.