linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Li Wang <liwang@redhat.com>
Cc: David Laight <david.laight.linux@gmail.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, David Hildenbrand <david@kernel.org>,
	Mark Brown <broonie@kernel.org>, Shuah Khan <shuah@kernel.org>,
	Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v3 1/3] selftests/mm/write_to_hugetlbfs: parse -s as size_t
Date: Mon, 22 Dec 2025 18:05:09 -0800	[thread overview]
Message-ID: <20251222180509.b12684e112195ac3f7ee9389@linux-foundation.org> (raw)
In-Reply-To: <CAEemH2fsAmhAkGAQb9rtD2WLUc7QMb9Q5dusG3S8LsJbNKsO_Q@mail.gmail.com>

On Mon, 22 Dec 2025 18:56:49 +0800 Li Wang <liwang@redhat.com> wrote:

> > It reality scanf() is 'not the function you are lookign for'.
> >
> > IIRC the 'SUS' (used to) say that this was absolutely fine for command
> > line parsing for 'standard utilities'.
> >
> > It is best to use strtoul() and check the 'end' character is '\0'.
> 
> Hmm, that sounds like we need to go back to the patch V1 [1] method.
> But I am not sure, @Andrew Morton, do you think so?
> 
> --- a/tools/testing/selftests/mm/write_to_hugetlbfs.c
> +++ b/tools/testing/selftests/mm/write_to_hugetlbfs.c
> @@ -86,10 +86,17 @@ int main(int argc, char **argv)
>         while ((c = getopt(argc, argv, "s:p:m:owlrn")) != -1) {
>                 switch (c) {
>                 case 's':
> -                       if (sscanf(optarg, "%zu", &size) != 1) {
> -                               perror("Invalid -s.");
> +                       char *end = NULL;
> +                       unsigned long tmp = strtoul(optarg, &end, 10);
> +                       if (errno || end == optarg || *end != '\0') {
> +                               perror("Invalid -s size");
>                                 exit_usage();
>                         }
> +                       if (tmp == 0) {
> +                               perror("size not found");
> +                               exit_usage();
> +                       }
> +                       size = (size_t)tmp;
>                         break;
>                 case 'p':

Geeze guys, it's just a selftest.

hp2:/usr/src/linux-6.19-rc1> grep -r scanf tools/testing/selftests | wc -l 
177

if your command line breaks the selftest, fix your command line?


  reply	other threads:[~2025-12-23  2:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-21 12:26 [PATCH v3 0/3] selftests/mm: hugetlb cgroup charging: robustness fixes Li Wang
2025-12-21 12:26 ` [PATCH v3 1/3] selftests/mm/write_to_hugetlbfs: parse -s as size_t Li Wang
2025-12-21 20:23   ` Waiman Long
2025-12-21 22:10   ` David Laight
2025-12-22  1:45     ` Li Wang
2025-12-22  9:48       ` David Laight
2025-12-22 10:56         ` Li Wang
2025-12-23  2:05           ` Andrew Morton [this message]
2025-12-23  2:41             ` Li Wang
2025-12-23  8:40               ` David Laight
2025-12-23  9:29                 ` Li Wang
2025-12-23 12:11                   ` David Laight
2025-12-21 12:26 ` [PATCH v3 2/3] selftests/mm/charge_reserved_hugetlb: drop mount size for hugetlbfs Li Wang
2025-12-21 20:24   ` Waiman Long
2025-12-22 10:01   ` David Hildenbrand (Red Hat)
2025-12-22 19:08     ` Andrew Morton
2025-12-21 12:26 ` [PATCH v3 3/3] selftests/mm/charge_reserved_hugetlb.sh: add waits with timeout helper Li Wang
2025-12-21 20:30   ` Waiman Long
2025-12-22  0:56     ` Li Wang
2025-12-22  3:54       ` Waiman Long
2025-12-22 10:06   ` David Hildenbrand (Red Hat)

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=20251222180509.b12684e112195ac3f7ee9389@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=david.laight.linux@gmail.com \
    --cc=david@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liwang@redhat.com \
    --cc=longman@redhat.com \
    --cc=shuah@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