netdev - Re: [PATCH 0/9] genetlink: clean up multicast group APIs

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] [day] [month] [year] [list]

Message-Id: <20131119.164034.545622999253259387.davem@davemloft.net>
Date:	Tue, 19 Nov 2013 16:40:34 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	johannes@...solutions.net
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 0/9] genetlink: clean up multicast group APIs

From: Johannes Berg <johannes@...solutions.net>
Date: Tue, 19 Nov 2013 15:19:30 +0100

> The generic netlink multicast group registration doesn't have to
> be dynamic, and can thus be simplified just like I did with the
> ops. This removes some complexity in registration code.
> 
> Additionally, two users of generic netlink already use multicast
> groups in a wrong way, add workarounds for those two to keep the
> userspace API working, but at the same time make them not clash
> with other users of multicast groups as might happen now.
> 
> While making it all a bit easier, also prevent such abuse by adding
> checks to the APIs so each family can only use the groups it owns.

This looks great, and makes the unfortunate multicast ID handling in
DM and elsewhere explicit, controlled, and validated.

Series applied, thanks.
--
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