As I've been working on the multiple concurrent modules project I have frequently encountered the use of the function prefix security_ in SELinux specific code. I understand and appreciate that this code has been there since the dawn of time. The LSM infrastructure also uses this prefix, and that's where I have my concern. When I'm grubbing about for uses of the LSM infrastructure in the SELinux code it's really quite annoying. Would the SELinux community be open to considering the possibility of thinking about cleaning up this bit of namespace pollution? It surely isn't a critical issue, but it would certainly look better. security_context_to_sid -> selinux_context_to_sid Just a thought. _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
