Johannes Berg ef6243acb4 genetlink: optionally validate strictly/dumps ... Add options to strictly validate messages and dump messages, sometimes perhaps validating dump messages non-strictly may be required, so add an option for that as well. Since none of this can really be applied to existing commands, set the options everwhere using the following spatch: @@ identifier ops; expression X; @@ struct genl_ops ops[] = { ..., { .cmd = X, + .validate = GENL_DONT_VALIDATE_STRICT | GENL_DONT_VALIDATE_DUMP, ... }, ... }; For new commands one should just not copy the .validate 'opt-out' flags and thus get strict validation. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2019-04-27 17:07:22 -04:00
..
hci
nci	NFC: nci: Add some bounds checking in nci_hci_cmd_received()	2019-04-06 15:05:07 -07:00
af_nfc.c
core.c
digital_core.c
digital_dep.c
digital_technology.c
digital.h
Kconfig
llcp_commands.c
llcp_core.c
llcp_sock.c
llcp.h
Makefile
netlink.c	genetlink: optionally validate strictly/dumps	2019-04-27 17:07:22 -04:00
nfc.h
rawsock.c