From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: "Michal Koutný" <mkoutny@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] memcg/memcontrol04: Fix judgment for recursive_protection
Date: Wed, 15 Jan 2025 13:17:44 +0100 [thread overview]
Message-ID: <20250115121744.GA648257@pevik> (raw)
In-Reply-To: <CAEemH2eMPDjSf0ShgsQc-4=Pg5M_9z6HnUMJRDM8OONkydDndg@mail.gmail.com>
Hi Li, Jin Guojie all,
> On Wed, Jan 15, 2025 at 2:33 PM Jin Guojie <guojie.jin@gmail.com> wrote:
Jin Guojie, thanks for handling this!
> > V3:
> > * Fix initialization of root->memory_recursiveprot
> > * The use of tst_cg_memory_recursiveprot(leaf_cg[F]) is changed to safe
> > check
> > * The type of memory_recursiveprot is changed to unsigned int
> > * Rebase the code to the latest branch
nit: if you add notes like version changelog (or other notes which should not be
part of the final commit message) below --- (above of the list of changed
files) we will see them in ML, but it will not be in git commit message.
> Thanks for refining this, code looks good to me, but as I pointed out
> can you rebase the patch on the latest branch? Otherwise, maintainer
> gets a conflict when applying your patch.
> Reviewed-by: Li Wang <liwang@redhat.com>
Acked-by: Petr Vorel <pvorel@suse.cz>
I also updated patchwork states for all versions of this.
> @Cyril, @Petr, I vote to merge this one before the release, and I also think
+1
> we need an additional tiny fix like below:
+1, Li, could you please send a regular patch for it?
Kind regards,
Petr
> --- a/lib/tst_cgroup.c
> +++ b/lib/tst_cgroup.c
> @@ -44,7 +44,7 @@ struct cgroup_dir {
> */
> int dir_fd;
> - int we_created_it:1;
> + unsigned int we_created_it:1;
> };
> /* The root of a CGroup hierarchy/tree */
> @@ -71,12 +71,12 @@ struct cgroup_root {
> /* CGroup for current test. Which may have children. */
> struct cgroup_dir test_dir;
> - int nsdelegate:1;
> - int memory_recursiveprot:1;
> + unsigned int nsdelegate:1;
> + unsigned int memory_recursiveprot:1;
> - int we_mounted_it:1;
> + unsigned int we_mounted_it:1;
> /* cpuset is in compatability mode */
> - int no_cpuset_prefix:1;
> + unsigned int no_cpuset_prefix:1;
> };
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-01-15 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a87594f-9066-4ee1-8bc7-5f9f2d71829a.jinguojie.jgj@alibaba-inc.com>
2025-01-15 6:33 ` [LTP] [PATCH v3] memcg/memcontrol04: Fix judgment for recursive_protection Jin Guojie
2025-01-15 9:26 ` Li Wang
2025-01-15 12:17 ` Petr Vorel [this message]
2025-01-15 12:49 ` Li Wang
2025-02-11 5:54 ` 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=20250115121744.GA648257@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=mkoutny@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