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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg Status in chromium-browser package in Ubuntu: New Status in snapd package in Ubuntu: Incomplete Bug description: [T okt 20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210734): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x50000 [T okt 20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210735): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x50000 [T okt 20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210736): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x50000 [T okt 20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210737): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x50000 [T okt 20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210738): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x50000 [T okt 20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210739): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x50000 Things like these just get repeated endlessly and very often, making any potential debugging very annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
