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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19462.1264468440@death.nxdomain.ibm.com>
Date:	Mon, 25 Jan 2010 17:14:00 -0800
From:	Jay Vosburgh <fubar@...ibm.com>
To:	David Miller <davem@...emloft.net>
cc:	netdev@...r.kernel.org
Subject: Re: Netlink usage question (for bonding comm with userspace)

David Miller <davem@...emloft.net> wrote:
[...]
>> 	I could, for this project, use a netlink_kernel_create and
>> socket(AF_NETLINK) pair to perform the communication (presumably adding
>> a NETLINK_BONDING or the like to <linux/netlink.h>).
>
>This is no longer done, so that we don't have an issue with
>running out of netlink sub-protocol numbers.
>
>Instead use generic netlink, the IDs are allocated dynamically
>and looked up via text strings which provides a better scheme
>for namespace allocation.

	Thanks for the response.

	Just so I'm clear, though: use generic netlink for the needs of
this particular project, and then later it's acceptable to have both
generic and rtnetlink co-existing for their respective uses?

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ