All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avinesh Kumar <akumar@suse.de>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: "Martin Doucha" <martin.doucha@suse.com>,
	"Michal Koutný" <mkoutny@suse.com>,
	ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] cgroup_regression_test: Use unique names for hierarchies in each test
Date: Wed, 30 Jul 2025 13:32:45 +0200	[thread overview]
Message-ID: <9489066.CDJkKcVGEf@thinkpad> (raw)
In-Reply-To: <a019aba3-eaa1-4dd9-973b-c4bb8f3d4973@suse.com>

Hi all¸

I would like to ask if there are any other suggestions on how to address this
issue.
I tried a rather simpler approach (as suggested by Martin) of just adding a
delay using sleep after the umount call, which also seems to solve this issue
of incomplete unmounting.

--- a/testcases/kernel/controllers/cgroup/cgroup_regression_test.sh
+++ b/testcases/kernel/controllers/cgroup/cgroup_regression_test.sh
@@ -102,10 +102,11 @@ test1()
        cat cgroup/tasks > /dev/null
 
        kill -TERM $!
        wait $! 2>/dev/null
        umount cgroup/
+       sleep 2
        check_kernel_bug
 }

I will send this in the patch if we agree to use this approach instead of
unique names.

Thanks,
Avinesh

On Monday, July 14, 2025 1:56:51 PM CEST Andrea Cervesato wrote:
> On 7/11/25 3:15 PM, Michal Koutný wrote:
> > On Fri, Jul 11, 2025 at 02:41:18PM +0200, Andrea Cervesato <andrea.cervesato@suse.com> wrote:
> >> This git commit is part of cgroup v1 code and now in
> >> kernel/cgroup/cgroup-v1.c:cgroup1_root_to_use, but I don't see the same
> >> mechanism used by cgroup v2, which is our main version.
> > The patched tests use cgroup v1.
> >
> >> Is that something which might affect our system?
> > Since there's only one cgroup v2 (unified) hierarchy, it sort of lives
> > forever (statically alloc'd), so I wouldn't expect such residuals on v2
> > (with the current implementation).
> >
> > Michal
> 
> I bisected util-linux, but it doesn't seem to be the problem. On my 
> system (Tumbleweed), we are facing the same failure, no matter the 
> commit that is tested in util-linux between 2.39 and 2.41 versions.
> 
> I guess this issue might be caused by a specific setup of the Linux 
> kernel and its async nature, mixed with some services which are slowing 
> down the umount process.
> 
> I'm wondering how to proceed, since this is actually a soft-failure and 
> any fix to the test might hide future bugs.
> 
> - Andrea
> 
> 






-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-07-30 11:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10  8:17 [LTP] [PATCH] cgroup_regression_test: Use unique names for hierarchies in each test Avinesh Kumar
2025-07-10  8:24 ` Avinesh Kumar
2025-07-10  8:47   ` Andrea Cervesato via ltp
2025-07-10  9:00     ` Cyril Hrubis
2025-07-11 10:36       ` Andrea Cervesato via ltp
     [not found]         ` <mqkxe24qlrcpb5jxgigbiarxxgemqjw3rmgnsprn55ubghrrda@etaozcz2nemy>
2025-07-11 12:41           ` Andrea Cervesato via ltp
     [not found]             ` <svs6pl6jmibp7uylvofkia5smvu2cuezfvnawlgkmjiulbrpfm@w7s7dlxxltap>
2025-07-14 11:56               ` Andrea Cervesato via ltp
2025-07-30 11:32                 ` Avinesh Kumar [this message]
2025-07-30 11:43                   ` Martin Doucha
2025-07-30 11:48                 ` Michal Koutný via ltp

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=9489066.CDJkKcVGEf@thinkpad \
    --to=akumar@suse.de \
    --cc=andrea.cervesato@suse.com \
    --cc=ltp@lists.linux.it \
    --cc=martin.doucha@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.