From: Miaohe Lin <linmiaohe@huawei.com>
To: Zi Yan <ziy@nvidia.com>, Sayali Patil <sayalip@linux.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
Ritesh Harjani <ritesh.list@gmail.com>,
David Hildenbrand <david@redhat.com>,
Michal Hocko <mhocko@kernel.org>,
"Oscar Salvador" <osalvador@suse.de>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Dev Jain <dev.jain@arm.com>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
<Liam.Howlett@oracle.com>
Subject: Re: [PATCH 12/13] selftests/mm: move hwpoison setup into run_test() and silence modprobe output for memory-failure category
Date: Wed, 11 Mar 2026 10:21:06 +0800 [thread overview]
Message-ID: <ae5108d1-4bf1-7b48-b299-ea3f12ee50e1@huawei.com> (raw)
In-Reply-To: <556E284E-9638-4F4E-8CE4-7158DB914AED@nvidia.com>
On 2026/3/11 3:15, Zi Yan wrote:
> On 10 Mar 2026, at 5:49, Sayali Patil wrote:
>
>> run_vmtests.sh contains special handling to ensure the hwpoison_inject
>> module is available for the memory-failure tests. This logic was
>> implemented outside of run_test(), making the setup category-specific
>> but managed globally.
>>
>> Move the hwpoison_inject handling into run_test() and restrict it
>> to the memory-failure category so that:
>> 1. the module is checked and loaded only when memory-failure tests run,
>> 2. the test is skipped if the module or the debugfs interface
>> (/sys/kernel/debug/hwpoison/) is not available.
>> 3. the module is unloaded after the test if it was loaded by the script.
>>
>> This localizes category-specific setup and makes the test flow
>> consistent with other per-category preparations.
>>
>> While updating this logic, fix the module availability check.
>> The script previously used:
>>
>> modprobe -R hwpoison_inject
>>
>> The -R option prints the resolved module name to stdout, causing every
>> run to print:
>>
>> hwpoison_inject
>>
>> in the test output, even when no action is required, introducing
>> unnecessary noise.
>>
>> Replace this with:
>>
>> modprobe -n hwpoison_inject
>>
>> which verifies that the module is loadable without producing output,
>> keeping the selftest logs clean and consistent.
>>
>> Fixes: ff4ef2fbd101 ("selftests/mm: add memory failure anonymous page test")
>> Signed-off-by: Sayali Patil <sayalip@linux.ibm.com>
>> ---
>> tools/testing/selftests/mm/run_vmtests.sh | 46 ++++++++++++++---------
>> 1 file changed, 28 insertions(+), 18 deletions(-)
>>
>> diff --git a/tools/testing/selftests/mm/run_vmtests.sh b/tools/testing/selftests/mm/run_vmtests.sh
>> index 7273c3e18227..7f3a3027cd9a 100755
>> --- a/tools/testing/selftests/mm/run_vmtests.sh
>> +++ b/tools/testing/selftests/mm/run_vmtests.sh
>> @@ -250,6 +250,27 @@ run_test() {
>> fi
>> fi
>>
>> + # Ensure hwpoison_inject is available for memory-failure tests
>> + if [ "${CATEGORY}" = "memory-failure" ]; then
>> + # Try to load hwpoison_inject if not present.
>> + HWPOISON_DIR=/sys/kernel/debug/hwpoison/
>> + if [ ! -d "$HWPOISON_DIR" ]; then
>> + if ! modprobe -n hwpoison_inject > /dev/null 2>&1; then
>> + echo "Module hwpoison_inject not found, skipping..." \
>> + | tap_prefix
>> + skip=1
>> + else
>> + modprobe hwpoison_inject > /dev/null 2>&1
>> + LOADED_MOD=1
>> + fi
>> + fi
>> +
>> + if [ ! -d "$HWPOISON_DIR" ]; then
>> + echo "hwpoison debugfs interface not present" | tap_prefix
>> + skip=1
>> + fi
>> + fi
>> +
>> local test=$(pretty_name "$*")
>> local title="running $*"
>> local sep=$(echo -n "$title" | tr "[:graph:][:space:]" -)
>> @@ -261,6 +282,12 @@ run_test() {
>> else
>> local ret=$ksft_skip
>> fi
>> +
>> + # Unload hwpoison_inject if we loaded it
>> + if [ -n "${LOADED_MOD}" ]; then
>> + modprobe -r hwpoison_inject > /dev/null 2>&1
>> + fi
>> +
>> count_total=$(( count_total + 1 ))
>> if [ $ret -eq 0 ]; then
>> count_pass=$(( count_pass + 1 ))
>> @@ -540,24 +567,7 @@ CATEGORY="page_frag" run_test ./test_page_frag.sh nonaligned
>>
>> CATEGORY="rmap" run_test ./rmap
>>
>> -# Try to load hwpoison_inject if not present.
>> -HWPOISON_DIR=/sys/kernel/debug/hwpoison/
>> -if [ ! -d "$HWPOISON_DIR" ]; then
>> - if ! modprobe -q -R hwpoison_inject; then
>> - echo "Module hwpoison_inject not found, skipping..."
>> - else
>> - modprobe hwpoison_inject > /dev/null 2>&1
>> - LOADED_MOD=1
>> - fi
>> -fi
>> -
>> -if [ -d "$HWPOISON_DIR" ]; then
>> - CATEGORY="memory-failure" run_test ./memory-failure
>> -fi
>> -
>> -if [ -n "${LOADED_MOD}" ]; then
>> - modprobe -r hwpoison_inject > /dev/null 2>&1
>> -fi
>> +CATEGORY="memory-failure" run_test ./memory-failure
>>
>> if [ "${HAVE_HUGEPAGES}" = 1 ]; then
>> echo "$orig_nr_hugepgs" > /proc/sys/vm/nr_hugepages
>> --
>> 2.52.0
>
> +Miaohe
>
> LGTM.
>
> Acked-by: Zi Yan <ziy@nvidia.com>
LGTM. Thanks both.
Acked-by: Miaohe Lin <linmiaohe@huawei.com>
Thanks.
.
next prev parent reply other threads:[~2026-03-11 2:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 9:49 [PATCH 00/13] selftests/mm: fix failures and robustness improvements Sayali Patil
2026-03-10 9:49 ` [PATCH 01/13] selftests/mm: restore default nr_hugepages value during cleanup in charge_reserved_hugetlb.sh Sayali Patil
2026-03-10 18:43 ` Zi Yan
2026-03-10 9:49 ` [PATCH 02/13] selftests/mm: fix hugetlb pathname construction " Sayali Patil
2026-03-10 18:54 ` Zi Yan
2026-03-10 9:49 ` [PATCH 03/13] selftests/mm: fix hugetlb pathname construction in hugetlb_reparenting_test.sh Sayali Patil
2026-03-10 18:55 ` Zi Yan
2026-03-10 9:49 ` [PATCH 04/13] selftest/mm: fix cgroup task placement and tolerance " Sayali Patil
2026-03-10 9:49 ` [PATCH 05/13] selftests/mm: size tmpfs according to PMD page size in split_huge_page_test Sayali Patil
2026-03-10 18:59 ` Zi Yan
2026-03-10 9:49 ` [PATCH 06/13] selftest/mm: adjust hugepage-mremap test size for large huge pages Sayali Patil
2026-03-10 19:01 ` Zi Yan
2026-03-10 9:49 ` [PATCH 07/13] selftest/mm: register existing mapping with userfaultfd in hugepage-mremap Sayali Patil
2026-03-10 9:49 ` [PATCH 08/13] selftests/mm: ensure destination is hugetlb-backed " Sayali Patil
2026-03-10 19:07 ` Zi Yan
2026-03-10 9:49 ` [PATCH 09/13] selftests/mm: skip uffd-wp-mremap if UFFD write-protect is unsupported Sayali Patil
2026-03-10 19:07 ` Zi Yan
2026-03-10 9:49 ` [PATCH 10/13] selftests/mm: skip uffd-stress test when nr_pages_per_cpu is zero Sayali Patil
2026-03-10 19:08 ` Zi Yan
2026-03-10 9:49 ` [PATCH 11/13] selftests/mm: fix double increment in linked list cleanup in compaction_test Sayali Patil
2026-03-10 19:10 ` Zi Yan
2026-03-10 9:49 ` [PATCH 12/13] selftests/mm: move hwpoison setup into run_test() and silence modprobe output for memory-failure category Sayali Patil
2026-03-10 19:15 ` Zi Yan
2026-03-11 2:21 ` Miaohe Lin [this message]
2026-03-10 9:49 ` [PATCH 13/13] selftests/cgroup: extend test_hugetlb_memcg.c to support all huge page sizes Sayali Patil
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=ae5108d1-4bf1-7b48-b299-ea3f12ee50e1@huawei.com \
--to=linmiaohe@huawei.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=ritesh.list@gmail.com \
--cc=sayalip@linux.ibm.com \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.com \
--cc=ziy@nvidia.com \
/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