Hi Roman,
Just want to share information here on what we notice on running this test case,
On Fri, 5 Apr 2019 at 23:17, Roman Gushchin guroan@gmail.com wrote:
This patch implements 9 tests for the freezer controller for cgroup v2:
...
- ptrace test: the test checks that it's possible to attach to
a process in a frozen cgroup, get some information and detach, and the cgroup will remain frozen.
selftests cgroup test_freezer failed because of the sys entry path not found. Cgroup /sys/fs/cgroup/unified/cg_test_ptrace isn't frozen /sys/fs/cgroup/unified/cg_test_ptrace: isn't_frozen # # not ok 6 test_cgfreezer_ptrace
This test case fails intermittently.
Test output: ------------- # selftests cgroup test_freezer cgroup: test_freezer_ # # Cgroup /sys/fs/cgroup/unified/cg_test_ptrace isn't frozen /sys/fs/cgroup/unified/cg_test_ptrace: isn't_frozen # # ok 1 test_cgfreezer_simple 1: test_cgfreezer_simple_ # # ok 2 test_cgfreezer_tree 2: test_cgfreezer_tree_ # # ok 3 test_cgfreezer_forkbomb 3: test_cgfreezer_forkbomb_ # # ok 4 test_cgfreezer_rmdir 4: test_cgfreezer_rmdir_ # # ok 5 test_cgfreezer_migrate 5: test_cgfreezer_migrate_ # # not ok 6 test_cgfreezer_ptrace ok: 6_test_cgfreezer_ptrace # # ok 7 test_cgfreezer_stopped 7: test_cgfreezer_stopped_ # # ok 8 test_cgfreezer_ptraced 8: test_cgfreezer_ptraced_ # # ok 9 test_cgfreezer_vfork 9: test_cgfreezer_vfork_ # [FAIL] 3 selftests cgroup test_freezer selftests: cgroup_test_freezer [FAIL]
Test results link, https://qa-reports.linaro.org/lkft/linux-mainline-oe/tests/kselftest/cgroup_...
- Naresh
On Tue, Jul 16, 2019 at 08:18:39PM +0530, Naresh Kamboju wrote:
Hi Roman,
Just want to share information here on what we notice on running this test case,
Hi Naresh!
Thank you for the report!
The interaction between ptrace and freezer is complicated (as ptrace in general),so there are known cases when spurious cgroup transitions (frozen <-> non frozen <-> frozen ) can happen.
Does it create any difficulties? If so, I'll send a diff to ignore the result of this test for now.
Thank you!
On Fri, 5 Apr 2019 at 23:17, Roman Gushchin guroan@gmail.com wrote:
This patch implements 9 tests for the freezer controller for cgroup v2:
...
- ptrace test: the test checks that it's possible to attach to
a process in a frozen cgroup, get some information and detach, and the cgroup will remain frozen.
selftests cgroup test_freezer failed because of the sys entry path not found.
Can you, please, elaborate on this?
Cgroup /sys/fs/cgroup/unified/cg_test_ptrace isn't frozen /sys/fs/cgroup/unified/cg_test_ptrace: isn't_frozen # # not ok 6 test_cgfreezer_ptrace
This test case fails intermittently.
Thank you!
Hi Roman,
The interaction between ptrace and freezer is complicated (as ptrace in general),so there are known cases when spurious cgroup transitions (frozen <-> non frozen <-> frozen ) can happen.
When test ran for 8 times it got failed 5 times. I have noticed intermittent failure on x86_64, arm64 hikey device and qemu_arm64.
Does it create any difficulties? If so, I'll send a diff to ignore the result of this test for now.
No difficulties. I will mark this test case as known failure.
This patch implements 9 tests for the freezer controller for cgroup v2:
...
- ptrace test: the test checks that it's possible to attach to
a process in a frozen cgroup, get some information and detach, and the cgroup will remain frozen.
selftests cgroup test_freezer failed because of the sys entry path not found.
Can you, please, elaborate on this?
I see this failure output on screen and sharing log here.
Please find full test log here, https://lkft.validation.linaro.org/scheduler/job/825346#L673
- Naresh
On Wed, Jul 17, 2019 at 02:26:49PM +0530, Naresh Kamboju wrote:
Hi Roman,
The interaction between ptrace and freezer is complicated (as ptrace in general),so there are known cases when spurious cgroup transitions (frozen <-> non frozen <-> frozen ) can happen.
When test ran for 8 times it got failed 5 times. I have noticed intermittent failure on x86_64, arm64 hikey device and qemu_arm64.
Oh, it wasn't nearly as bad when I ran it. I'll take a look.
Does it create any difficulties? If so, I'll send a diff to ignore the result of this test for now.
No difficulties. I will mark this test case as known failure.
Sure.
Thanks!