linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: David Vernet <void@manifault.com>
Cc: Adam Sindelar <adam@wowsignal.io>,
	Andrew Morton <akpm@linux-foundation.org>,
	 linux-mm <linux-mm@kvack.org>, Adam Sindelar <ats@fb.com>,
	kernel-team@fb.com
Subject: Re: [PATCH v4] selftests/vm: fix errno handling in mrelease_test
Date: Wed, 6 Jul 2022 09:41:54 -0700	[thread overview]
Message-ID: <CAJuCfpGfyeWV3pcWNkSLfM_0AwjtUVKyXF-8JtYW4r0r3JVXUg@mail.gmail.com> (raw)
In-Reply-To: <20220706152937.j3ejwofwofnsgsxs@dev0025.ash9.facebook.com>

On Wed, Jul 6, 2022 at 8:29 AM David Vernet <void@manifault.com> wrote:
>
> On Wed, Jul 06, 2022 at 04:16:02PM +0200, Adam Sindelar wrote:
> > mrelease_test should return KSFT_SKIP when process_mrelease is not
> > defined, but due to a perror call consuming the errno, it returns
> > KSFT_FAIL.
> >
> > This patch decides the exit codes before calling perror.
> >
> > Fixes: 33776141b812 ("selftests: vm: add process_mrelease tests")
> >
> > Signed-off-by: Adam Sindelar <adam@wowsignal.io>

Reviewed-by: Suren Baghdasaryan <surenb@google.com>

> > ---
> > v1->v2: Fixed second instance in the same file
> > v2->v3: Fixed remaining instances of errno mishandling
> > v3->v4: Added a "Fixes:" line for the log
> >
> >  tools/testing/selftests/vm/mrelease_test.c | 16 +++++++++++-----
> >  1 file changed, 11 insertions(+), 5 deletions(-)
> >
> > diff --git a/tools/testing/selftests/vm/mrelease_test.c b/tools/testing/selftests/vm/mrelease_test.c
> > index 96671c2f7d48..6c62966ab5db 100644
> > --- a/tools/testing/selftests/vm/mrelease_test.c
> > +++ b/tools/testing/selftests/vm/mrelease_test.c
> > @@ -62,19 +62,22 @@ static int alloc_noexit(unsigned long nr_pages, int pipefd)
> >  /* The process_mrelease calls in this test are expected to fail */
> >  static void run_negative_tests(int pidfd)
> >  {
> > +     int res;
> >       /* Test invalid flags. Expect to fail with EINVAL error code. */
> >       if (!syscall(__NR_process_mrelease, pidfd, (unsigned int)-1) ||
> >                       errno != EINVAL) {
> > +             res = (errno == ENOSYS ? KSFT_SKIP : KSFT_FAIL);
> >               perror("process_mrelease with wrong flags");
> > -             exit(errno == ENOSYS ? KSFT_SKIP : KSFT_FAIL);
> > +             exit(res);
> >       }
> >       /*
> >        * Test reaping while process is alive with no pending SIGKILL.
> >        * Expect to fail with EINVAL error code.
> >        */
> >       if (!syscall(__NR_process_mrelease, pidfd, 0) || errno != EINVAL) {
> > +             res = (errno == ENOSYS ? KSFT_SKIP : KSFT_FAIL);
> >               perror("process_mrelease on a live process");
> > -             exit(errno == ENOSYS ? KSFT_SKIP : KSFT_FAIL);
> > +             exit(res);
> >       }
> >  }
> >
> > @@ -100,8 +103,9 @@ int main(void)
> >
> >       /* Test a wrong pidfd */
> >       if (!syscall(__NR_process_mrelease, -1, 0) || errno != EBADF) {
> > +             res = (errno == ENOSYS ? KSFT_SKIP : KSFT_FAIL);
> >               perror("process_mrelease with wrong pidfd");
> > -             exit(errno == ENOSYS ? KSFT_SKIP : KSFT_FAIL);
> > +             exit(res);
> >       }
> >
> >       /* Start the test with 1MB child memory allocation */
> > @@ -156,8 +160,9 @@ int main(void)
> >       run_negative_tests(pidfd);
> >
> >       if (kill(pid, SIGKILL)) {
> > +             res = (errno == ENOSYS ? KSFT_SKIP : KSFT_FAIL);
> >               perror("kill");
> > -             exit(errno == ENOSYS ? KSFT_SKIP : KSFT_FAIL);
> > +             exit(res);
> >       }
> >
> >       success = (syscall(__NR_process_mrelease, pidfd, 0) == 0);
> > @@ -172,9 +177,10 @@ int main(void)
> >               if (errno == ESRCH) {
> >                       retry = (size <= MAX_SIZE_MB);
> >               } else {
> > +                     res = (errno == ENOSYS ? KSFT_SKIP : KSFT_FAIL);
> >                       perror("process_mrelease");
> >                       waitpid(pid, NULL, 0);
> > -                     exit(errno == ENOSYS ? KSFT_SKIP : KSFT_FAIL);
> > +                     exit(res);
> >               }
> >       }
> >
> > --
> > 2.35.1
> >
>
> Thanks, Adam. Looks great.
>
> Reviewed-by: David Vernet <void@manifault.com>

Thanks for the fix!


      reply	other threads:[~2022-07-06 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 14:16 Adam Sindelar
2022-07-06 15:29 ` David Vernet
2022-07-06 16:41   ` Suren Baghdasaryan [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=CAJuCfpGfyeWV3pcWNkSLfM_0AwjtUVKyXF-8JtYW4r0r3JVXUg@mail.gmail.com \
    --to=surenb@google.com \
    --cc=adam@wowsignal.io \
    --cc=akpm@linux-foundation.org \
    --cc=ats@fb.com \
    --cc=kernel-team@fb.com \
    --cc=linux-mm@kvack.org \
    --cc=void@manifault.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