So I did a bit of looking and it appears that Chromium only calls sched_setaffinity for it's renderer threads on Android (maybe?). I'm not super familiar with Chromium source code so it's a bit difficult for me to tell, but I tried playing videos etc. which might trigger some sort of rendering code and I couldn't reproduce the denial.
@avamander, do you have a reproducer for this? I'm happy to allow chromium this access for browser-support with the allow-sandbox: true attribute as chromium uses it, as there are other more privileged system calls already allowed to Chromium through this interface and it appears to me that this system call may allow better performance on some specific devices with "big / little" architectures such as ARM, but I would like to see if anyone else can reproduce this and perhaps if Olivier can comment about Chromium's usage of sched_setaffinity... If we can't determine what is causing the denial, then we can also deny/silence it in the policy so it stops filling up log messages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
