From: Miaohe Lin <linmiaohe@huawei.com>
To: Lisa Wang <wyihan@google.com>
Cc: <rientjes@google.com>, <seanjc@google.com>,
<ackerleytng@google.com>, <vannapurve@google.com>,
<michael.roth@amd.com>, <jiaqiyan@google.com>, <tabba@google.com>,
<dave.hansen@linux.intel.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>, Hugh Dickins <hughd@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"David Hildenbrand" <david@kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
<linux-kselftest@vger.kernel.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>
Subject: Re: [PATCH RFC v3 5/7] mm: selftests: Add shmem into memory failure test
Date: Mon, 13 Apr 2026 19:57:55 +0800 [thread overview]
Message-ID: <9effbeca-3453-f0fe-571f-85f8923e1385@huawei.com> (raw)
In-Reply-To: <20260408-memory-failure-mf-delayed-fix-rfc-v3-v3-5-718f45eb7c75@google.com>
On 2026/4/9 1:24, Lisa Wang wrote:
> Add a shmem memory failure selftest to test the shmem memory failure is
> correct after modifying shmem return value.
>
> Test that
> + madvise() call returns 0 when the poisoned shmem page is clean
> + trigger a SIGBUS when the poisoned shmem page is dirty
> + trigger another SIGBUS when the poisoned shmem page is fault-in again.
>
> Signed-off-by: Lisa Wang <wyihan@google.com>
Thanks for your patch. Two questions below.
> ---
> tools/testing/selftests/mm/memory-failure.c | 109 +++++++++++++++++++++++++++-
> 1 file changed, 106 insertions(+), 3 deletions(-)
>
> diff --git a/tools/testing/selftests/mm/memory-failure.c b/tools/testing/selftests/mm/memory-failure.c
> index 3d9e0b9ffb41..eb3f8d98f6c9 100644
> --- a/tools/testing/selftests/mm/memory-failure.c
> +++ b/tools/testing/selftests/mm/memory-failure.c
> @@ -30,9 +30,14 @@ enum result_type {
> MADV_HARD_ANON,
> MADV_HARD_CLEAN_PAGECACHE,
> MADV_HARD_DIRTY_PAGECACHE,
> + MADV_HARD_CLEAN_SHMEM,
> + MADV_HARD_DIRTY_SHMEM,
> MADV_SOFT_ANON,
> MADV_SOFT_CLEAN_PAGECACHE,
> MADV_SOFT_DIRTY_PAGECACHE,
> + MADV_SOFT_CLEAN_SHMEM,
> + MADV_SOFT_DIRTY_SHMEM,
> + READ_ERROR,
> };
>
> static jmp_buf signal_jmp_buf;
> @@ -165,17 +170,21 @@ static void check(struct __test_metadata *_metadata, FIXTURE_DATA(memory_failure
> case MADV_HARD_CLEAN_PAGECACHE:
> case MADV_SOFT_CLEAN_PAGECACHE:
> case MADV_SOFT_DIRTY_PAGECACHE:
> - /* It is not expected to receive a SIGBUS signal. */
> - ASSERT_EQ(setjmp, 0);
> -
> + case MADV_SOFT_DIRTY_SHMEM:
> /* The page content should remain unchanged. */
> ASSERT_TRUE(check_memory(vaddr, self->page_size));
Why we skip check_memory() for case MADV_SOFT_CLEAN_SHMEM?
> + case MADV_HARD_CLEAN_SHMEM:
> + case MADV_SOFT_CLEAN_SHMEM:
> + /* It is not expected to receive a SIGBUS signal. */
> + ASSERT_EQ(setjmp, 0);
>
> /* The backing pfn of addr should have changed. */
> ASSERT_NE(pagemap_get_pfn(self->pagemap_fd, vaddr), self->pfn);
> break;
> case MADV_HARD_ANON:
> case MADV_HARD_DIRTY_PAGECACHE:
> + case MADV_HARD_DIRTY_SHMEM:
> + case READ_ERROR:
> /* The SIGBUS signal should have been received. */
> ASSERT_EQ(setjmp, 1);
>
> @@ -260,6 +269,20 @@ static int prepare_file(const char *fname, unsigned long size)
> return fd;
> }
>
> +static int prepare_shmem(const char *fname, unsigned long size)
> +{
> + int fd;
> +
> + fd = memfd_create(fname, 0);
> + if (fd < 0)
> + return -1;
> + if (ftruncate(fd, size) < 0) {
> + close(fd);
> + return -1;
> + }
> + return fd;
> +}
> +
> /* Borrowed from mm/gup_longterm.c. */
> static int get_fs_type(int fd)
> {
> @@ -356,4 +379,84 @@ TEST_F(memory_failure, dirty_pagecache)
> ASSERT_EQ(close(fd), 0);
> }
>
> +TEST_F(memory_failure, dirty_shmem)
> +{
> + int fd;
> + char *addr;
> + int ret;
> +
> + fd = prepare_shmem("shmem-file", self->page_size);
> + if (fd < 0)
> + SKIP(return, "failed to open test shmem-file.\n");
> +
> + addr = mmap(0, self->page_size, PROT_READ | PROT_WRITE,
> + MAP_SHARED, fd, 0);
> + if (addr == MAP_FAILED) {
> + close(fd);
> + SKIP(return, "mmap failed, not enough memory.\n");
> + }
> + memset(addr, 0xce, self->page_size);
> +
> + prepare(_metadata, self, addr);
> +
> + ret = sigsetjmp(signal_jmp_buf, 1);
> + if (ret == 0)
> + ASSERT_EQ(variant->inject(self, addr), 0);
> +
> + if (variant->type == MADV_HARD) {
> + check(_metadata, self, addr, MADV_HARD_DIRTY_SHMEM, ret);
> + ret = sigsetjmp(signal_jmp_buf, 1);
> + if (ret == 0)
> + FORCE_READ(*addr);
> + check(_metadata, self, addr, READ_ERROR, ret);
> + } else {
Should we always add a FORCE_READ() just after variant->inject to verify the accessibility
to the addr for soft-offline case ?
Thanks.
.
> + check(_metadata, self, addr, MADV_SOFT_DIRTY_SHMEM, ret);> + }
> +
> + ASSERT_EQ(munmap(addr, self->page_size), 0);
> +
> + ASSERT_EQ(close(fd), 0);
> + cleanup(_metadata, self, addr);
> +}
> +
> +TEST_F(memory_failure, clean_shmem)
> +{
> + int fd;
> + char *addr;
> + int ret;
> +
> + fd = prepare_shmem("shmem-file", self->page_size);
> + if (fd < 0)
> + SKIP(return, "failed to open test shmem-file.\n");
> +
> + addr = mmap(0, self->page_size, PROT_READ | PROT_WRITE,
> + MAP_SHARED, fd, 0);
> + if (addr == MAP_FAILED) {
> + close(fd);
> + SKIP(return, "mmap failed, not enough memory.\n");
> + }
> + FORCE_READ(*addr);
> +
> + prepare(_metadata, self, addr);
> +
> + ret = sigsetjmp(signal_jmp_buf, 1);
> + if (ret == 0)
> + ASSERT_EQ(variant->inject(self, addr), 0);
> +
> + if (variant->type == MADV_HARD) {
> + check(_metadata, self, addr, MADV_HARD_CLEAN_SHMEM, ret);
> + ret = sigsetjmp(signal_jmp_buf, 1);
> + if (ret == 0)
> + FORCE_READ(*addr);
> + check(_metadata, self, addr, READ_ERROR, ret);
> + } else {
> + check(_metadata, self, addr, MADV_SOFT_CLEAN_SHMEM, ret);
> + }
> +
> + ASSERT_EQ(munmap(addr, self->page_size), 0);
> +
> + ASSERT_EQ(close(fd), 0);
> + cleanup(_metadata, self, addr);
> +}
> +
> TEST_HARNESS_MAIN
>
next prev parent reply other threads:[~2026-04-13 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 17:24 [PATCH RFC v3 0/7] mm: Fix MF_DELAYED handling on memory failure Lisa Wang
2026-04-08 17:24 ` [PATCH RFC v3 1/7] mm: memory_failure: Clarify the MF_DELAYED definition Lisa Wang
2026-04-08 17:24 ` [PATCH RFC v3 2/7] mm: memory_failure: Allow truncate_error_folio to return MF_DELAYED Lisa Wang
2026-04-08 17:24 ` [PATCH RFC v3 3/7] mm: shmem: Update shmem handler to the MF_DELAYED definition Lisa Wang
2026-04-08 17:24 ` [PATCH RFC v3 4/7] mm: memory_failure: Generalize extra_pins handling to all MF_DELAYED cases Lisa Wang
2026-04-08 17:24 ` [PATCH RFC v3 5/7] mm: selftests: Add shmem into memory failure test Lisa Wang
2026-04-13 11:57 ` Miaohe Lin [this message]
2026-04-08 17:24 ` [PATCH RFC v3 6/7] KVM: selftests: Add memory failure tests in guest_memfd_test Lisa Wang
2026-04-08 17:24 ` [PATCH RFC v3 7/7] KVM: selftests: Test guest_memfd behavior with respect to stage 2 page tables Lisa Wang
2026-04-13 11:48 ` [PATCH RFC v3 0/7] mm: Fix MF_DELAYED handling on memory failure Miaohe Lin
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=9effbeca-3453-f0fe-571f-85f8923e1385@huawei.com \
--to=linmiaohe@huawei.com \
--cc=Liam.Howlett@oracle.com \
--cc=ackerleytng@google.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=hughd@google.com \
--cc=jiaqiyan@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=michael.roth@amd.com \
--cc=nao.horiguchi@gmail.com \
--cc=pbonzini@redhat.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=tabba@google.com \
--cc=vannapurve@google.com \
--cc=vbabka@kernel.org \
--cc=wyihan@google.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