From: Avinesh Kumar <akumar@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] setuid03.c: using TST_EXP_FAIL() and SAFE_SETUID() macros
Date: Thu, 11 Aug 2022 11:41:07 +0530 [thread overview]
Message-ID: <20220811061107.30966-1-akumar@suse.de> (raw)
use TST_EXP_FAIL() with expected errno code, use SAFE_SETUID() in setup
and turn comment into docparse
Signed-off-by: Avinesh Kumar <akumar@suse.de>
---
testcases/kernel/syscalls/setuid/setuid03.c | 21 ++++++---------------
1 file changed, 6 insertions(+), 15 deletions(-)
diff --git a/testcases/kernel/syscalls/setuid/setuid03.c b/testcases/kernel/syscalls/setuid/setuid03.c
index f2e007f8d..06934f142 100644
--- a/testcases/kernel/syscalls/setuid/setuid03.c
+++ b/testcases/kernel/syscalls/setuid/setuid03.c
@@ -1,9 +1,12 @@
// SPDX-License-Identifier: GPL-2.0-or-later
/*
* Copyright (c) International Business Machines Corp., 2001
+ * Copyright (c) Linux Test Project, 2009-2022
*/
-/* DESCRIPTION
+/*\
+ * [Description]
+ *
* This test will switch to nobody user for correct error code collection.
* Verify setuid returns errno EPERM when it switches to root_user.
*/
@@ -19,16 +22,7 @@
static void verify_setuid(void)
{
- TEST(SETUID(ROOT_USER));
- if (TST_RET != -1) {
- tst_res(TFAIL | TTERRNO, "setuid() succeeded unexpectedly");
- return;
- }
-
- if (TST_ERR == EPERM)
- tst_res(TPASS, "setuid() returned errno EPERM");
- else
- tst_res(TFAIL | TTERRNO, "setuid() returned unexpected errno");
+ TST_EXP_FAIL(SETUID(ROOT_USER), EPERM);
}
static void setup(void)
@@ -39,10 +33,7 @@ static void setup(void)
pw = SAFE_GETPWNAM("nobody");
uid = pw->pw_uid;
- if (SETUID(uid) == -1) {
- tst_brk(TBROK,
- "setuid() failed to set the effective uid to %d", uid);
- }
+ SAFE_SETUID(uid);
umask(0);
}
--
2.36.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2022-08-11 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 6:11 Avinesh Kumar [this message]
2022-10-11 11:26 ` [LTP] [PATCH v2] setuid03.c: using TST_EXP_FAIL() and SAFE_SETUID() macros Richard Palethorpe
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=20220811061107.30966-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