I recently went ahead and confined PCSX-df (downloaded from Codeplex, of course) in its own domain with the SELinux policy creator, didn't issue any real privileges to it, and got it past the mmap() segfault it gives out when running headlong into the allow_unconfined_mmap_low() boolean. After firing up one of my games, it froze PCSX-df after a couple of minutes and some real choppy audio.
It wouldn't let me kill the pcsx process with a -9 via terminal, a top command showed 99.7 CPU being devoted to PCSX, and the system responded in every other way except for that. I had to restart the computer, after which I logged out, tried logging back in, and got a "too many logins for <user>" warning.
PulseAudio, upon checking audit and message logs, seemed to be the culprit. Its latency kept climbing and made the whole thing run out of memory.
SELinux was running in enforcing mode, but since I remember something about PulseAudio being a major security problem (is that still true for recent F11 repo kernels?) I just wanted to double check and see if I haven't boned the pooch by doing something bad.
Can anyone help shed some light on this?
Linear Mode
