netdev - Re: [Patch 1/5] Network Drop Monitor: Add netlink protocol identifer

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]

Date:	Tue, 3 Mar 2009 22:04:57 +0300
From:	Evgeniy Polyakov <zbr@...emap.net>
To:	Neil Horman <nhorman@...driver.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [Patch 1/5] Network Drop Monitor: Add netlink protocol identifer

On Tue, Mar 03, 2009 at 02:00:54PM -0500, Neil Horman (nhorman@...driver.com) wrote:
> Because this is its own protocol.  I could have used NETLINK_GENERIC I suppose,
> but this is a feature that, if used is going to be commonly built into the
> kernel, I see no need to add an additional step of making userspace search for a
> protocol registered to NETLINK_GENERIC when we dont need to.  In other words,
> why not define my own protocol?

genetlink is alwats built into the kernel, there are access libraries
helpers and there is really no userspace overhead. It was really
specially designed for this kind of the tasks to eliminate netlink
internal structure access and provide simple high-level interface.

-- 
	Evgeniy Polyakov
--
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