On Thu, 10 Nov 2005, Thomas Graf wrote:
> Although generic netlink modules can request static identifiers,
> it is recommended to use GENL_ID_GENERATE and to let the controller
> assign a unique identifier to the module. Userspace applications
> will then ask the controller and lookup the idenfier by the module
> name.
For SELinux, we'll need to track genl ID assignment and deletion, so we
can determine what the Netlink family number means when we see a Netlink
message. We'll have to assume that the sysadmin has not changed the
module name.
Could you consider adding a prefix to struct members to help grepping the
code?
e.g.
struct genl_family
{
unsigned int id;
unsigned int hdrsize;
becomes
struct genl_family
{
unsigned int genlf_id;
unsigned int genlf_hdrsize;
etc.
Looks like cool stuff. Are you replacing the Netlink connector?
- James
--
James Morris
<[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
