Closed martinpitt closed 8 months ago
So Chromium is doing something dubious here.
Just FTR: I am not so sure about dubious. Chromium's JIT has always needed executable memory, and that was always okay with SELinux. But something must have changed in the details.
With current Fedora 39, Chromium often runs into these crashes:
This causes the browser to hang, and the test force-killed after the timeout.
The general tone in past bug reports is that this is intended -- heap shouldn't be writable and executable at the same time. So Chromium is doing something dubious here.
This isn't something we can easily influence, so just poke a hole into the policy.
This was generated by collecting the full denial with
ausearch -c 'ThreadPoolForeg' --raw
, and feeding the result intoaudit2allow
:Fixes #579
I rolled this out to our infra. Let's check tomorrow morning if it actually worked. Update: It did, and it's still necessary with Chromium 122.