Skip to contentSkip to conversation

hidden_def and libselinux

DISCUSSION Russell Coker 2 participants 2 messages Aug 29, 2011 SELinux security module

lore
Share & tools
lore
#0 lore raw

A build of libselinux 2.1.0 fails on Debian because of new symbols.

setrans_lib_destructor() and matchpathcon_lib_destructor() look like good candidates for hidden_def (or something similar) as it doesn't seem possible to call them from outside the library. What do you think?

There are a bunch of other new symbols that just need to be added to the symbol list.

Signature · 7 lines
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.
#1 lore raw
Quoted 9 lines · Russell Coker

A build of libselinux 2.1.0 fails on Debian because of new symbols.

setrans_lib_destructor() and matchpathcon_lib_destructor() look like good candidates for hidden_def (or something similar) as it doesn't seem possible to call them from outside the library. What do you think?

There are a bunch of other new symbols that just need to be added to the symbol list.

Use hidden to hide the symbol from external users. Use hidden_def/hidden_proto to declare and define a function that is visible to external users but also called within the library (defines a hidden internal reference that avoids relocations).

Signature · 8 lines
Stephen Smalley
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.