From: Chunyu Hu <chuhu@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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, rppt@kernel.org,
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 v5 4/6] selftests/mm/vm_util: robust write_file()
Date: Tue, 24 Mar 2026 08:18:24 +0800 [thread overview]
Message-ID: <acHYUE1rn5TYyxgR@gmail.com> (raw)
In-Reply-To: <20260323153941.289938dd9ced4dbb76ca7804@linux-foundation.org>
On Mon, Mar 23, 2026 at 03:39:41PM -0700, Andrew Morton wrote:
> On Mon, 23 Mar 2026 23:17:51 +0800 Chunyu Hu <chuhu@redhat.com> 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.
> >
> > ...
> >
> > --- a/tools/testing/selftests/mm/vm_util.c
> > +++ b/tools/testing/selftests/mm/vm_util.c
> > @@ -769,6 +769,8 @@ void write_file(const char *path, const char *buf, size_t buflen)
> > {
> > int fd;
> > ssize_t numwritten;
> > + if (buflen < 1)
> > + ksft_exit_fail_msg("Incorrect buffer len: %zu\n", buflen);
> >
> > fd = open(path, O_WRONLY);
> > if (fd == -1)
> > @@ -777,5 +779,9 @@ void write_file(const char *path, const char *buf, size_t buflen)
> > numwritten = write(fd, buf, buflen - 1);
> > close(fd);
> > if (numwritten < 1)
> > - ksft_exit_fail_msg("Write failed\n");
> > + ksft_exit_fail_msg("%s write(%s) failed: %s\n", path, buf,
> > + strerror(errno));
>
> AI review
> (https://sashiko.dev/#/patchset/20260323151753.2576137-1-chuhu@redhat.com)
> points out that `errno' was overwritten by the close(). Maybe. Or
> maybe a successful close() leaves errno alone, dunno.
I'll address this errno part by adding a save and restore before/after
the close().
>
> Apart from that the comments appear fairly minor. Please lmk if you
> think we should proceed as-is.
For the other two minor questions about buflen == 1 and non-null
buffer, user should know a string buffer need to be '\0' ended.
Those are really minor, we can leave as it is.
AI's comment on patch 5 should be other topic, and minor. Let's
leave as it it.
>
> (I'm really trying to slow things down now - we have a *lot* of
> material and a few weeks of consolidation is needed. But selftests/
> tend to get a pass, for obvious reasons)
>
next prev parent reply other threads:[~2026-03-24 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 15:17 [PATCH v5 0/6] selftests/mm: skip several tests when thp is not available Chunyu Hu
2026-03-23 15:17 ` [PATCH v5 1/6] selftests/mm/guard-regions: skip collapse test when thp not enabled Chunyu Hu
2026-03-23 15:17 ` [PATCH v5 2/6] selftests/mm: soft-dirty: skip two tests when thp is not available Chunyu Hu
2026-03-23 15:17 ` [PATCH v5 3/6] selftests/mm: move write_file helper to vm_util Chunyu Hu
2026-03-23 15:48 ` Lorenzo Stoakes (Oracle)
2026-03-24 0:23 ` Chunyu Hu
2026-03-23 15:17 ` [PATCH v5 4/6] selftests/mm/vm_util: robust write_file() Chunyu Hu
2026-03-23 22:39 ` Andrew Morton
2026-03-24 0:18 ` Chunyu Hu [this message]
2026-03-23 15:17 ` [PATCH v5 5/6] selftests/mm: split_huge_page_test: skip the test when thp is not available Chunyu Hu
2026-03-23 15:17 ` [PATCH v5 6/6] selftests/mm: transhuge_stress: skip the test when thp " Chunyu Hu
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=acHYUE1rn5TYyxgR@gmail.com \
--to=chuhu@redhat.com \
--cc=Liam.Howlett@oracle.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=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=rppt@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.