I've marked the chromium bug as invalid since snapd now allows
sched_setaffinity with browser-sandbox: true (see comment 16). I checked
here with firefox and chromium (both snaps) and the only syscall=203
denial is unrelated:

$ journalctl -o cat -b-1 -k --grep syscall=203
audit: type=1326 audit(1666098873.038:90): auid=1000 uid=1000 gid=1000 ses=3 
subj=? pid=3817 comm="snapd-desktop-i" 
exe="/snap/snapd-desktop-integration/14/bin/snapd-desktop-integration" sig=0 
arch=c000003e syscall=203 compat=0 ip=0x7078b4388741 code=0x50000

** Changed in: chromium-browser (Ubuntu)
       Status: Confirmed => Invalid

-- 
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] Apparmor audit messages for calls to sched_setaffinity

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Committed

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     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to