Reading about SCHED_RR, we had some reports in focal which were about issues setting real-time priority to processes and that appeared to be caused by enabling CONFIG_RT_GROUP_SCHED (which was a request by docker). That happened before release and after 5.4.0-21 (see bug #1873315). And Thadeu's commment #6 points to code which is active only when that config is turned on.
So this is something that we released with and the question is whether it should be "fixed" by turning this off again or having properly handled the special cases. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876697 Title: test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on zVM "kernel04" with 5.4.0-29.33 ====================================================================== FAIL: test_regression_testsuite (__main__.ApparmorTestsuites) Run kernel regression tests ---------------------------------------------------------------------- Traceback (most recent call last): File "./test-apparmor.py", line 1746, in test_regression_testsuite self.assertEqual(expected, rc, result + report) AssertionError: Got exit code 2, expected 0 running aa_exec running access xfail: ACCESS file rx (r) xfail: ACCESS file rwx (r) xfail: ACCESS file r (wx) xfail: ACCESS file rx (wx) xfail: ACCESS file rwx (wx) xfail: ACCESS dir rwx (r) xfail: ACCESS dir r (wx) xfail: ACCESS dir rx (wx) xfail: ACCESS dir rwx (wx) running at_secure running introspect running capabilities (ptrace) (sethostname) (setdomainname) (setpriority) (setscheduler) Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- unconfined' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation not permitted' Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- all caps' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation not permitted' preparing apparmor_2.13.3-7ubuntu5.dsc... done Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- capability sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation not permitted' Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- all caps' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation not permitted' Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- capability sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation not permitted' (reboot) (chroot) (mlockall) (net_raw) Please find attachment for the complete test log. To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1876697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
