linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: David Hildenbrand <david@redhat.com>,
	akpm@linux-foundation.org, hughd@google.com
Cc: willy@infradead.org, 21cnbao@gmail.com, ryan.roberts@arm.com,
	ziy@nvidia.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests: mincore: fix tmpfs mincore test failure
Date: Tue, 8 Apr 2025 16:11:33 +0800	[thread overview]
Message-ID: <f0026429-de3e-4e20-8603-39683180a643@linux.alibaba.com> (raw)
In-Reply-To: <61e36a73-2c8c-4897-9ba5-3b2d59f57b5d@redhat.com>



On 2025/4/7 23:04, David Hildenbrand wrote:
> On 07.04.25 13:31, Baolin Wang wrote:
>> When running mincore test cases, I encountered the following failures:
>>
>> "
>> mincore_selftest.c:359:check_tmpfs_mmap:Expected ra_pages (511) == 0 (0)
>> mincore_selftest.c:360:check_tmpfs_mmap:Read-ahead pages found in memory
>> check_tmpfs_mmap: Test terminated by assertion
>>            FAIL  global.check_tmpfs_mmap
>> not ok 5 global.check_tmpfs_mmap
>> FAILED: 4 / 5 tests passed
>> "
>>
>> The reason for the test case failure is that my system automatically 
>> enabled
>> tmpfs large folio allocation by adding the 
>> 'transparent_hugepage_tmpfs=always'
>> cmdline. However, the test case still expects the tmpfs mounted on 
>> /dev/shm to
>> allocate small folios, which leads to assertion failures when 
>> verifying readahead
>> pages.
>>
>> As discussed with David, there's no reason to continue checking the 
>> readahead
>> logic for tmpfs. Drop it to fix this issue.
>>
> 
> BTW, should we add a Fixes: ? Could only be tmpfs support that changed 
> the behavior but didn't fixup the test case.

I was hesitant about whether a Fixes tag is needed, because this issue 
can be traced back to the earliest patch set that added THP support to 
tmpfs. However, the test issue wasn't exposed because the 'huge=' 
parameter wasn't included when mounting /dev/shm.

After the cmdline 'transparent_hugepage_tmpfs' was added for tmpfs, the 
issue is exposed easily. So I am inclined to add a Fixes tag for the 
patch added the 'transparent_hugepage_tmpfs' cmdline.

Fixes: d635ccdb435c ("mm: shmem: add a kernel command line to change the 
default huge policy for tmpfs")

>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>> ---
>> Changes from v1:
>>   - Drop the readahead logic check, per David.
>> ---
>>   .../testing/selftests/mincore/mincore_selftest.c | 16 ++--------------
>>   1 file changed, 2 insertions(+), 14 deletions(-)
>>
>> diff --git a/tools/testing/selftests/mincore/mincore_selftest.c 
>> b/tools/testing/selftests/mincore/mincore_selftest.c
>> index e949a43a6145..0fd4b00bd345 100644
>> --- a/tools/testing/selftests/mincore/mincore_selftest.c
>> +++ b/tools/testing/selftests/mincore/mincore_selftest.c
>> @@ -286,8 +286,7 @@ TEST(check_file_mmap)
>>   /*
>>    * Test mincore() behavior on a page backed by a tmpfs file.  This test
>> - * performs the same steps as the previous one. However, we don't expect
>> - * any readahead in this case.
>> + * performs the same steps as the previous one.
>>    */
>>   TEST(check_tmpfs_mmap)
>>   {
>> @@ -298,7 +297,6 @@ TEST(check_tmpfs_mmap)
>>       int page_size;
>>       int fd;
>>       int i;
>> -    int ra_pages = 0;
>>       page_size = sysconf(_SC_PAGESIZE);
>>       vec_size = FILE_SIZE / page_size;
>> @@ -341,8 +339,7 @@ TEST(check_tmpfs_mmap)
>>       }
>>       /*
>> -     * Touch a page in the middle of the mapping. We expect only
>> -     * that page to be fetched into memory.
>> +     * Touch a page in the middle of the mapping.
>>        */
>>       addr[FILE_SIZE / 2] = 1;
>>       retval = mincore(addr, FILE_SIZE, vec);
>> @@ -351,15 +348,6 @@ TEST(check_tmpfs_mmap)
>>           TH_LOG("Page not found in memory after use");
>>       }
>> -    i = FILE_SIZE / 2 / page_size + 1;
>> -    while (i < vec_size && vec[i]) {
>> -        ra_pages++;
>> -        i++;
>> -    }
>> -    ASSERT_EQ(ra_pages, 0) {
>> -        TH_LOG("Read-ahead pages found in memory");
>> -    }
>> -
>>       munmap(addr, FILE_SIZE);
>>       close(fd);
>>       free(vec);
> 
> Acked-by: David Hildenbrand <david@redhat.com>

Thanks.


      reply	other threads:[~2025-04-08  8:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 11:31 Baolin Wang
2025-04-07 14:24 ` Zi Yan
2025-04-07 15:04 ` David Hildenbrand
2025-04-08  8:11   ` Baolin Wang [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=f0026429-de3e-4e20-8603-39683180a643@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.com \
    --cc=willy@infradead.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