From: Mike Rapoport <rppt@kernel.org>
To: Chunyu Hu <chuhu@redhat.com>
Cc: akpm@linux-foundation.org, david@kernel.org, shuah@kernel.org,
linux-mm@kvack.org, ljs@kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
vbabka@suse.cz, surenb@google.com, mhocko@suse.com,
ziy@nvidia.com, baolin.wang@linux.alibaba.com, npache@redhat.com,
ryan.roberts@arm.com, dev.jain@arm.com, baohua@kernel.org,
lance.yang@linux.dev
Subject: Re: [PATCH v6 4/6] selftests/mm/vm_util: robust write_file()
Date: Fri, 27 Mar 2026 15:32:01 +0300 [thread overview]
Message-ID: <acZ4wTxSmPn_s_mn@kernel.org> (raw)
In-Reply-To: <20260324013316.2590422-5-chuhu@redhat.com>
On Tue, Mar 24, 2026 at 09:33:14AM +0800, Chunyu Hu wrote:
> Add two more checks for buflen and numwritten. The buflen should be at
> least one, otherwise the 'buflen - 1' could underflow and cause trouble.
> The numwritten should be equal to 'buflen - 1'. The test will exit if
> any of these conditions aren't met.
>
> Additionally, add more print information when a write failure occurs or
> a truncated write happens, providing clearer diagnostics.
>
> Signed-off-by: Chunyu Hu <chuhu@redhat.com>
> ---
> Changes in v6:
> - save/restore errno before and after the close(), so the log could show
> the correct error info on failure. Suggested by AI.
> Chagnes in v5:
> - new patch for making improve on write_file. Add more safety checks and
> diagnostics info in log
> ---
> tools/testing/selftests/mm/vm_util.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/mm/vm_util.c b/tools/testing/selftests/mm/vm_util.c
> index ad96d19d1b85..572ccb99de8e 100644
> --- a/tools/testing/selftests/mm/vm_util.c
> +++ b/tools/testing/selftests/mm/vm_util.c
> @@ -767,15 +767,23 @@ int unpoison_memory(unsigned long pfn)
>
> void write_file(const char *path, const char *buf, size_t buflen)
> {
> - int fd;
> + int fd, saved_errno;
> ssize_t numwritten;
> + if (buflen < 1)
> + ksft_exit_fail_msg("Incorrect buffer len: %zu\n", buflen);
>
> fd = open(path, O_WRONLY);
> if (fd == -1)
> ksft_exit_fail_msg("%s open failed: %s\n", path, strerror(errno));
We have ksft_exit_fail_perror(), fits great here
>
> numwritten = write(fd, buf, buflen - 1);
> + saved_errno = errno;
> close(fd);
> + errno = saved_errno;
> if (numwritten < 1)
> - ksft_exit_fail_msg("Write failed\n");
> + ksft_exit_fail_msg("%s write(%s) failed: %s\n", path, buf,
> + strerror(errno));
and here.
> + if (numwritten != buflen - 1)
> + ksft_exit_fail_msg("%s write(%s) is truncated, expected %zu bytes, got %zd bytes\n",
> + path, buf, buflen - 1, numwritten);
> }
> --
> 2.53.0
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-03-27 12:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 1:33 [PATCH v6 0/6] selftests/mm: skip several tests when thp is not available Chunyu Hu
2026-03-24 1:33 ` [PATCH v6 1/6] selftests/mm/guard-regions: skip collapse test when thp not enabled Chunyu Hu
2026-03-27 7:43 ` Lorenzo Stoakes (Oracle)
2026-03-24 1:33 ` [PATCH v6 2/6] selftests/mm: soft-dirty: skip two tests when thp is not available Chunyu Hu
2026-03-24 1:33 ` [PATCH v6 3/6] selftests/mm: move write_file helper to vm_util Chunyu Hu
2026-03-24 1:33 ` [PATCH v6 4/6] selftests/mm/vm_util: robust write_file() Chunyu Hu
2026-03-27 6:03 ` Andrew Morton
2026-03-27 7:46 ` Lorenzo Stoakes (Oracle)
2026-03-27 12:32 ` Mike Rapoport [this message]
2026-03-24 1:33 ` [PATCH v6 5/6] selftests/mm: split_huge_page_test: skip the test when thp is not available Chunyu Hu
2026-03-24 1:33 ` [PATCH v6 6/6] selftests/mm: transhuge_stress: skip the test when thp " Chunyu Hu
2026-03-24 16:09 ` [PATCH v6 0/6] selftests/mm: skip several tests when thp is " Andrew Morton
2026-03-27 13:24 ` David Hildenbrand (Arm)
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=acZ4wTxSmPn_s_mn@kernel.org \
--to=rppt@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chuhu@redhat.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--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