From: Adam Sindelar <adam@wowsignal.io>
To: David Vernet <void@manifault.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Suren Baghdasaryan <surenb@google.com>,
linux-mm@kvack.org, Adam Sindelar <ats@fb.com>,
kernel-team@fb.com
Subject: Re: [PATCH v3] selftests/vm: fix errno handling in mrelease_test
Date: Wed, 6 Jul 2022 16:15:07 +0200 [thread overview]
Message-ID: <YsWY6y6SZmyk4mxd@vroom.lan> (raw)
In-Reply-To: <20220706134508.xiqkgdidg433tybh@dev0025.ash9.facebook.com>
On Wed, Jul 06, 2022 at 06:45:08AM -0700, David Vernet wrote:
> On Wed, Jul 06, 2022 at 11:57:07AM +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.
>
> As requested on the v2 version of the patch, please also include a "Fixes" line
> here (see [0]):
>
> Fixes: 33776141b812 ("selftests: vm: add process_mrelease tests")
>
> [0]: https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes
>
Done, sending shortly. Sorry, getting used to review over email.
> >
> > Signed-off-by: Adam Sindelar <adam@wowsignal.io>
> > ---
> > v1->v2: Fixed second instance in the same file
> > v2->v3: Fixed remaining instances of errno mishandling
> >
> > 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
>
> [...]
>
> Looks good otherwise, thanks.
>
> Reviewed-by: David Vernet <void@manifault.com>
next prev parent reply other threads:[~2022-07-06 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 9:57 Adam Sindelar
2022-07-06 13:45 ` David Vernet
2022-07-06 14:15 ` Adam Sindelar [this message]
2022-07-06 15:28 ` David Vernet
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=YsWY6y6SZmyk4mxd@vroom.lan \
--to=adam@wowsignal.io \
--cc=akpm@linux-foundation.org \
--cc=ats@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--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