diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2020-01-22 17:18:38 +0100 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2020-01-22 18:31:19 +0100 |
| commit | 2bdcee05b50579be92a767376eaf874c0c70233c (patch) | |
| tree | 73d2a134e08e0800790cecf0e39c944653ca5a8f /sys/linux/ipvs.txt.warn | |
| parent | e4c56f390e76bddfd2911006d7036e2970b3f5d1 (diff) | |
sys/linux: mark all nested netlink attributes as nlnest
As far as I understand most subsystems don't care about
the nest flag, but some do. But marking them as nest
won't harm (?). Let's mark all of them.
Caught several cases where should have been used array[policy]
but used just policy.
Update #590
Diffstat (limited to 'sys/linux/ipvs.txt.warn')
| -rw-r--r-- | sys/linux/ipvs.txt.warn | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/sys/linux/ipvs.txt.warn b/sys/linux/ipvs.txt.warn index e718436c0..238b7447e 100644 --- a/sys/linux/ipvs.txt.warn +++ b/sys/linux/ipvs.txt.warn @@ -1,5 +1,2 @@ -bad-netlink-attr: ip_vs_cmd_policy.IPVS_CMD_ATTR_SERVICE: should be nlnest -bad-netlink-attr: ip_vs_cmd_policy.IPVS_CMD_ATTR_DEST: should be nlnest -bad-netlink-attr: ip_vs_cmd_policy.IPVS_CMD_ATTR_DAEMON: should be nlnest bad-netlink-attr: ip_vs_dest_policy.IPVS_DEST_ATTR_FWD_METHOD: bad size 2, expect 4 no-such-struct: ip_vs_svcdest_user |