mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <usama.anjum@arm.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: usama.anjum@arm.com, 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>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
	Zi Yan <ziy@nvidia.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Nico Pache <npache@redhat.com>,
	Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
	Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
	Usama Arif <usama.arif@linux.dev>,
	Naoya Horiguchi <nao.horiguchi@gmail.com>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, sarthak.sharma@arm.com
Subject: Re: [PATCH v2 4/5] selftests/mm: skip hard dirty page-cache test on NFS
Date: Mon, 27 Jul 2026 10:21:00 +0100	[thread overview]
Message-ID: <0ec4de92-5ddc-482b-98e4-9a26f9a6e622@arm.com> (raw)
In-Reply-To: <57c6bec2-3135-35ab-46c7-b1ab041393c9@huawei.com>

On 25/07/2026 3:10 am, Miaohe Lin wrote:
> On 2026/7/24 18:24, Muhammad Usama Anjum wrote:
>> The hard dirty_pagecache variant uses MADV_HWPOISON to exercise recovery
>> of a dirty file-backed page. The recovery path records -EIO in the
>> address_space mapping, which NFS later reports when the test closes the
>> file. This makes the test fail after the hwpoison checks have completed.
>>
>> Skip this variant when the test file is on NFS. Keep the hard clean-page
>> and both soft-offline variants enabled because they use folio removal,
>> invalidation, or migration rather than recording a delayed writeback
>> error.
>>
>> The unsupported-filesystem path in clean_pagecache() also returns
>> without closing the opened test file. Close the descriptor before
>> skipping there and in dirty_pagecache().
>>
>> Signed-off-by: Muhammad Usama Anjum <usama.anjum@arm.com>
>> ---
>> Changes since v1:
>> - Limit the NFS skip to the hard dirty-page variant.
>> ---
>>  tools/testing/selftests/mm/memory-failure.c | 9 +++++++--
>>  1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/testing/selftests/mm/memory-failure.c b/tools/testing/selftests/mm/memory-failure.c
>> index 032ed952057c6..3c72084f57e8b 100644
>> --- a/tools/testing/selftests/mm/memory-failure.c
>> +++ b/tools/testing/selftests/mm/memory-failure.c
>> @@ -283,8 +283,10 @@ TEST_F(memory_failure, clean_pagecache)
>>  	if (fd < 0)
>>  		SKIP(return, "failed to open test file.\n");
>>  	fs_type = get_fs_type(fd);
>> -	if (!fs_type || fs_type == TMPFS_MAGIC)
>> +	if (!fs_type || fs_type == TMPFS_MAGIC) {
>> +		close(fd);
>>  		SKIP(return, "unsupported filesystem :%x\n", fs_type);
>> +	}
>>  
>>  	addr = mmap(0, self->page_size, PROT_READ | PROT_WRITE,
>>  		    MAP_SHARED, fd, 0);
>> @@ -325,8 +327,11 @@ TEST_F(memory_failure, dirty_pagecache)
>>  	if (fd < 0)
>>  		SKIP(return, "failed to open test file.\n");
>>  	fs_type = get_fs_type(fd);
>> -	if (!fs_type || fs_type == TMPFS_MAGIC)
>> +	if (!fs_type || fs_type == TMPFS_MAGIC ||
>> +	    (fs_type == NFS_SUPER_MAGIC && variant->type == MADV_HARD)) {
> 
> It would be helpful if we add some comments here.
> 
> Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
Thanks for reviewing. Sure, I'll add a comment.

-- 
Thanks,
Usama


  reply	other threads:[~2026-07-27  9:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 10:24 [PATCH v2 0/5] selftests/mm: Handle unsupported and transient test conditions Muhammad Usama Anjum
2026-07-24 10:24 ` [PATCH v2 1/5] selftests/mm: skip COW tmpfile cases when fallocate() is unsupported Muhammad Usama Anjum
2026-07-24 10:24 ` [PATCH v2 2/5] selftests/mm: skip guard hole-punch test if MADV_REMOVE " Muhammad Usama Anjum
2026-07-24 10:24 ` [PATCH v2 3/5] selftests/mm: skip khugepaged swap tests without swap Muhammad Usama Anjum
2026-07-24 11:16   ` Sarthak Sharma
2026-07-24 10:24 ` [PATCH v2 4/5] selftests/mm: skip hard dirty page-cache test on NFS Muhammad Usama Anjum
2026-07-25  2:10   ` Miaohe Lin
2026-07-27  9:21     ` Muhammad Usama Anjum [this message]
2026-07-24 10:24 ` [PATCH v2 5/5] selftests/mm: retry migration failures for the full runtime Muhammad Usama Anjum
2026-07-24 11:46   ` Dev Jain
2026-07-24 11:53     ` Muhammad Usama Anjum
2026-07-24 15:23       ` Dev Jain
2026-07-24 15:57         ` Muhammad Usama Anjum
2026-07-25  9:25           ` Dev Jain
2026-07-27  9:20             ` Muhammad Usama Anjum

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=0ec4de92-5ddc-482b-98e4-9a26f9a6e622@arm.com \
    --to=usama.anjum@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=nao.horiguchi@gmail.com \
    --cc=npache@redhat.com \
    --cc=rppt@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=sarthak.sharma@arm.com \
    --cc=shuah@kernel.org \
    --cc=surenb@google.com \
    --cc=usama.arif@linux.dev \
    --cc=vbabka@kernel.org \
    --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

all inboxes | Powered by JetHome®