netdev - [PATCH 0/3] net: implement auto-loading of generic netlink modules

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1338319842-18395-1-git-send-email-nhorman@tuxdriver.com>
Date:	Tue, 29 May 2012 15:30:39 -0400
From:	Neil Horman <nhorman@...driver.com>
To:	netdev@...r.kernel.org
Cc:	Neil Horman <nhorman@...driver.com>,
	Eric Dumazet <eric.dumazet@...il.com>,
	James Chapman <jchapman@...alix.com>,
	David Miller <davem@...emloft.net>
Subject: [PATCH 0/3] net: implement auto-loading of generic netlink modules

Eric D. recently noted that the drop_monitor module didn't autoload when the
dropwatch user space utility started.  Looking into this I noted that theres no
formal macro set to define module aliases that can be used by a request module
call in the generic netlink family lookup path.  Currenlty the
net-pf-*-proto-*-type-<n> format is used, but the macros which form this expect
<n> to be a well defined integer, which generic netlink doesn't use for family
definitions.  So this series creates a new macro that create a
net-pf-*-proto-*-name format where name can be any arbitrary string, allowing us
to apend family-<x> where x is a generic netlink family name.  With these
macros, we can easily autoload modules that register generic netlink families

Signed-off-by: Neil Horman <nhorman@...driver.com>
CC: Eric Dumazet <eric.dumazet@...il.com>
CC: James Chapman <jchapman@...alix.com>
CC: David Miller <davem@...emloft.net>

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html