diff options
author | David Herrmann <dh.herrmann@gmail.com> | 2015-06-23 10:47:44 +0200 |
---|---|---|
committer | David Herrmann <dh.herrmann@gmail.com> | 2015-06-24 13:45:56 +0200 |
commit | 12b7dff45b0e2442355008a1e53f1211bd227147 (patch) | |
tree | 88d3cc7f2c2dce683630d13205dae4bf0e0f5b13 /src/path | |
parent | 979e7eb9cc3376f23c08054b4e5987f5874377e5 (diff) |
sd-netlink: make sure the root-level type is nested
In sd-netlink-message, we always guarantee that the currently selected
type-system is non-NULL. Otherwise, we would be unable to parse any types
in the current container level. Hence, this assertion must be true:
message->container_type_system[m->n_containers] != NULL
During message_new() we currently do not verify that this assertion is
true. Instead, we blindly access nl_type->type_system and use it (which
might be NULL for basic types and unions). Fix this, by explicitly
checking that the root-level type is nested.
Note that this is *not* a strict requirement of netlink, but it's a strict
requirement for all message types we currently support. Furthermore, all
the callers of message_new() already verify that only supported types are
passed, therefore, this is a pure cosmetic check. However, it might be
needed on the future, so make sure we don't trap into this once we change
the type-system.
Diffstat (limited to 'src/path')
0 files changed, 0 insertions, 0 deletions