From: kernel test robot <oliver.sang@intel.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
Bert Karwatzki <spasswolf@web.de>, <cgroups@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [cgroup] a72f73c4dd: kernel-selftests.cgroup.test_stress.sh.test_cgcore_destroy.fail
Date: Sun, 22 Mar 2026 21:48:01 +0800 [thread overview]
Message-ID: <202603222104.2c81684e-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests.cgroup.test_stress.sh.test_cgcore_destroy.fail" on:
commit: a72f73c4dd9b209c53cf8b03b6e97fcefad4262c ("cgroup: Don't expose dead tasks in cgroup")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master a0c83177734ab98623795e1ba2cf4b72c23de5e7]
[test failed on linux-next/master 785f0eb2f85decbe7c1ef9ae922931f0194ffc2e]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-8a30aeb0d1b4-1_20260319
with following parameters:
group: cgroup
config: x86_64-rhel-9.4-kselftests
compiler: gcc-14
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz (Skylake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
there is another test kernel-selftests.cgroup.test_core.test_cgcore_destroy also
failed on this commit but can pass on parent.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/group:
lkp-skl-d08/kernel-selftests/debian-13-x86_64-20250902.cgz/x86_64-rhel-9.4-kselftests/gcc-14/cgroup
ca174c705db52db3 a72f73c4dd9b209c53cf8b03b6e
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:9 67% 6:6 kernel-selftests.cgroup.test_core.test_cgcore_destroy.fail
:9 67% 6:6 kernel-selftests.cgroup.test_stress.sh.test_cgcore_destroy.fail
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202603222104.2c81684e-lkp@intel.com
TAP version 13
1..13
# timeout set to 300
# selftests: cgroup: test_core
# TAP version 13
# 1..12
# ok 1 test_cgcore_internal_process_constraint
# ok 2 test_cgcore_top_down_constraint_enable
# ok 3 test_cgcore_top_down_constraint_disable
# ok 4 test_cgcore_no_internal_process_constraint_on_threads
# ok 5 test_cgcore_parent_becomes_threaded
# ok 6 test_cgcore_invalid_domain
# ok 7 test_cgcore_populated
# ok 8 test_cgcore_proc_migration
# ok 9 test_cgcore_thread_migration
# not ok 10 test_cgcore_destroy <------------
# ok 11 test_cgcore_lesser_euid_open
# ok 12 test_cgcore_lesser_ns_open
# # Totals: pass:11 fail:1 xfail:0 xpass:0 skip:0 error:0
not ok 1 selftests: cgroup: test_core # exit=1
...
# timeout set to 300
# selftests: cgroup: test_stress.sh
# TAP version 13
# 1..12
# ok 1 test_cgcore_internal_process_constraint
# ok 2 test_cgcore_top_down_constraint_enable
# ok 3 test_cgcore_top_down_constraint_disable
# ok 4 test_cgcore_no_internal_process_constraint_on_threads
# ok 5 test_cgcore_parent_becomes_threaded
# ok 6 test_cgcore_invalid_domain
# ok 7 test_cgcore_populated
# ok 8 test_cgcore_proc_migration
# ok 9 test_cgcore_thread_migration
# not ok 10 test_cgcore_destroy <------------
# ok 11 test_cgcore_lesser_euid_open
# ok 12 test_cgcore_lesser_ns_open
# # Totals: pass:11 fail:1 xfail:0 xpass:0 skip:0 error:0
not ok 11 selftests: cgroup: test_stress.sh # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260322/202603222104.2c81684e-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-22 13:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202603222104.2c81684e-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=bigeasy@linutronix.de \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=spasswolf@web.de \
--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