I know anonymous inodes are related to polling the disk for data which isn't there anymore, but how come SELinux only just now decided to spit these warnings out at me after four years of use with no issues like this and no updates of the SELinux Arch packages in a week save for systemd?
Code:
AVC avc: denied { use } for pid=333009 comm="sudo" path="anon_inode:[eventfd]" dev="anon_inodefs" ino=7972 scontext=deckard_u:staff_r:staff_sudo_t tcontext=deckard_u:staff_r:staff_systemd_t tclass=fd permissive=0
Can I safely ignore these, seeing as they're only happening when I transition to root via sudo? What problems might result from not allowing, or allowing as it were, this in policy?
