From: Petr Vorel <pvorel@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4] clone3: Add clone3's clone_args cgroup
Date: Wed, 17 May 2023 11:28:23 +0200 [thread overview]
Message-ID: <20230517092823.GA19852@pevik> (raw)
In-Reply-To: <20230509003148.16094-1-wegao@suse.com>
Hi Wei,
...
> +++ b/include/tst_cgroup.h
> @@ -157,6 +157,9 @@ const char *
> tst_cg_group_name(const struct tst_cg_group *const cg)
> __attribute__ ((nonnull, warn_unused_result));
Maybe to add a comment to describe the function? (other functions have a
description).
> +int tst_cg_group_unified_dir_fd(const struct tst_cg_group *const cg)
> + __attribute__ ((nonnull, warn_unused_result));
> +
> /* Remove a descendant CGroup */
> struct tst_cg_group *
> tst_cg_group_rm(struct tst_cg_group *const cg)
> diff --git a/include/tst_clone.h b/include/tst_clone.h
> index 9ffdc68d1..7b278dfa7 100644
> --- a/include/tst_clone.h
> +++ b/include/tst_clone.h
> @@ -11,6 +11,7 @@
> struct tst_clone_args {
> uint64_t flags;
> uint64_t exit_signal;
> + uint64_t cgroup;
> };
...
> +++ b/testcases/kernel/syscalls/clone3/clone303.c
...
> +
> +static void run(void)
> +{
> + pid_t pid;
> +
> + pid = clone_into_cgroup(fd);
> +
> + if (!pid) {
> + TST_CHECKPOINT_WAIT(0);
> + return;
> + }
> +
> + char buf[BUF_LEN];
> +
> + SAFE_CG_READ(cg_child_test_simple, "cgroup.procs", buf, BUF_LEN);
> +
> + int x = atoi(buf);
> +
> + if (x == pid)
x is using only here. Why not just:
if (atoi(buf) == pid)
> + tst_res(TPASS, "clone3 case pass!");
> + else
> + tst_brk(TFAIL | TTERRNO, "clone3() failed !");
> +
> + TST_CHECKPOINT_WAKE(0);
> +
> + SAFE_WAITPID(pid, NULL, 0);
> +
> +}
> +
> +static void setup(void)
> +{
> + clone3_supported_by_kernel();
> +
> + cg_child_test_simple = tst_cg_group_mk(tst_cg, "cg_test_simple");
> +
> + fd = tst_cg_group_unified_dir_fd(cg_child_test_simple);
> +
> + if (fd < 0)
> + tst_res(TFAIL | TTERRNO, "get dir fd failed !");
Wouldn't be better to use here
tst_brk(TBROK | TTERRNO, "get dir fd failed!");
Or even just
tst_brk(TBROK, "get dir fd failed!");
Because tst_cg_group_unified_dir_fd() does not do any real operation which would
set errno.
I mean does make sense to continue testing if fd is invalid?
> +}
...
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-05-17 7:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 0:35 [LTP] [PATCH v1] clone3: Add clone3's clone_args cgroup Wei Gao via ltp
2023-03-23 9:26 ` Petr Vorel
2023-03-23 12:17 ` Wei Gao via ltp
2023-03-24 6:32 ` Petr Vorel
2023-03-24 6:54 ` Wei Gao via ltp
2023-03-24 8:26 ` Petr Vorel
2023-04-21 12:38 ` [LTP] [PATCH v2] " Wei Gao via ltp
2023-04-21 13:29 ` Cyril Hrubis
2023-04-22 1:42 ` [LTP] [PATCH v3] " Wei Gao via ltp
2023-04-26 13:44 ` Cyril Hrubis
2023-05-09 0:31 ` [LTP] [PATCH v4] " Wei Gao via ltp
2023-05-17 9:28 ` Petr Vorel [this message]
2023-05-17 12:08 ` [LTP] [PATCH v5] " Wei Gao via ltp
2023-08-25 10:36 ` Richard Palethorpe
2023-08-29 23:26 ` Wei Gao via ltp
2023-08-30 8:02 ` Richard Palethorpe
2023-08-29 23:18 ` [LTP] [PATCH v6] " Wei Gao via ltp
2023-08-31 6:47 ` [LTP] [PATCH v7] " Wei Gao via ltp
2023-08-31 9:19 ` Richard Palethorpe
2023-09-01 10:19 ` Petr Vorel
2023-09-01 10:22 ` Petr Vorel
2023-09-02 5:05 ` Wei Gao via ltp
2024-04-04 20:42 ` Petr Vorel
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=20230517092823.GA19852@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=wegao@suse.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