Johannes Berg a07ea4d994 genetlink: no longer support using static family IDs
Static family IDs have never really been used, the only
use case was the workaround I introduced for those users
that assumed their family ID was also their multicast
group ID.

Additionally, because static family IDs would never be
reserved by the generic netlink code, using a relatively
low ID would only work for built-in families that can be
registered immediately after generic netlink is started,
which is basically only the control family (apart from
the workaround code, which I also had to add code for so
it would reserve those IDs)

Thus, anything other than GENL_ID_GENERATE is flawed and
luckily not used except in the cases I mentioned. Move
those workarounds into a few lines of code, and then get
rid of GENL_ID_GENERATE entirely, making it more robust.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-10-27 16:16:09 -04:00
..
2015-08-25 13:37:31 -07:00
2015-05-28 11:23:20 +08:00
2016-09-10 23:12:51 -07:00
2016-05-31 14:07:49 -07:00
2016-09-10 23:12:52 -07:00
2016-09-06 12:54:17 -07:00
2016-04-27 22:48:24 -04:00
2016-10-20 14:51:10 -04:00
2016-06-27 15:06:17 -04:00
2015-02-28 16:56:51 -05:00
2015-11-03 10:52:13 -05:00
2016-08-23 23:23:50 -07:00
2016-09-21 10:09:14 +02:00
2016-09-21 10:09:14 +02:00