Re: [PATCH net-next 00/20] rtnetlink: Add support for rigid checking of data in dump request

2018-10-05 Thread David Miller
From: David Ahern Date: Fri, 5 Oct 2018 15:18:11 -0600 > One thing I missed in the rfc and v1 versions is strict attribute > parsing -- ie., there should be nothing remaining after nla_parse is > done. I have a new patch that adds an nlmsg_parse_strict and > nla_parse_strict that returns -EINVAL

Re: [PATCH net-next 00/20] rtnetlink: Add support for rigid checking of data in dump request

2018-10-05 Thread David Ahern
On 10/4/18 3:33 PM, David Ahern wrote: > From: David Ahern ... > This patch set addresses the problem by adding a new socket flag, > NETLINK_DUMP_STRICT_CHK, that userspace can use with setsockopt to > request strict checking of headers and attributes on dump requests and > hence unlock the abil

[PATCH net-next 00/20] rtnetlink: Add support for rigid checking of data in dump request

2018-10-04 Thread David Ahern
From: David Ahern There are many use cases where a user wants to influence what is returned in a dump for some rtnetlink command: one is wanting data for a different namespace than the one the request is received and another is limiting the amount of data returned in the dump to a specific set of