From: Wei Yang <richard.weiyang@gmail.com>
To: Vineet Agarwal <agarwal.vineet2006@gmail.com>
Cc: akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: check file initialization writes in split_huge_page_test
Date: Fri, 15 May 2026 09:22:11 +0000 [thread overview]
Message-ID: <20260515092211.qkmaxcofxwfdexld@master> (raw)
In-Reply-To: <20260512074924.27721-1-agarwal.vineet2006@gmail.com>
On Tue, May 12, 2026 at 01:19:24PM +0530, Vineet Agarwal wrote:
>create_pagecache_thp_and_fd() fills the backing file for the
>pagecache THP tests using repeated write() calls, but the return
>value is never checked.
>
>If a write fails or completes only partially, the test may continue
>with an incompletely initialized file and produce misleading results.
>
>Check the result of write() and fail the test if the expected number
>of bytes was not written.
>
>Signed-off-by: Vineet Agarwal <agarwal.vineet2006@gmail.com>
>---
> tools/testing/selftests/mm/split_huge_page_test.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
>diff --git a/tools/testing/selftests/mm/split_huge_page_test.c b/tools/testing/selftests/mm/split_huge_page_test.c
>index 500d07c4938b..eab69b0f59a0 100644
>--- a/tools/testing/selftests/mm/split_huge_page_test.c
>+++ b/tools/testing/selftests/mm/split_huge_page_test.c
>@@ -609,9 +609,16 @@ static int create_pagecache_thp_and_fd(const char *testfile, size_t fd_size,
> assert(fd_size % sizeof(buf) == 0);
> for (i = 0; i < sizeof(buf); i++)
> buf[i] = (unsigned char)i;
>- for (i = 0; i < fd_size; i += sizeof(buf))
>- write(*fd, buf, sizeof(buf));
>-
>+ for (i = 0; i < fd_size; i += sizeof(buf)) {
>+ ssize_t written;
>+
>+ written = write(*fd, buf, sizeof(buf));
>+ if (written != sizeof(buf)) {
>+ ksft_perror("write testfile");
>+ close(*fd);
>+ goto err_out_unlink;
Maybe we can "goto err_out_close" and remove the close() here?
Apart from this, I found on error writing to /proc/sys/vm/drop_caches in below,
it just goto err_out_unlink, which left fd open.
How about fix that at the same time.
Generally, the change look good.
>+ }
>+ }
> close(*fd);
> sync();
> *fd = open("/proc/sys/vm/drop_caches", O_WRONLY);
>--
>2.54.0
>
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2026-05-15 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 7:49 [PATCH] selftests/mm: check file initialization writes in split_huge_page_test Vineet Agarwal
2026-05-12 7:57 ` David Hildenbrand (Arm)
2026-05-15 9:22 ` Wei Yang [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=20260515092211.qkmaxcofxwfdexld@master \
--to=richard.weiyang@gmail.com \
--cc=agarwal.vineet2006@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
/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