memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11

[Kleber Sacilotto de Souza]

memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out when running with hirsute/linux 5.11.

startup='Mon Jul 19 15:17:41 2021'
memcg_subgroup_charge 1 TINFO: timeout per run is 0h 5m 0s
memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_subgroup_charge 1 TINFO: Test that group and subgroup have no relationship
memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 270336
memcg_subgroup_charge 1 TINFO: Warming up pid: 443417
memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 443417
memcg_subgroup_charge 1 TBROK: timed out on memory.usage_in_bytes
memcg_subgroup_charge 1 TINFO: AppArmor enabled, this may affect test results
memcg_subgroup_charge 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
memcg_subgroup_charge 1 TINFO: loaded AppArmor profiles: none

Summary:
passed 0
failed 0
broken 1
skipped 0
warnings 0
tag=memcg_subgroup_charge stime=1626707861 dur=11 exit=exited stat=2 core=no cu=19 cs=12

This is not a regression as it already failed on previous releases.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1939035

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Brian Murray (brian-murray)]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release.