From: Avinesh Kumar <akumar@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] setfsuid02: using -1 as invalid fsuid for setfsuid()
Date: Thu, 27 Oct 2022 19:39:54 +0530 [thread overview]
Message-ID: <20221027140954.4094-1-akumar@suse.de> (raw)
a uid which does not have an entry in the /etc/passwd
file is not really an invalid fsuid for setfsuid(), so changing
the test to use -1 as an invalid fsuid.
And second setfsuid(-1) call is to verify that preceding call has
actually failed and there is no change in the fsuid.
Signed-off-by: Avinesh Kumar <akumar@suse.de>
---
testcases/kernel/syscalls/setfsuid/setfsuid02.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/testcases/kernel/syscalls/setfsuid/setfsuid02.c b/testcases/kernel/syscalls/setfsuid/setfsuid02.c
index 850f17834..f5aa1c004 100644
--- a/testcases/kernel/syscalls/setfsuid/setfsuid02.c
+++ b/testcases/kernel/syscalls/setfsuid/setfsuid02.c
@@ -21,9 +21,7 @@ static void run(void)
uid_t invalid_uid, current_uid;
current_uid = geteuid();
- invalid_uid = 1;
- while (getpwuid(invalid_uid))
- invalid_uid++;
+ invalid_uid = -1;
UID16_CHECK(invalid_uid, setfsuid);
--
2.38.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2022-10-27 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 14:09 Avinesh Kumar [this message]
2022-10-31 11:37 ` [LTP] [PATCH] setfsuid02: using -1 as invalid fsuid for setfsuid() Petr Vorel
2022-10-31 13:36 ` Martin Doucha
2022-10-31 13:50 ` Petr Vorel
2022-10-31 14:00 ` Martin Doucha
2022-10-31 14:56 ` Petr Vorel
2022-10-31 17:23 ` Martin Doucha
2022-10-31 21:39 ` Petr Vorel
2022-11-02 7:40 ` Avinesh Kumar
2022-10-31 13:01 ` Richard Palethorpe
2022-10-31 21:40 ` Petr Vorel
2022-11-01 9:03 ` Richard Palethorpe
2022-11-02 7:52 ` Avinesh Kumar
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=20221027140954.4094-1-akumar@suse.de \
--to=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;
as well as URLs for NNTP newsgroup(s).