Comment 1 for bug 1578217

I think the proposal is generally fine but I wonder about its viability with pulseaudio which creates a number of shm files in /dev/shm. Eg:

$ ls -l /dev/shm/pulse-shm-*
-rwx------ 1 jamie jamie 67108904 May 2 19:11 /dev/shm/pulse-shm-1126818553
-rwx------ 1 jamie jamie 67108904 May 3 09:39 /dev/shm/pulse-shm-1225715323
-rwx------ 1 jamie jamie 67108904 May 3 16:40 /dev/shm/pulse-shm-145271673
-rwx------ 1 lightdm lightdm 67108904 May 2 19:11 /dev/shm/pulse-shm-147887719
-rwx------ 1 jamie jamie 67108904 May 4 08:35 /dev/shm/pulse-shm-1487298717
-rwx------ 1 jamie jamie 67108904 May 2 19:11 /dev/shm/pulse-shm-2387793072
-rwx------ 1 lightdm lightdm 67108904 May 2 19:11 /dev/shm/pulse-shm-2399721183
-rwx------ 1 jamie jamie 67108904 May 4 08:35 /dev/shm/pulse-shm-3323349813
-rwx------ 1 jamie jamie 67108904 May 3 14:14 /dev/shm/pulse-shm-3437821583
-rwx------ 1 lightdm lightdm 67108904 May 2 19:11 /dev/shm/pulse-shm-36248552
-rwx------ 1 jamie jamie 67108904 May 2 19:11 /dev/shm/pulse-shm-980235161

Have you tested this approach with an app that uses pulseaudio? (I understand there is no pulseaudio interface yet, but it can be tested by adjust the policy directly).