From: Richard Palethorpe <rpalethorpe@suse.de>
To: Avinesh Kumar <akumar@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] setreuid01: Use SETREUID() instead of setreuid() to check 32bit syscall
Date: Tue, 10 Jan 2023 14:20:14 +0000 [thread overview]
Message-ID: <87mt6qh3oc.fsf@suse.de> (raw)
In-Reply-To: <20230110130711.29274-1-akumar@suse.de>
Hello,
Merged, thanks!
Avinesh Kumar <akumar@suse.de> writes:
> Signed-off-by: Avinesh Kumar <akumar@suse.de>
> ---
> testcases/kernel/syscalls/setreuid/setreuid01.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/setreuid/setreuid01.c b/testcases/kernel/syscalls/setreuid/setreuid01.c
> index bbf29d360..7c2b6d589 100644
> --- a/testcases/kernel/syscalls/setreuid/setreuid01.c
> +++ b/testcases/kernel/syscalls/setreuid/setreuid01.c
> @@ -26,13 +26,13 @@ static void run(void)
> euid = geteuid();
> UID16_CHECK(euid, setreuid);
>
> - TST_EXP_PASS(setreuid(-1, -1));
> - TST_EXP_PASS(setreuid(-1, euid));
> - TST_EXP_PASS(setreuid(ruid, -1));
> - TST_EXP_PASS(setreuid(-1, ruid));
> - TST_EXP_PASS(setreuid(euid, -1));
> - TST_EXP_PASS(setreuid(euid, euid));
> - TST_EXP_PASS(setreuid(ruid, ruid));
> + TST_EXP_PASS(SETREUID(-1, -1));
> + TST_EXP_PASS(SETREUID(-1, euid));
> + TST_EXP_PASS(SETREUID(ruid, -1));
> + TST_EXP_PASS(SETREUID(-1, ruid));
> + TST_EXP_PASS(SETREUID(euid, -1));
> + TST_EXP_PASS(SETREUID(euid, euid));
> + TST_EXP_PASS(SETREUID(ruid, ruid));
> }
>
> static struct tst_test test = {
> --
> 2.39.0
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2023-01-10 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 13:07 [LTP] [PATCH] setreuid01: Use SETREUID() instead of setreuid() to check 32bit syscall Avinesh Kumar
2023-01-10 14:20 ` Richard Palethorpe [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=87mt6qh3oc.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=akumar@suse.de \
--cc=ltp@lists.linux.it \
/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