From: Bert Karwatzki <spasswolf@web.de>
To: Mark Brown <broonie@kernel.org>, Tejun Heo <tj@kernel.org>
Cc: "Johannes Weiner" <hannes@cmpxchg.org>,
"spasswolf@web.de Michal Koutný" <mkoutny@suse.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Petr Malat" <oss@malat.biz>,
"kernel test robot" <oliver.sang@intel.com>,
"Martin Pitt" <martin@piware.de>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Aishwarya.TCV@arm.com
Subject: Re: [PATCH 5/5] cgroup: Defer kill_css_finish() in cgroup_apply_control_disable()
Date: Sun, 31 May 2026 11:19:30 +0200 [thread overview]
Message-ID: <8b15e2465901b48ee63f4827c69a67ff6d0e6098.camel@web.de> (raw)
In-Reply-To: <fd72aa26-4fed-4fcb-b4b1-d7ce9d891fe4@sirena.org.uk>
Am Freitag, dem 29.05.2026 um 22:08 +0100 schrieb Mark Brown:
> On Fri, May 29, 2026 at 07:25:29AM -1000, Tejun Heo wrote:
> > On Wed, May 27, 2026 at 11:45:54AM +0100, Mark Brown wrote:
> > > On Mon, May 04, 2026 at 02:51:21PM -1000, Tejun Heo wrote:
>
> > > with no further output and given that this is a cgroup locking change
> > > this does seem like a plausible commmit, though I didn't look into it in
> > > detail. Bisect log and the list of LTP tests we're running in our test
> > > job below. We are running multuple tests in parallel.
>
> > Unfortunately, I can't reproduce this in my environment. Any chance you can
> > try testing on x86 tooa nd see whether it produces there?
>
> Not readily sadly, I'll see if I can figure something out. Our rootfs
> images are based on Debian Trixie if that's relevant?
Using debian unstable (sid/forky) I can at least detect a timeout when running
the ltp controller testsuite:
# LTPROOT=/home/bert/ltp-install/ ./kirk --run-suite controllers
Host information
Hostname: homer
Python: 3.13.12 (main, Feb 4 2026, 15:06:39) [GCC 15.2.0]
Directory: /tmp/kirk.root/tmp092in2yb
Connecting to SUT: default
Suite: controllers
──────────────────
cgroup_core01: pass (0.024s)
cgroup_core02: pass (0.004s)
cgroup_core03: pass (0.017s)
cgroup: skip (2m 41s)
memcg_regression: skip (3.414s)
memcg_test_3: pass (0.090s)
memcg_failcnt: skip (0.019s)
memcg_force_empty: skip (0.015s)
memcg_limit_in_bytes: skip (0.017s)
memcg_stat_rss: skip (0.015s)
memcg_subgroup_charge: skip (0.015s)
memcg_max_usage_in_bytes: skip (0.014s)
memcg_move_charge_at_immigrate: skip (0.014s)
memcg_memsw_limit_in_bytes: skip (0.015s)
memcg_stat: skip (0.015s)
memcg_use_hierarchy: skip (0.015s)
memcg_usage_in_bytes: skip (0.014s)
memcg_stress: pass (30m 4s)
memcg_control: pass (6.058s)
memcontrol01: pass (0.004s)
memcontrol02: pass (0.636s)
memcontrol03: pass (15.983s)
memcontrol04: pass (0.890s)
cgroup_fj_function_debug: skip (0.013s)
cgroup_fj_function_cpuset: skip (0.044s)
cgroup_fj_function_cpu: skip (0.050s)
cgroup_fj_function_cpuacct: pass (0.052s)
cgroup_fj_function_memory: skip (0.042s)
cgroup_fj_function_freezer: pass (0.044s)
cgroup_fj_function_devices: pass (0.066s)
cgroup_fj_function_blkio: skip (0.009s)
cgroup_fj_function_net_cls: pass (0.073s)
cgroup_fj_function_perf_event: pass (0.072s)
cgroup_fj_function_net_prio: Suite 'controllers' timed out after 3600 seconds
Execution time: 1h 33m 13s
Disconnecting from SUT: default
Target information
──────────────────
Kernel: Linux 7.1.0-rc5-next-20260528-master-dirty #480 SMP PREEMPT_RT Thu May 28 19:55:12 CEST 2026
Cmdline: BOOT_IMAGE=/boot/vmlinuz-7.1.0-rc5-next-20260528-master-dirty
root=UUID=3d5cdc5d-1902-40bf-9e16-ca819372d350
ro
quiet
Machine: unknown
Arch: x86_64
RAM: 63439380 kB
Swap: 78125052 kB
Distro: debian
────────────────────────
TEST SUMMARY
────────────────────────
Suite: controllers
Runtime: 33m 13s
Runs: 347
Results:
Passed: 181
Failed: 0
Broken: 0
Skipped: 350
Warnings: 0
Session stopped
In dmesg I get messages about task tst_cgtl hanging:
[ 2212.794669] [ T346] INFO: task tst_cgctl:317896 blocked for more than 122 seconds.
[ 2212.794674] [ T346] Not tainted 7.1.0-rc5-next-20260528-master-dirty #480
[ 2212.794675] [ T346] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[...]
[ 3318.721344] [ T346] INFO: task tst_cgctl:317896 blocked for more than 1228 seconds.
[ 3318.721349] [ T346] Not tainted 7.1.0-rc5-next-20260528-master-dirty #480
[ 3318.721351] [ T346] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
On 6.19.14 the Results of this testrun is:
# LTPROOT=/home/bert/ltp-install/ ./kirk --run-suite controllers
[...]
Target information
──────────────────
Kernel: Linux 6.19.14-stable #1238 SMP PREEMPT_RT Sat May 30 17:28:29 CEST 2026
Cmdline: BOOT_IMAGE=/boot/vmlinuz-6.19.14-stable
root=UUID=3d5cdc5d-1902-40bf-9e16-ca819372d350
ro
quiet
Machine: unknown
Arch: x86_64
RAM: 63436188 kB
Swap: 78125052 kB
Distro: debian
────────────────────────
TEST SUMMARY
────────────────────────
Suite: controllers
Runtime: 36m 12s
Runs: 347
Results:
Passed: 1742
Failed: 0
Broken: 0
Skipped: 97
Warnings: 0
Session stopped
With 6.19.14 I also get no hung tasks.
On 7.0.10 the tests also work:
root@homer:/mnt/data/linux-forest/kirk# LTPROOT=/home/bert/ltp-install/ ./kirk --run-suite controllers
Host information
Hostname: homer
Python: 3.13.12 (main, Feb 4 2026, 15:06:39) [GCC 15.2.0]
Directory: /tmp/kirk.root/tmpq32b09g7
Connecting to SUT: default
Suite: controllers
──────────────────
cgroup_core01: pass (0.016s)
[...]
pids_9_100: pass (0.107s)
Execution time: 36m 15s
Disconnecting from SUT: default
Target information
──────────────────
Kernel: Linux 7.0.10-stable #1239 SMP PREEMPT_RT Sun May 31 00:42:41 CEST 2026
Cmdline: BOOT_IMAGE=/boot/vmlinuz-7.0.10-stable
root=UUID=3d5cdc5d-1902-40bf-9e16-ca819372d350
ro
quiet
Machine: unknown
Arch: x86_64
RAM: 63435940 kB
Swap: 78125052 kB
Distro: debian
────────────────────────
TEST SUMMARY
────────────────────────
Suite: controllers
Runtime: 36m 13s
Runs: 347
Results:
Passed: 1742
Failed: 0
Broken: 0
Skipped: 97
Warnings: 0
Session stopped
I'm not sure if this is related to the problems on arm64, but I'll try bisecting this.
Bert Karwatzki
next prev parent reply other threads:[~2026-05-31 9:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 0:51 [PATCHSET cgroup/for-7.2] cgroup: Per-css kill_css_finish deferral Tejun Heo
2026-05-05 0:51 ` [PATCH 1/5] cgroup: Inline cgroup_has_tasks() in cgroup.h Tejun Heo
2026-05-05 0:51 ` [PATCH 2/5] cgroup: Annotate unlocked nr_populated_* accesses with READ_ONCE/WRITE_ONCE Tejun Heo
2026-05-05 0:51 ` [PATCH 3/5] cgroup: Move populated counters to cgroup_subsys_state Tejun Heo
2026-05-05 0:51 ` [PATCH 4/5] cgroup: Add per-subsys-css kill_css_finish deferral Tejun Heo
2026-05-05 0:51 ` [PATCH 5/5] cgroup: Defer kill_css_finish() in cgroup_apply_control_disable() Tejun Heo
2026-05-27 10:45 ` Mark Brown
2026-05-29 17:25 ` Tejun Heo
2026-05-29 21:08 ` Mark Brown
2026-05-31 9:19 ` Bert Karwatzki [this message]
2026-05-31 18:45 ` Bert Karwatzki
2026-06-01 9:22 ` Bert Karwatzki
2026-06-01 19:02 ` [PATCH] cgroup: Migrate tasks to the root css when a controller is rebound Tejun Heo
2026-06-01 19:07 ` Bert Karwatzki
2026-06-01 19:50 ` Bert Karwatzki
2026-06-02 16:28 ` Mark Brown
2026-06-02 18:34 ` Tejun Heo
2026-05-13 21:01 ` [PATCHSET cgroup/for-7.2] cgroup: Per-css kill_css_finish deferral Tejun Heo
2026-05-15 17:28 ` Tejun Heo
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=8b15e2465901b48ee63f4827c69a67ff6d0e6098.camel@web.de \
--to=spasswolf@web.de \
--cc=Aishwarya.TCV@arm.com \
--cc=bigeasy@linutronix.de \
--cc=broonie@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@piware.de \
--cc=mkoutny@suse.com \
--cc=oliver.sang@intel.com \
--cc=oss@malat.biz \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®