From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Cc: rpalethorpe@suse.com, luke.nowakowskikrijger@canonical.com
Subject: [LTP] [PATCH] lib: rewrite cgroup_find_ctrl with using for_each_ctrl
Date: Thu, 13 Jan 2022 20:34:18 +0800 [thread overview]
Message-ID: <20220113123418.1911231-1-liwang@redhat.com> (raw)
It is safe to start from controllers[0] to traverse each of
the controller whatever V2 or V1, then we can make use of it
in the cgroup_find_ctrl() function.
Signed-off-by: Li Wang <liwang@redhat.com>
---
lib/tst_cgroup.c | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/lib/tst_cgroup.c b/lib/tst_cgroup.c
index 2ef599d9e..10b65364b 100644
--- a/lib/tst_cgroup.c
+++ b/lib/tst_cgroup.c
@@ -214,7 +214,7 @@ static const char *cgroup_v2_ltp_mount = "unified";
#define for_each_v1_root(r) \
for ((r) = roots + 1; (r)->ver; (r)++)
#define for_each_ctrl(ctrl) \
- for ((ctrl) = controllers + 1; (ctrl)->ctrl_name; (ctrl)++)
+ for ((ctrl) = controllers; (ctrl)->ctrl_name; (ctrl)++)
/* In all cases except one, this only loops once.
*
@@ -325,15 +325,14 @@ void tst_cgroup_print_config(void)
__attribute__ ((nonnull, warn_unused_result))
static struct cgroup_ctrl *cgroup_find_ctrl(const char *const ctrl_name)
{
- struct cgroup_ctrl *ctrl = controllers;
-
- while (ctrl->ctrl_name && strcmp(ctrl_name, ctrl->ctrl_name))
- ctrl++;
+ struct cgroup_ctrl *ctrl;
- if (!ctrl->ctrl_name)
- ctrl = NULL;
+ for_each_ctrl(ctrl) {
+ if (!strcmp(ctrl_name, ctrl->ctrl_name))
+ return ctrl;
+ }
- return ctrl;
+ return NULL;
}
/* Determine if a mounted cgroup hierarchy is unique and record it if so.
--
2.31.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2022-01-13 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 12:34 Li Wang [this message]
2022-01-17 9:05 ` [LTP] [PATCH] lib: rewrite cgroup_find_ctrl with using for_each_ctrl Richard Palethorpe
2022-01-18 9:02 ` Li Wang
2022-01-21 5:23 ` Petr Vorel
2022-01-24 0:28 ` Li Wang
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=20220113123418.1911231-1-liwang@redhat.com \
--to=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=luke.nowakowskikrijger@canonical.com \
--cc=rpalethorpe@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