From: Shuah Khan <skhan@linuxfoundation.org>
To: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>,
"shuah@kernel.org" <shuah@kernel.org>
Cc: "linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Lai, Yi1" <yi1.lai@intel.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 1/1] selftests/mincore: Allow read-ahead pages to reach the end of the file
Date: Tue, 8 Apr 2025 17:11:18 -0600 [thread overview]
Message-ID: <f9a861ca-754b-41e7-a6dd-16d77958ab51@linuxfoundation.org> (raw)
In-Reply-To: <CY8PR11MB7134D020E20B290625057A4089B52@CY8PR11MB7134.namprd11.prod.outlook.com>
On 4/7/25 20:42, Zhuo, Qiuxu wrote:
> Hi Shuah Khan,
>
> Just a gentle ping regarding this patch.
> If you have any questions, please feel free to let me know.
>
> Thanks!
> -Qiuxu
>
>> From: Zhuo, Qiuxu <qiuxu.zhuo@intel.com>
>> [...]
>> Subject: [PATCH 1/1] selftests/mincore: Allow read-ahead pages to reach the
>> end of the file
>>
>> When running the mincore_selftest on a system with an XFS file system, it
>> failed the "check_file_mmap" test case due to the read-ahead pages reaching
>> the end of the file. The failure log is as below:
>>
>> RUN global.check_file_mmap ...
>> mincore_selftest.c:264:check_file_mmap:Expected i (1024) < vec_size (1024)
>> mincore_selftest.c:265:check_file_mmap:Read-ahead pages reached the
>> end of the file
>> check_file_mmap: Test failed
>> FAIL global.check_file_mmap
>>
>> This is because the read-ahead window size of the XFS file system on this
>> machine is 4 MB, which is larger than the size from the #PF address to the end
>> of the file. As a result, all the pages for this file are populated.
>>
>> blockdev --getra /dev/nvme0n1p5
>> 8192
>> blockdev --getbsz /dev/nvme0n1p5
>> 512
>>
>> This issue can be fixed by extending the current FILE_SIZE 4MB to a larger
>> number, but it will still fail if the read-ahead window size of the file system is
>> larger enough. Additionally, in the real world, read-ahead pages reaching the
>> end of the file can happen and is an expected behavior.
>> Therefore, allowing read-ahead pages to reach the end of the file is a better
>> choice for the "check_file_mmap" test case.
>>
>> Reported-by: Yi Lai <yi1.lai@intel.com>
>> Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
>> ---
Applied for Linux 6.15-rc2
https://web.git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=fixes
thanks,
-- Shuah
next prev parent reply other threads:[~2025-04-08 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 8:09 Qiuxu Zhuo
2025-04-08 2:42 ` Zhuo, Qiuxu
2025-04-08 23:11 ` Shuah Khan [this message]
2025-04-09 2:44 ` Zhuo, Qiuxu
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=f9a861ca-754b-41e7-a6dd-16d77958ab51@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=shuah@kernel.org \
--cc=yi1.lai@intel.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®