From: xieziyao <xieziyao@huawei.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3] syscalls/chown: Rewrite chown/chown03.c with the new api
Date: Tue, 20 Apr 2021 06:28:34 +0000 [thread overview]
Message-ID: <176808ab097741f8922867d5eacae77c@huawei.com> (raw)
In-Reply-To: <60ae8451-30f5-9b82-dcdc-11b97e29099e@oracle.com>
Hi,
Thanks so much for your review!
I just re-checked the latest code and submit the v4 version based on your suggestions:
1. Move two similar owner checks to a single function;
2. Modify the incorrect code style.
Please see: https://patchwork.ozlabs.org/project/ltp/patch/20210420061954.155049-1-xieziyao@huawei.com/
Thanks very much!
Best Regards,
Ziyao
-----Original Message-----
From: Alexey Kodanev [mailto:alexey.kodanev@oracle.com]
Sent: Tuesday, April 20, 2021 12:09 AM
To: xieziyao <xieziyao@huawei.com>; ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] syscalls/chown: Rewrite chown/chown03.c with the new api
On 19.04.2021 04:34, Xie Ziyao wrote:
> For this:
> testcases/kernel/syscalls/chown/chown03.c
>
> Signed-off-by: Xie Ziyao <xieziyao@huawei.com>
> ---
> v2->v3:
> 1. Remove some unnecessary comments and incorrect output prints; 2.
> Moved some prerequisite codes from the setup() function to the run()
> function and add code logic for checking whether the setting is successful.
>
Hi Ziyao,
> testcases/kernel/syscalls/chown/chown03.c | 241
> +++++++---------------
> 1 file changed, 70 insertions(+), 171 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/chown/chown03.c
> b/testcases/kernel/syscalls/chown/chown03.c
> index 2c7bcfe7d..4469f1c4d 100644
> --- a/testcases/kernel/syscalls/chown/chown03.c
> +++ b/testcases/kernel/syscalls/chown/chown03.c
> @@ -1,72 +1,18 @@
...
> -int TST_TOTAL = 1; /* Total number of test conditions */
> -char nobody_uid[] = "nobody";
> struct passwd *ltpuser;
static struct passwd *ltpuser;
>
> -void setup(); /* setup function for the test */
> -void cleanup(); /* cleanup function for the test */
> -
> -int main(int ac, char **av)
> +static void run(void)
> {
...
> + SAFE_SETEUID(0);
> + SAFE_CHOWN(FILENAME, -1, 0);
> + SAFE_CHMOD(FILENAME, NEW_PERMS);
> + SAFE_SETEUID(ltpuser->pw_uid);
> +
> + uid_t uid;
> + gid_t gid;
> + UID16_CHECK((uid = geteuid()), "chown");
> + GID16_CHECK((gid = getegid()), "chown");
> +
> + struct stat stat_buf;
> + SAFE_STAT(FILENAME, &stat_buf);
> + if (stat_buf.st_uid != uid || stat_buf.st_gid != 0)
> + tst_res(TFAIL, "%s: Incorrect ownership"
> + "set to %d %d, Expected %d %d",
> + FILENAME, stat_buf.st_uid,
> + stat_buf.st_gid, uid, 0);
> +
> + TST_EXP_PASS(CHOWN(FILENAME, -1, gid), "chown(%s,%d,%d)",
> + FILENAME, -1, gid);
> +
> + SAFE_STAT(FILENAME, &stat_buf);
> + if (stat_buf.st_uid != uid || stat_buf.st_gid != gid)
> + tst_res(TFAIL, "%s: Incorrect ownership"
> + "set to %d %d, Expected %d %d",
> + FILENAME, stat_buf.st_uid,
> + stat_buf.st_gid, uid, gid);
There are two similar owner checks now, it would be better to move them to a single function, something like this:
static void check_owner(struct stat *s, uid_t exp_uid, gid_t exp_gid) {
if (s->st_uid != exp_uid || s->st_gid != exp_gid) {
tst_res(TFAIL, "%s: wrong owner set to %d %d, expected %d %d",
FILENAME, s->st_uid, s->st_gid, exp_uid, exp_gid);
} else {
tst_res(TPASS, "%s: expected owner set %d %d",
FILENAME, exp_uid, exp_gid);
}
}
next prev parent reply other threads:[~2021-04-20 6:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 1:34 [LTP] [PATCH v3] syscalls/chown: Rewrite chown/chown03.c with the new api Xie Ziyao
2021-04-19 14:55 ` Cyril Hrubis
2021-04-20 6:30 ` xieziyao
2021-04-19 16:09 ` Alexey Kodanev
2021-04-20 6:28 ` xieziyao [this message]
2021-04-20 6:19 ` [LTP] [PATCH v4] " Xie Ziyao
2021-04-21 11:58 ` Cyril Hrubis
2021-04-22 2:51 ` xieziyao
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=176808ab097741f8922867d5eacae77c@huawei.com \
--to=xieziyao@huawei.com \
--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