genetlink: mark families as __ro_after_init
Now genl_register_family() is the only thing (other than the users themselves, perhaps, but I didn't find any doing that) writing to the family struct. In all families that I found, genl_register_family() is only called from __init functions (some indirectly, in which case I've add __init annotations to clarifly things), so all can actually be marked __ro_after_init. This protects the data structure from accidental corruption. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:

committed by
David S. Miller

parent
2ae0f17df1
commit
56989f6d85
@@ -2740,7 +2740,7 @@ static const struct genl_multicast_group team_nl_mcgrps[] = {
|
||||
{ .name = TEAM_GENL_CHANGE_EVENT_MC_GRP_NAME, },
|
||||
};
|
||||
|
||||
static struct genl_family team_nl_family = {
|
||||
static struct genl_family team_nl_family __ro_after_init = {
|
||||
.name = TEAM_GENL_NAME,
|
||||
.version = TEAM_GENL_VERSION,
|
||||
.maxattr = TEAM_ATTR_MAX,
|
||||
@@ -2773,7 +2773,7 @@ static int team_nl_send_event_port_get(struct team *team,
|
||||
port);
|
||||
}
|
||||
|
||||
static int team_nl_init(void)
|
||||
static int __init team_nl_init(void)
|
||||
{
|
||||
return genl_register_family(&team_nl_family);
|
||||
}
|
||||
|
Reference in New Issue
Block a user