memcg_* from ubuntu_ltp_controllers fails on Focal 5.15 with mmap (Invalid argument)

[Kleber Sacilotto de Souza]

Testcases memcg_failcnt|memcg_max_usage_in_bytes|memcg_subgroup_charge|memcg_usage_in_byte from ubuntu_ltp_controllers are failing with focal/linux-lowlatency-5.15 5.15.0-41.44~20.04.1 flavor lowlatency-64k.

memcg_failcnt 1 TINFO: timeout per run is 0h 5m 0s
memcg_failcnt 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_failcnt 1 TINFO: Setting shmmax
memcg_failcnt 1 TINFO: Running memcg_process --mmap-anon -s 0
memcg_failcnt 1 TPASS: memory.failcnt is 36, > 0 as expected
memcg_failcnt 2 TINFO: Running memcg_process --mmap-file -s 0
memcg_process: mmap(file) failed: Invalid argument
memcg_failcnt 2 TFAIL: memory.failcnt is 0, <= 0 expected
memcg_failcnt 3 TINFO: Running memcg_process --shm -s 0
memcg_failcnt 3 TPASS: memory.failcnt is 36, > 0 as expected
memcg_failcnt 4 TINFO: AppArmor enabled, this may affect test results
memcg_failcnt 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
memcg_failcnt 4 TINFO: loaded AppArmor profiles: none

This doesn't seem to be a regression as this test is failing on other combinations of architectures/flavors with bug 1949532.

[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 1981070

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.