rtnetlink: Add support for rigid checking of data in dump request
Subsystems (9)
David Ahern
maintainerv2 cover rtnetlink: Add support for rigid checking of data in dump request
From: David Ahern <[email protected]>
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 interest to userspace, reducing the cpu overhead of both kernel and userspace. Unfortunately, the kernel has historically not been strict with checking for the proper header or checking the values passed in the header. This lenient implementation has allowed iproute2 and other packages to pass any struct or data in the dump request as long as the family is the first byte. For example, ifinfomsg struct is used by iproute2 for all generic dump requests - links, addresses, routes and rules when it is really only valid for link requests.
There is 1 is example where the kernel deals with the wrong struct: link dumps after VF support was added. Older iproute2 was sending rtgenmsg as the header instead of ifinfomsg so a patch was added to try and detect old userspace vs new:e5eca6d41f53 ("rtnetlink: fix userspace API breakage for iproute2 < v3.9.0")
The latest example is Christian's patch set wanting to return addresses for a target namespace. It guesses the header struct is an ifaddrmsg and if it guesses wrong a netlink warning is generated in the kernel log on every address dump which is unacceptable.
Another example where the kernel is a bit lenient is route dumps: iproute2 can send either a request with either ifinfomsg or a rtmsg as the header struct, yet the kernel always treats the header as an rtmsg (see inet_dump_fib and rtm_flags check). The header inconsistency impacts the ability to add kernel side filters for route dumps - a necessary feature for scale setups with 100k+ routes.
How to resolve the problem of not breaking old userspace yet be able to move forward with new features such as kernel side filtering which are crucial for efficient operation at high scale?
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 ability to use kernel side filters as they are added.
Kernel side, the dump handlers are updated to verify the message contains at least the expected header struct:
RTM_GETLINK: ifinfomsg
RTM_GETADDR: ifaddrmsg
RTM_GETMULTICAST: ifaddrmsg
RTM_GETANYCAST: ifaddrmsg
RTM_GETADDRLABEL: ifaddrlblmsg
RTM_GETROUTE: rtmsg
RTM_GETSTATS: if_stats_msg
RTM_GETNEIGH: ndmsg
RTM_GETNEIGHTBL: ndtmsg
RTM_GETNSID: rtgenmsg
RTM_GETRULE: fib_rule_hdr
RTM_GETNETCONF: netconfmsg
RTM_GETMDB: br_port_msgAnd then every field in the header struct should be 0 with the exception of the family. There are a few exceptions to this rule where the kernel already influences the data returned by values in the struct. Next the message should not contain attributes unless the kernel implements filtering for it. Any unexpected data causes the dump to fail with EINVAL. If the new flag is honored by the kernel and the dump contents adjusted by any data passed in the request, the dump handler can set the NLM_F_DUMP_FILTERED flag in the netlink message header.
For old userspace on new kernel there is no impact as all checks are wrapped in a check on the new strict flag. For new userspace on old kernel, the data in the headers and any appended attributes are silently ignored though the setsockopt failing is the clue to userspace the feature is not supported. New userspace on new kernel gets the requested data dump.
iproute2 patches can be found here:
https://github.com/dsahern/iproute2 dump-enhancements
Major changes since v1
- inner header is supposed to be 4-bytes aligned. So for dumps that should not have attributes appended changed the check to use:
if (nlmsg_attrlen(nlh, sizeof(hdr)))
Only impacts patches with headers that are not multiples of 4-bytes (rtgenmsg, netconfmsg), but applied the change to all patches not calling nlmsg_parse for consistency.
- Added nlmsg_parse_strict and nla_parse_strict for tighter control on attribute parsing. There should be no unknown attribute types or extra bytes.
- Moved validation to a helper in most cases
Changes since rfc-v2
- dropped the NLM_F_DUMP_FILTERED flag from target nsid dumps per Jiri's objections
- changed the opt-in uapi from a netlink message flag to a socket flag. setsockopt provides an api for userspace to definitively know if the kernel supports strict checking on dumps.
- re-ordered patches to peel off the extack on dumps if needed to keep this set size within limits
- misc cleanups in patches based on testing
David Ahern (23):
netlink: Pass extack to dump handlers
netlink: Add extack message to nlmsg_parse for invalid header length
net: Add extack to nlmsg_parse
netlink: Add strict version of nlmsg_parse and nla_parse net/ipv6: Refactor address dump to push inet6_fill_args to
in6_dump_addrs
netlink: Add new socket option to enable strict checking on dumps net/ipv4: Update inet_dump_ifaddr for strict data checking net/ipv6: Update inet6_dump_addr for strict data checking
rtnetlink: Update rtnl_dump_ifinfo for strict data checking
rtnetlink: Update rtnl_bridge_getlink for strict data checking
rtnetlink: Update rtnl_stats_dump for strict data checking
rtnetlink: Update inet6_dump_ifinfo for strict data checking
rtnetlink: Update ipmr_rtm_dumplink for strict data checking
rtnetlink: Update fib dumps for strict data checking net/neighbor: Update neigh_dump_info for strict data checking net/neighbor: Update neightbl_dump_info for strict data checking net/namespace: Update rtnl_net_dumpid for strict data checking net/fib_rules: Update fib_nl_dumprule for strict data checking net/ipv6: Update ip6addrlbl_dump for strict data checking
net: Update netconf dump handlers for strict data checking net/bridge: Update br_mdb_dump for strict data checking
rtnetlink: Move input checking for rtnl_fdb_dump to helper
rtnetlink: Update rtnl_fdb_dump for strict data checking
include/linux/netlink.h | 2 + include/net/ip_fib.h | 2 + include/net/netlink.h | 21 ++- include/uapi/linux/netlink.h | 1 + lib/nlattr.c | 48 +++++-- net/bridge/br_mdb.c | 30 ++++ net/core/devlink.c | 2 +- net/core/fib_rules.c | 36 ++++- net/core/neighbour.c | 119 ++++++++++++--- net/core/net_namespace.c | 6 + net/core/rtnetlink.c | 318 ++++++++++++++++++++++++++++++++--------- net/ipv4/devinet.c | 101 ++++++++++--- net/ipv4/fib_frontend.c | 42 +++++- net/ipv4/ipmr.c | 39 +++++ net/ipv6/addrconf.c | 177 ++++++++++++++++++----- net/ipv6/addrlabel.c | 34 ++++- net/ipv6/ip6_fib.c | 8 ++ net/ipv6/ip6mr.c | 9 ++ net/ipv6/route.c | 2 +- net/mpls/af_mpls.c | 28 +++- net/netfilter/ipvs/ip_vs_ctl.c | 2 +- net/netlink/af_netlink.c | 33 ++++- net/netlink/af_netlink.h | 1 + net/sched/act_api.c | 2 +- net/sched/cls_api.c | 6 +- net/sched/sch_api.c | 2 +- net/xfrm/xfrm_user.c | 2 +- 27 files changed, 908 insertions(+), 165 deletions(-)
Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 1/23 netlink: Pass extack to dump handlers
From: David Ahern <[email protected]>
Declare extack in netlink_dump and pass to dump handlers via netlink_callback. Add any extack message after the dump_done_errno allowing error messages to be returned. This will be useful when strict checking is done on dump requests, returning why the dump fails EINVAL.
--- include/linux/netlink.h | 1 + net/netlink/af_netlink.c | 12 +++++++++++- 2 files changed, 12 insertions(+), 1 deletion(-)
include/linux/netlink.h +1 -0
@@ -176,6 +176,7 @@ struct netlink_callback {void *data;/* the module that dump function belong to */ struct module *module; +struct netlink_ext_ack *extack;u16 family;u16 min_dump_alloc;unsigned int prev_seq, seq;
net/netlink/af_netlink.c +11 -1
@@ -2171,6 +2171,7 @@ EXPORT_SYMBOL(__nlmsg_put);static int netlink_dump (struct sock *sk) {struct netlink_sock *nlk =nlk_sk (sk); +struct netlink_ext_ack extack = {};struct netlink_callback *cb;struct sk_buff *skb =NULL ;struct nlmsghdr *nlh;
@@ -2222,8 +2223,11 @@ static int netlink_dump(struct sock *sk)skb_reserve (skb,skb_tailroom (skb) - alloc_size);netlink_skb_set_owner_r (skb, sk); -if (nlk->dump_done_errno >0 ) +if (nlk->dump_done_errno >0 ) { + cb->extack = &extack; nlk->dump_done_errno = cb->dump (skb, cb); + cb->extack =NULL ; + }if (nlk->dump_done_errno >0 ||skb_tailroom (skb) <nlmsg_total_size (sizeof (nlk->dump_done_errno))) {
@@ -2246,6 +2250,12 @@ static int netlink_dump(struct sock *sk)memcpy (nlmsg_data (nlh), &nlk->dump_done_errno,sizeof (nlk->dump_done_errno)); +if (extack._msg && nlk->flags &NETLINK_F_EXT_ACK ) { + nlh->nlmsg_flags |=NLM_F_ACK_TLVS ; +if (!nla_put_string (skb,NLMSGERR_ATTR_MSG , extack._msg)) +nlmsg_end (skb, nlh); + } +if (sk_filter (sk, skb))kfree_skb (skb);else
Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 2/23 netlink: Add extack message to nlmsg_parse for invalid header length
In reply to David AhernFrom: David Ahern <[email protected]>
Give a user a reason why EINVAL is returned in nlmsg_parse.
--- include/net/netlink.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
include/net/netlink.h +3 -1
@@ -516,8 +516,10 @@ static inline int nlmsg_parse(const struct nlmsghdr *nlh, int hdrlen,const struct nla_policy *policy, struct netlink_ext_ack *extack) { - if (nlh->nlmsg_len < nlmsg_msg_size(hdrlen)) + if (nlh->nlmsg_len < nlmsg_msg_size(hdrlen)) { + NL_SET_ERR_MSG(extack, "Invalid header length");return -EINVAL ; + }return nla_parse (tb, maxtype,nlmsg_attrdata (nlh, hdrlen),nlmsg_attrlen (nlh, hdrlen), policy, extack);
Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 3/23 net: Add extack to nlmsg_parse
In reply to David AhernFrom: David Ahern <[email protected]>
Make sure extack is passed to nlmsg_parse where easy to do so. Most of these are dump handlers and leveraging the extack in the netlink_callback.
--- net/core/devlink.c | 2 +- net/core/neighbour.c | 3 ++- net/core/rtnetlink.c | 4 ++-- net/ipv4/devinet.c | 9 +++++---- net/ipv6/addrconf.c | 2 +- net/ipv6/route.c | 2 +- net/mpls/af_mpls.c | 2 +- net/netfilter/ipvs/ip_vs_ctl.c | 2 +- net/sched/act_api.c | 2 +- net/sched/cls_api.c | 6 ++++-- net/sched/sch_api.c | 2 +- net/xfrm/xfrm_user.c | 2 +- 12 files changed, 21 insertions(+), 17 deletions(-)
net/core/devlink.c +1 -1
@@ -3504,7 +3504,7 @@ static int devlink_nl_cmd_region_read_dumpit(struct sk_buff *skb, start_offset = *((u64 *)&cb->args[0 ]); err =nlmsg_parse (cb->nlh,GENL_HDRLEN + devlink_nl_family.hdrsize, - attrs,DEVLINK_ATTR_MAX , ops->policy,NULL ); + attrs,DEVLINK_ATTR_MAX , ops->policy, cb->extack);if (err) goto out;
net/core/neighbour.c +2 -1
@@ -2445,7 +2445,8 @@ static int neigh_dump_info(struct sk_buff *skb, struct netlink_callback *cb) ((struct ndmsg *)nlmsg_data(nlh))->ndm_flags == NTF_PROXY) proxy =1 ; - err =nlmsg_parse (nlh,sizeof (struct ndmsg ), tb,NDA_MAX ,NULL ,NULL ); + err =nlmsg_parse (nlh,sizeof (struct ndmsg ), tb,NDA_MAX ,NULL , + cb->extack);if (!err) {if (tb[NDA_IFINDEX ]) {if (nla_len (tb[NDA_IFINDEX ]) !=sizeof (u32))
net/core/rtnetlink.c +2 -2
@@ -1909,7 +1909,7 @@ static int rtnl_dump_ifinfo(struct sk_buff *skb, struct netlink_callback *cb) sizeof(struct rtgenmsg) : sizeof(struct ifinfomsg);if (nlmsg_parse (cb->nlh, hdrlen, tb,IFLA_MAX , - ifla_policy,NULL ) >=0 ) { + ifla_policy, cb->extack) >=0 ) {if (tb[IFLA_TARGET_NETNSID ]) { netnsid =nla_get_s32 (tb[IFLA_TARGET_NETNSID ]); tgt_net =rtnl_get_net_ns_capable (skb->sk, netnsid);
@@ -3774,7 +3774,7 @@ static int rtnl_fdb_dump(struct sk_buff *skb, struct netlink_callback *cb) (nlmsg_len(cb->nlh) != sizeof(struct ndmsg) + nla_attr_size(sizeof(u32)))) { err =nlmsg_parse (cb->nlh,sizeof (struct ifinfomsg ), tb, -IFLA_MAX , ifla_policy,NULL ); +IFLA_MAX , ifla_policy, cb->extack);if (err <0 ) {return -EINVAL ; }else if (err ==0 ) {
net/ipv4/devinet.c +5 -4
@@ -782,7 +782,8 @@ static void set_ifa_lifetime(struct in_ifaddr *ifa, __u32 valid_lft, }static struct in_ifaddr *rtm_to_ifaddr (struct net *net,struct nlmsghdr *nlh, -__u32 *pvalid_lft,__u32 *pprefered_lft) +__u32 *pvalid_lft,__u32 *pprefered_lft, +struct netlink_ext_ack *extack) {struct nlattr *tb[IFA_MAX +1 ];struct in_ifaddr *ifa;
@@ -792,7 +793,7 @@ static struct in_ifaddr *rtm_to_ifaddr(struct net *net, struct nlmsghdr *nlh,int err; err =nlmsg_parse (nlh,sizeof (*ifm), tb,IFA_MAX , ifa_ipv4_policy, -NULL ); + extack);if (err <0 ) goto errout;
@@ -897,7 +898,7 @@ static int inet_rtm_newaddr(struct sk_buff *skb, struct nlmsghdr *nlh,ASSERT_RTNL (); - ifa =rtm_to_ifaddr (net, nlh, &valid_lft, &prefered_lft); + ifa =rtm_to_ifaddr (net, nlh, &valid_lft, &prefered_lft, extack);if (IS_ERR (ifa))return PTR_ERR (ifa);
@@ -1684,7 +1685,7 @@ static int inet_dump_ifaddr(struct sk_buff *skb, struct netlink_callback *cb) s_ip_idx = ip_idx = cb->args[2 ];if (nlmsg_parse (cb->nlh,sizeof (struct ifaddrmsg ), tb,IFA_MAX , - ifa_ipv4_policy,NULL ) >=0 ) { + ifa_ipv4_policy, cb->extack) >=0 ) {if (tb[IFA_TARGET_NETNSID ]) { fillargs.netnsid =nla_get_s32 (tb[IFA_TARGET_NETNSID ]);
net/ipv6/addrconf.c +1 -1
@@ -5021,7 +5021,7 @@ static int inet6_dump_addr(struct sk_buff *skb, struct netlink_callback *cb, s_ip_idx = ip_idx = cb->args[2 ];if (nlmsg_parse (cb->nlh,sizeof (struct ifaddrmsg ), tb,IFA_MAX , - ifa_ipv6_policy,NULL ) >=0 ) { + ifa_ipv6_policy, cb->extack) >=0 ) {if (tb[IFA_TARGET_NETNSID ]) { netnsid =nla_get_s32 (tb[IFA_TARGET_NETNSID ]);
net/ipv6/route.c +1 -1
@@ -4117,7 +4117,7 @@ static int rtm_to_fib6_config(struct sk_buff *skb, struct nlmsghdr *nlh,int err; err =nlmsg_parse (nlh,sizeof (*rtm), tb,RTA_MAX , rtm_ipv6_policy, -NULL ); + extack);if (err <0 ) goto errout;
net/mpls/af_mpls.c +1 -1
@@ -1223,7 +1223,7 @@ static int mpls_netconf_get_devconf(struct sk_buff *in_skb,int err; err =nlmsg_parse (nlh,sizeof (*ncm), tb,NETCONFA_MAX , - devconf_mpls_policy,NULL ); + devconf_mpls_policy, extack);if (err <0 ) goto errout;
net/netfilter/ipvs/ip_vs_ctl.c +1 -1
@@ -3234,7 +3234,7 @@ static int ip_vs_genl_dump_dests(struct sk_buff *skb,/* Try to find the service for which to dump destinations */ if (nlmsg_parse (cb->nlh,GENL_HDRLEN , attrs,IPVS_CMD_ATTR_MAX , - ip_vs_cmd_policy,NULL )) + ip_vs_cmd_policy, cb->extack)) goto out_err;
net/sched/act_api.c +1 -1
@@ -1452,7 +1452,7 @@ static int tc_dump_action(struct sk_buff *skb, struct netlink_callback *cb)u32 act_count =0 ; ret =nlmsg_parse (cb->nlh,sizeof (struct tcamsg ), tb,TCA_ROOT_MAX , - tcaa_policy,NULL ); + tcaa_policy, cb->extack);if (ret <0 )return ret;
net/sched/cls_api.c +4 -2
@@ -1727,7 +1727,8 @@ static int tc_dump_tfilter(struct sk_buff *skb, struct netlink_callback *cb)if (nlmsg_len (cb->nlh) <sizeof (*tcm))return skb->len; - err =nlmsg_parse (cb->nlh,sizeof (*tcm), tca,TCA_MAX ,NULL ,NULL ); + err =nlmsg_parse (cb->nlh,sizeof (*tcm), tca,TCA_MAX ,NULL , + cb->extack);if (err)return err;
@@ -2054,7 +2055,8 @@ static int tc_dump_chain(struct sk_buff *skb, struct netlink_callback *cb)if (nlmsg_len (cb->nlh) <sizeof (*tcm))return skb->len; - err =nlmsg_parse (cb->nlh,sizeof (*tcm), tca,TCA_MAX ,NULL ,NULL ); + err =nlmsg_parse (cb->nlh,sizeof (*tcm), tca,TCA_MAX ,NULL , + cb->extack);if (err)return err;
net/sched/sch_api.c +1 -1
@@ -1671,7 +1671,7 @@ static int tc_dump_qdisc(struct sk_buff *skb, struct netlink_callback *cb)ASSERT_RTNL (); err =nlmsg_parse (nlh,sizeof (struct tcmsg ), tca,TCA_MAX , - rtm_tca_policy,NULL ); + rtm_tca_policy, cb->extack);if (err <0 )return err;
net/xfrm/xfrm_user.c +1 -1
@@ -1007,7 +1007,7 @@ static int xfrm_dump_sa(struct sk_buff *skb, struct netlink_callback *cb)int err; err =nlmsg_parse (cb->nlh,0 , attrs,XFRMA_MAX , xfrma_policy, -NULL ); + cb->extack);if (err <0 )return err;
Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 4/23 netlink: Add strict version of nlmsg_parse and nla_parse
In reply to David AhernFrom: David Ahern <[email protected]>
nla_parse is currently lenient on message parsing, allowing type to be 0 or greater than max expected and only logging a message
"netlink: %d bytes leftover after parsing attributes in process `%s'."
if the netlink message has unknown data at the end after parsing. What this could mean is that the header at the front of the attributes is actually wrong and the parsing is shifted from what is expected.
Add a new strict version that actually fails with EINVAL if there are any bytes remaining after the parsing loop completes, if the atttrbitue type is 0 or greater than max expected.
--- include/net/netlink.h | 17 +++++++++++++++++ lib/nlattr.c | 48 ++++++++++++++++++++++++++++++++++++------------ 2 files changed, 53 insertions(+), 12 deletions(-)
include/net/netlink.h +17 -0
@@ -373,6 +373,9 @@ int nla_validate(const struct nlattr *head, int len, int maxtype,int nla_parse (struct nlattr **tb,int maxtype,const struct nlattr *head,int len,const struct nla_policy *policy,struct netlink_ext_ack *extack); +int nla_parse_strict (struct nlattr **tb,int maxtype,const struct nlattr *head, +int len,const struct nla_policy *policy, +struct netlink_ext_ack *extack);int nla_policy_len (const struct nla_policy *,int );struct nlattr *nla_find (const struct nlattr *head,int len,int attrtype);size_t nla_strlcpy (char *dst,const struct nlattr *nla,size_t dstsize);
@@ -525,6 +528,20 @@ static inline int nlmsg_parse(const struct nlmsghdr *nlh, int hdrlen, nlmsg_attrlen(nlh, hdrlen), policy, extack); } +static inline int nlmsg_parse_strict (const struct nlmsghdr *nlh,int hdrlen, +struct nlattr *tb[],int maxtype, +const struct nla_policy *policy, +struct netlink_ext_ack *extack) +{ +if (nlh->nlmsg_len <nlmsg_msg_size (hdrlen)) { +NL_SET_ERR_MSG (extack,"Invalid header length" ); +return -EINVAL ; + } + +return nla_parse_strict (tb, maxtype,nlmsg_attrdata (nlh, hdrlen), +nlmsg_attrlen (nlh, hdrlen), policy, extack); +} +/** * nlmsg_find_attr - find a specific attribute in a netlink message * @nlh: netlink message header
lib/nlattr.c +36 -12
72 lines not on this page · raw message
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 04/23] netlink: Add strict version of nlmsg_parse and nla_parse
Quoted 11 lines · David Ahern
From: David Ahern <[email protected]>
nla_parseis currently lenient on message parsing, allowing type to be 0 or greater than max expected and only logging a message"netlink: %d bytes leftover after parsing attributes in process `%s'."
if the netlink message has unknown data at the end after parsing. What this could mean is that the header at the front of the attributes is actually wrong and the parsing is shifted from what is expected.
Quoted 5 lines
Add a new strict version that actually fails with EINVAL if there are any bytes remaining after the parsing loop completes, if the atttrbitue type is 0 or greater than max expected.
Signed-off-by David Ahern <[email protected]>
+1
Quoted 121 lines
--- include/net/netlink.h | 17 +++++++++++++++++ lib/nlattr.c | 48 ++++++++++++++++++++++++++++++++++++------------ 2 files changed, 53 insertions(+), 12 deletions(-)include/net/netlink.h +17
-0@@ -373,6 +373,9 @@ int nla_validate(const struct nlattr *head, int len, int maxtype,int nla_parse (struct nlattr **tb,int maxtype,const struct nlattr *head,int len,const struct nla_policy *policy,struct netlink_ext_ack *extack); +int nla_parse_strict (struct nlattr **tb,int maxtype,const struct nlattr *head, +int len,const struct nla_policy *policy, +struct netlink_ext_ack *extack);int nla_policy_len (const struct nla_policy *,int );struct nlattr *nla_find (const struct nlattr *head,int len,int attrtype);size_t nla_strlcpy (char *dst,const struct nlattr *nla,size_t dstsize);@@ -525,6 +528,20 @@ static inline int nlmsg_parse(const struct nlmsghdr *nlh, int hdrlen, nlmsg_attrlen(nlh, hdrlen), policy, extack); } +static inline int nlmsg_parse_strict (const struct nlmsghdr *nlh,int hdrlen, +struct nlattr *tb[],int maxtype, +const struct nla_policy *policy, +struct netlink_ext_ack *extack) +{ +if (nlh->nlmsg_len <nlmsg_msg_size (hdrlen)) { +NL_SET_ERR_MSG (extack,"Invalid header length" ); +return -EINVAL ; + } + +return nla_parse_strict (tb, maxtype,nlmsg_attrdata (nlh, hdrlen), +nlmsg_attrlen (nlh, hdrlen), policy, extack); +} +/** * nlmsg_find_attr - find a specific attribute in a netlink message * @nlh: netlink message header lib/nlattr.c +36
-12@@ -391,9 +391,10 @@ EXPORT_SYMBOL(nla_policy_len);* * Returns 0 on success or a negative error code. */ -int nla_parse (struct nlattr **tb,int maxtype,const struct nlattr *head, -int len,const struct nla_policy *policy, -struct netlink_ext_ack *extack) +static int __nla_parse (struct nlattr **tb,int maxtype, +const struct nlattr *head,int len, +bool strict,const struct nla_policy *policy, +struct netlink_ext_ack *extack) {const struct nlattr *nla;int rem;@@ -403,27 +404,50 @@ int nla_parse(struct nlattr **tb, int maxtype, const struct nlattr *head,nla_for_each_attr (nla, head, len, rem) {u16 type =nla_type (nla); -if (type >0 && type <= maxtype) { -if (policy) { -int err =validate_nla (nla, maxtype, policy, - extack); - -if (err <0 ) -return err; +if (type ==0 || type > maxtype) { +if (strict) { +NL_SET_ERR_MSG (extack,"Unknown attribute type" ); +return -EINVAL ; } +continue ; + } +if (policy) { +int err =validate_nla (nla, maxtype, policy, extack); - tb[type] = (struct nlattr *)nla; +if (err <0 ) +return err; } + + tb[type] = (struct nlattr *)nla; } -if (unlikely (rem >0 )) +if (unlikely (rem >0 )) {pr_warn_ratelimited ("netlink: %d bytes leftover after parsing attributes in process `%s'.\n" , rem, current->comm); +NL_SET_ERR_MSG (extack,"bytes leftover after parsing attributes" ); +if (strict) +return -EINVAL ; + }return 0 ; } + +int nla_parse (struct nlattr **tb,int maxtype,const struct nlattr *head, +int len,const struct nla_policy *policy, +struct netlink_ext_ack *extack) +{ +return __nla_parse (tb, maxtype, head, len, false, policy, extack); +}EXPORT_SYMBOL (nla_parse); +int nla_parse_strict (struct nlattr **tb,int maxtype,const struct nlattr *head, +int len,const struct nla_policy *policy, +struct netlink_ext_ack *extack) +{ +return __nla_parse (tb, maxtype, head, len, true, policy, extack); +} +EXPORT_SYMBOL (nla_parse_strict); +/** * nla_find - Find a specific attribute in a stream of attributes * @head: head of attribute stream Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 5/23 net/ipv6: Refactor address dump to push inet6_fill_args to in6_dump_addrs
In reply to David AhernFrom: David Ahern <[email protected]>
Pull the inet6_fill_args arg up to in6_dump_addrs and move netnsid into it.
--- net/ipv6/addrconf.c | 57 ++++++++++++++++++++++++++++------------------------- 1 file changed, 30 insertions(+), 27 deletions(-)
net/ipv6/addrconf.c +30 -27
@@ -4793,12 +4793,19 @@ static inline int inet6_ifaddr_msgsize(void) +nla_total_size (4 )/* IFA_RT_PRIORITY */ ; } +enum addr_type_t { +UNICAST_ADDR , +MULTICAST_ADDR , +ANYCAST_ADDR , +}; +struct inet6_fill_args {u32 portid;u32 seq;int event;unsigned int flags;int netnsid; +enum addr_type_t type; }; static int inet6_fill_ifaddr(struct sk_buff *skb, struct inet6_ifaddr *ifa,
@@ -4930,39 +4937,28 @@ static int inet6_fill_ifacaddr(struct sk_buff *skb, struct ifacaddr6 *ifaca,return 0 ; } -enum addr_type_t { -UNICAST_ADDR , -MULTICAST_ADDR , -ANYCAST_ADDR , -}; -/* called with rcu_read_lock() */ static int in6_dump_addrs (struct inet6_dev *idev,struct sk_buff *skb, -struct netlink_callback *cb,enum addr_type_t type, -int s_ip_idx,int *p_ip_idx,int netnsid) +struct netlink_callback *cb, +int s_ip_idx,int *p_ip_idx, +struct inet6_fill_args *fillargs) { -struct inet6_fill_args fillargs = { - .portid =NETLINK_CB (cb->skb).portid, - .seq = cb->nlh->nlmsg_seq, - .flags =NLM_F_MULTI , - .netnsid = netnsid, - };struct ifmcaddr6 *ifmca;struct ifacaddr6 *ifaca;int err =1 ;int ip_idx = *p_ip_idx;read_lock_bh (&idev->lock); -switch (type) { +switch (fillargs->type) {case UNICAST_ADDR : {struct inet6_ifaddr *ifa; - fillargs.event =RTM_NEWADDR ; + fillargs->event =RTM_NEWADDR ;/* unicast address incl. temp addr */ list_for_each_entry (ifa, &idev->addr_list, if_list) {if (++ip_idx < s_ip_idx)continue ; - err =inet6_fill_ifaddr (skb, ifa, &fillargs); + err =inet6_fill_ifaddr (skb, ifa, fillargs);if (err <0 )break ;nl_dump_check_consistent (cb,nlmsg_hdr (skb));
@@ -4970,26 +4966,26 @@ static int in6_dump_addrs(struct inet6_dev *idev, struct sk_buff *skb,break ; }case MULTICAST_ADDR : - fillargs.event =RTM_GETMULTICAST ; + fillargs->event =RTM_GETMULTICAST ;/* multicast address */ for (ifmca = idev->mc_list; ifmca; ifmca = ifmca->next, ip_idx++) {if (ip_idx < s_ip_idx)continue ; - err =inet6_fill_ifmcaddr (skb, ifmca, &fillargs); + err =inet6_fill_ifmcaddr (skb, ifmca, fillargs);if (err <0 )break ; }break ;case ANYCAST_ADDR : - fillargs.event =RTM_GETANYCAST ; + fillargs->event =RTM_GETANYCAST ;/* anycast address */ for (ifaca = idev->ac_list; ifaca; ifaca = ifaca->aca_next, ip_idx++) {if (ip_idx < s_ip_idx)continue ; - err =inet6_fill_ifacaddr (skb, ifaca, &fillargs); + err =inet6_fill_ifacaddr (skb, ifaca, fillargs);if (err <0 )break ; }
@@ -5005,10 +5001,16 @@ static int in6_dump_addrs(struct inet6_dev *idev, struct sk_buff *skb,static int inet6_dump_addr (struct sk_buff *skb,struct netlink_callback *cb,enum addr_type_t type) { +struct inet6_fill_args fillargs = { + .portid =NETLINK_CB (cb->skb).portid, + .seq = cb->nlh->nlmsg_seq, + .flags =NLM_F_MULTI , + .netnsid =-1 , + .type = type, + };struct net *net =sock_net (skb->sk);struct nlattr *tb[IFA_MAX +1 ];struct net *tgt_net = net; -int netnsid =-1 ;int h, s_h;int idx, ip_idx;int s_idx, s_ip_idx;
@@ -5023,9 +5025,10 @@ static int inet6_dump_addr(struct sk_buff *skb, struct netlink_callback *cb,if (nlmsg_parse (cb->nlh,sizeof (struct ifaddrmsg ), tb,IFA_MAX , ifa_ipv6_policy, cb->extack) >=0 ) {if (tb[IFA_TARGET_NETNSID ]) { - netnsid =nla_get_s32 (tb[IFA_TARGET_NETNSID ]); + fillargs.netnsid =nla_get_s32 (tb[IFA_TARGET_NETNSID ]); - tgt_net =rtnl_get_net_ns_capable (skb->sk, netnsid); + tgt_net =rtnl_get_net_ns_capable (skb->sk, + fillargs.netnsid);if (IS_ERR (tgt_net))return PTR_ERR (tgt_net); }
@@ -5046,8 +5049,8 @@ static int inet6_dump_addr(struct sk_buff *skb, struct netlink_callback *cb,if (!idev) goto cont; -if (in6_dump_addrs (idev, skb, cb, type, - s_ip_idx, &ip_idx, netnsid) <0 ) +if (in6_dump_addrs (idev, skb, cb, s_ip_idx, &ip_idx, + &fillargs) <0 ) goto done; cont: idx++;
@@ -5058,7 +5061,7 @@ static int inet6_dump_addr(struct sk_buff *skb, struct netlink_callback *cb, cb->args[0 ] = h; cb->args[1 ] = idx; cb->args[2 ] = ip_idx; -if (netnsid >=0 ) +if (fillargs.netnsid >=0 )put_net (tgt_net);return skb->len;
Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 6/23 netlink: Add new socket option to enable strict checking on dumps
In reply to David AhernFrom: David Ahern <[email protected]>
Add a new socket option, NETLINK_DUMP_STRICT_CHK, that userspace can use via setsockopt to request strict checking of headers and attributes on dump requests.
To get dump features such as kernel side filtering based on data in the header or attributes appended to the dump request, userspace must call setsockopt() for NETLINK_DUMP_STRICT_CHK and a non-zero value. Since the netlink sock and its flags are private to the af_netlink code, the strict checking flag is passed to dump handlers via a flag in the netlink_callback struct.
For old userspace on new kernel there is no impact as all of the data checks in later patches are wrapped in a check on the new strict flag.
For new userspace on old kernel, the setsockopt will fail and even if new userspace sets data in the headers and appended attributes the kernel will silently ignore it. Moving forward when the setsockopt succeeds, the new userspace on old kernel means the dump request can pass an attribute the kernel does not understand. The dump will then fail as the older kernel does not understand it.
New userspace on new kernel setting the socket option gets the benefit of the improved data dump.
Kernel side the NETLINK_DUMP_STRICT_CHK uapi is converted to a generic NETLINK_F_STRICT_CHK flag which can potentially be leveraged for tighter checking on the NEW, DEL, and SET commands.
--- include/linux/netlink.h | 1 + include/uapi/linux/netlink.h | 1 + net/netlink/af_netlink.c | 21 ++++++++++++++++++++- net/netlink/af_netlink.h | 1 + 4 files changed, 23 insertions(+), 1 deletion(-)
include/linux/netlink.h +1 -0
@@ -179,6 +179,7 @@ struct netlink_callback {struct netlink_ext_ack *extack;u16 family;u16 min_dump_alloc; +bool strict_check;unsigned int prev_seq, seq;long args[6 ]; };
include/uapi/linux/netlink.h +1 -0
@@ -155,6 +155,7 @@ enum nlmsgerr_attrs {#define NETLINK_LIST_MEMBERSHIPS 9#define NETLINK_CAP_ACK 10#define NETLINK_EXT_ACK 11 +#define NETLINK_DUMP_STRICT_CHK 12struct nl_pktinfo {__u32 group;
net/netlink/af_netlink.c +20 -1
@@ -1706,6 +1706,13 @@ static int netlink_setsockopt(struct socket *sock, int level, int optname, nlk->flags &= ~NETLINK_F_EXT_ACK ; err =0 ;break ; +case NETLINK_DUMP_STRICT_CHK : +if (val) + nlk->flags |=NETLINK_F_STRICT_CHK ; +else + nlk->flags &= ~NETLINK_F_STRICT_CHK ; + err =0 ; +break ;default : err = -ENOPROTOOPT ; }
@@ -1799,6 +1806,15 @@ static int netlink_getsockopt(struct socket *sock, int level, int optname,return -EFAULT ; err =0 ;break ; +case NETLINK_DUMP_STRICT_CHK : +if (len <sizeof (int )) +return -EINVAL ; + len =sizeof (int ); + val = nlk->flags &NETLINK_F_STRICT_CHK ?1 :0 ; +if (put_user (len, optlen) ||put_user (val, optval)) +return -EFAULT ; + err =0 ; +break ;default : err = -ENOPROTOOPT ; }
@@ -2282,9 +2298,9 @@ int __netlink_dump_start(struct sock *ssk, struct sk_buff *skb,const struct nlmsghdr *nlh, struct netlink_dump_control *control) { + struct netlink_sock *nlk, *nlk2;struct netlink_callback *cb;struct sock *sk; -struct netlink_sock *nlk;int ret;refcount_inc (&skb->users);
@@ -2318,6 +2334,9 @@ int __netlink_dump_start(struct sock *ssk, struct sk_buff *skb, cb->min_dump_alloc = control->min_dump_alloc; cb->skb = skb; + nlk2 =nlk_sk (NETLINK_CB (skb).sk); + cb->strict_check = !!(nlk2->flags &NETLINK_F_STRICT_CHK ); +if (control->start) { ret = control->start (cb);if (ret)
net/netlink/af_netlink.h +1 -0
@@ -15,6 +15,7 @@#define NETLINK_F_LISTEN_ALL_NSID 0x10#define NETLINK_F_CAP_ACK 0x20#define NETLINK_F_EXT_ACK 0x40 +#define NETLINK_F_STRICT_CHK 0x80#define NLGRPSZ (x) (ALIGN(x, sizeof(unsigned long) * 8) / 8)#define NLGRPLONGS (x) (NLGRPSZ(x)/sizeof(unsigned long))
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 06/23] netlink: Add new socket option to enable strict checking on dumps
Quoted 23 lines · David Ahern
From: David Ahern <[email protected]>
Add a new socket option,
NETLINK_DUMP_STRICT_CHK, that userspace can use via setsockopt to request strict checking of headers and attributes on dump requests.To get dump features such as kernel side filtering based on data in the header or attributes appended to the dump request, userspace must call
setsockopt()forNETLINK_DUMP_STRICT_CHKand a non-zero value. Since the netlink sock and its flags are private to theaf_netlinkcode, the strict checking flag is passed to dump handlers via a flag in thenetlink_callbackstruct.For old userspace on new kernel there is no impact as all of the data checks in later patches are wrapped in a check on the new strict flag.
For new userspace on old kernel, the setsockopt will fail and even if new userspace sets data in the headers and appended attributes the kernel will silently ignore it. Moving forward when the setsockopt succeeds, the new userspace on old kernel means the dump request can pass an attribute the kernel does not understand. The dump will then fail as the older kernel does not understand it.
Quoted 8 lines
New userspace on new kernel setting the socket option gets the benefit of the improved data dump.
Kernel side the
NETLINK_DUMP_STRICT_CHKuapi is converted to a genericNETLINK_F_STRICT_CHKflag which can potentially be leveraged for tighter checking on the NEW, DEL, and SET commands.Signed-off-by David Ahern <[email protected]>
Thanks for the bool. :)
Quoted 101 lines
--- include/linux/netlink.h | 1 + include/uapi/linux/netlink.h | 1 + net/netlink/af_netlink.c | 21 ++++++++++++++++++++- net/netlink/af_netlink.h | 1 + 4 files changed, 23 insertions(+), 1 deletion(-)include/linux/netlink.h +1
-0@@ -179,6 +179,7 @@ struct netlink_callback {struct netlink_ext_ack *extack;u16 family;u16 min_dump_alloc; +bool strict_check;unsigned int prev_seq, seq;long args[6 ]; };include/uapi/linux/netlink.h +1
-0@@ -155,6 +155,7 @@ enum nlmsgerr_attrs {#define NETLINK_LIST_MEMBERSHIPS 9#define NETLINK_CAP_ACK 10#define NETLINK_EXT_ACK 11 +#define NETLINK_DUMP_STRICT_CHK 12struct nl_pktinfo {__u32 group;net/netlink/af_netlink.c +20
-1@@ -1706,6 +1706,13 @@ static int netlink_setsockopt(struct socket *sock, int level, int optname, nlk->flags &= ~NETLINK_F_EXT_ACK ; err =0 ;break ; +case NETLINK_DUMP_STRICT_CHK : +if (val) + nlk->flags |=NETLINK_F_STRICT_CHK ; +else + nlk->flags &= ~NETLINK_F_STRICT_CHK ; + err =0 ; +break ;default : err = -ENOPROTOOPT ; }@@ -1799,6 +1806,15 @@ static int netlink_getsockopt(struct socket *sock, int level, int optname,return -EFAULT ; err =0 ;break ; +case NETLINK_DUMP_STRICT_CHK : +if (len <sizeof (int )) +return -EINVAL ; + len =sizeof (int ); + val = nlk->flags &NETLINK_F_STRICT_CHK ?1 :0 ; +if (put_user (len, optlen) ||put_user (val, optval)) +return -EFAULT ; + err =0 ; +break ;default : err = -ENOPROTOOPT ; }@@ -2282,9 +2298,9 @@ int __netlink_dump_start(struct sock *ssk, struct sk_buff *skb,const struct nlmsghdr *nlh, struct netlink_dump_control *control) { + struct netlink_sock *nlk, *nlk2;struct netlink_callback *cb;struct sock *sk; -struct netlink_sock *nlk;int ret;refcount_inc (&skb->users);@@ -2318,6 +2334,9 @@ int __netlink_dump_start(struct sock *ssk, struct sk_buff *skb, cb->min_dump_alloc = control->min_dump_alloc; cb->skb = skb; + nlk2 =nlk_sk (NETLINK_CB (skb).sk); + cb->strict_check = !!(nlk2->flags &NETLINK_F_STRICT_CHK ); +if (control->start) { ret = control->start (cb);if (ret)net/netlink/af_netlink.h +1
-0@@ -15,6 +15,7 @@#define NETLINK_F_LISTEN_ALL_NSID 0x10#define NETLINK_F_CAP_ACK 0x20#define NETLINK_F_EXT_ACK 0x40 +#define NETLINK_F_STRICT_CHK 0x80#define NLGRPSZ (x) (ALIGN(x, sizeof(unsigned long) * 8) / 8)#define NLGRPLONGS (x) (NLGRPSZ(x)/sizeof(unsigned long))Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 7/23 net/ipv4: Update inet_dump_ifaddr for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update inet_dump_ifaddr for strict data checking. If the flag is set, the dump request is expected to have an ifaddrmsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values supported by the dump handler are allowed to be non-0 or set in the request. At the moment only the IFA_TARGET_NETNSID attribute is supported. Follow on patches can support for other fields (e.g., honor ifa_index and only return data for the given device index).
--- net/ipv4/devinet.c | 72 +++++++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 61 insertions(+), 11 deletions(-)
net/ipv4/devinet.c +61 -11
@@ -1660,17 +1660,70 @@ static int inet_fill_ifaddr(struct sk_buff *skb, struct in_ifaddr *ifa,return -EMSGSIZE ; } +static int inet_valid_dump_ifaddr_req (const struct nlmsghdr *nlh, +struct inet_fill_args *fillargs, +struct net **tgt_net,struct sock *sk, +struct netlink_ext_ack *extack) +{ +struct nlattr *tb[IFA_MAX +1 ]; +struct ifaddrmsg *ifm; +int err, i; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid header for address dump request" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->ifa_prefixlen || ifm->ifa_flags || ifm->ifa_scope) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid values in header for address dump request" ); +return -EINVAL ; + } +if (ifm->ifa_index) { +NL_SET_ERR_MSG (extack,"ipv4: Filter by device index not supported for address dump" ); +return -EINVAL ; + } + + err =nlmsg_parse_strict (nlh,sizeof (*ifm), tb,IFA_MAX , + ifa_ipv4_policy, extack); +if (err <0 ) +return err; + +for (i =0 ; i <=IFA_MAX ; ++i) { +if (!tb[i]) +continue ; + +if (i ==IFA_TARGET_NETNSID ) { +struct net *net; + + fillargs->netnsid =nla_get_s32 (tb[i]); + + net =rtnl_get_net_ns_capable (sk, fillargs->netnsid); +if (IS_ERR (net)) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid target network namespace id" ); +return PTR_ERR (net); + } + *tgt_net = net; + }else { +NL_SET_ERR_MSG (extack,"ipv4: Unsupported attribute in dump request" ); +return -EINVAL ; + } + } + +return 0 ; +} +static int inet_dump_ifaddr (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct inet_fill_args fillargs = { .portid =NETLINK_CB (cb->skb).portid, - .seq = cb->nlh->nlmsg_seq, + .seq = nlh->nlmsg_seq, .event =RTM_NEWADDR , .flags =NLM_F_MULTI , .netnsid =-1 , };struct net *net =sock_net (skb->sk); -struct nlattr *tb[IFA_MAX +1 ];struct net *tgt_net = net;int h, s_h;int idx, s_idx;
@@ -1684,16 +1737,13 @@ static int inet_dump_ifaddr(struct sk_buff *skb, struct netlink_callback *cb) s_idx = idx = cb->args[1 ]; s_ip_idx = ip_idx = cb->args[2 ]; -if (nlmsg_parse (cb->nlh,sizeof (struct ifaddrmsg ), tb,IFA_MAX , - ifa_ipv4_policy, cb->extack) >=0 ) { -if (tb[IFA_TARGET_NETNSID ]) { - fillargs.netnsid =nla_get_s32 (tb[IFA_TARGET_NETNSID ]); +if (cb->strict_check) { +int err; - tgt_net =rtnl_get_net_ns_capable (skb->sk, - fillargs.netnsid); -if (IS_ERR (tgt_net)) -return PTR_ERR (tgt_net); - } + err =inet_valid_dump_ifaddr_req (nlh, &fillargs, &tgt_net, + skb->sk, cb->extack); +if (err <0 ) +return err; }for (h = s_h; h <NETDEV_HASHENTRIES ; h++, s_idx =0 ) {
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 07/23] net/ipv4: Update inet_dump_ifaddr for strict data checking
Quoted 11 lines · David Ahern
From: David Ahern <[email protected]>
Update
inet_dump_ifaddrfor strict data checking. If the flag is set, the dump request is expected to have an ifaddrmsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values supported by the dump handler are allowed to be non-0 or set in the request. At the moment only theIFA_TARGET_NETNSIDattribute is supported. Follow on patches can support for other fields (e.g., honorifa_indexand only return data for the given device index).
Quoted 1 line
Signed-off-by David Ahern <[email protected]>
Thanks, with the *_strict() it looks way cleaner now.
Quoted 107 lines
--- net/ipv4/devinet.c | 72 +++++++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 61 insertions(+), 11 deletions(-)net/ipv4/devinet.c +61
-11@@ -1660,17 +1660,70 @@ static int inet_fill_ifaddr(struct sk_buff *skb, struct in_ifaddr *ifa,return -EMSGSIZE ; } +static int inet_valid_dump_ifaddr_req (const struct nlmsghdr *nlh, +struct inet_fill_args *fillargs, +struct net **tgt_net,struct sock *sk, +struct netlink_ext_ack *extack) +{ +struct nlattr *tb[IFA_MAX +1 ]; +struct ifaddrmsg *ifm; +int err, i; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid header for address dump request" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->ifa_prefixlen || ifm->ifa_flags || ifm->ifa_scope) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid values in header for address dump request" ); +return -EINVAL ; + } +if (ifm->ifa_index) { +NL_SET_ERR_MSG (extack,"ipv4: Filter by device index not supported for address dump" ); +return -EINVAL ; + } + + err =nlmsg_parse_strict (nlh,sizeof (*ifm), tb,IFA_MAX , + ifa_ipv4_policy, extack); +if (err <0 ) +return err; + +for (i =0 ; i <=IFA_MAX ; ++i) { +if (!tb[i]) +continue ; + +if (i ==IFA_TARGET_NETNSID ) { +struct net *net; + + fillargs->netnsid =nla_get_s32 (tb[i]); + + net =rtnl_get_net_ns_capable (sk, fillargs->netnsid); +if (IS_ERR (net)) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid target network namespace id" ); +return PTR_ERR (net); + } + *tgt_net = net; + }else { +NL_SET_ERR_MSG (extack,"ipv4: Unsupported attribute in dump request" ); +return -EINVAL ; + } + } + +return 0 ; +} +static int inet_dump_ifaddr (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct inet_fill_args fillargs = { .portid =NETLINK_CB (cb->skb).portid, - .seq = cb->nlh->nlmsg_seq, + .seq = nlh->nlmsg_seq, .event =RTM_NEWADDR , .flags =NLM_F_MULTI , .netnsid =-1 , };struct net *net =sock_net (skb->sk); -struct nlattr *tb[IFA_MAX +1 ];struct net *tgt_net = net;int h, s_h;int idx, s_idx;@@ -1684,16 +1737,13 @@ static int inet_dump_ifaddr(struct sk_buff *skb, struct netlink_callback *cb) s_idx = idx = cb->args[1 ]; s_ip_idx = ip_idx = cb->args[2 ]; -if (nlmsg_parse (cb->nlh,sizeof (struct ifaddrmsg ), tb,IFA_MAX , - ifa_ipv4_policy, cb->extack) >=0 ) { -if (tb[IFA_TARGET_NETNSID ]) { - fillargs.netnsid =nla_get_s32 (tb[IFA_TARGET_NETNSID ]); +if (cb->strict_check) { +int err; - tgt_net =rtnl_get_net_ns_capable (skb->sk, - fillargs.netnsid); -if (IS_ERR (tgt_net)) -return PTR_ERR (tgt_net); - } + err =inet_valid_dump_ifaddr_req (nlh, &fillargs, &tgt_net, + skb->sk, cb->extack); +if (err <0 ) +return err; }for (h = s_h; h <NETDEV_HASHENTRIES ; h++, s_idx =0 ) {Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 8/23 net/ipv6: Update inet6_dump_addr for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update inet6_dump_addr for strict data checking. If the flag is set, the dump request is expected to have an ifaddrmsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values suppored by the dump handler are allowed to be non-0 or set in the request. At the moment only the IFA_TARGET_NETNSID attribute is supported. Follow on patches can add support for other fields (e.g., honor ifa_index and only return data for the given device index).
--- net/ipv6/addrconf.c | 69 +++++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 59 insertions(+), 10 deletions(-)
net/ipv6/addrconf.c +59 -10
@@ -4998,9 +4998,62 @@ static int in6_dump_addrs(struct inet6_dev *idev, struct sk_buff *skb,return err; } +static int inet6_valid_dump_ifaddr_req (const struct nlmsghdr *nlh, +struct inet6_fill_args *fillargs, +struct net **tgt_net,struct sock *sk, +struct netlink_ext_ack *extack) +{ +struct nlattr *tb[IFA_MAX +1 ]; +struct ifaddrmsg *ifm; +int err, i; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for address dump request" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->ifa_prefixlen || ifm->ifa_flags || ifm->ifa_scope) { +NL_SET_ERR_MSG_MOD (extack,"Invalid values in header for address dump request" ); +return -EINVAL ; + } +if (ifm->ifa_index) { +NL_SET_ERR_MSG_MOD (extack,"Filter by device index not supported for address dump" ); +return -EINVAL ; + } + + err =nlmsg_parse_strict (nlh,sizeof (*ifm), tb,IFA_MAX , + ifa_ipv6_policy, extack); +if (err <0 ) +return err; + +for (i =0 ; i <=IFA_MAX ; ++i) { +if (!tb[i]) +continue ; + +if (i ==IFA_TARGET_NETNSID ) { +struct net *net; + + fillargs->netnsid =nla_get_s32 (tb[i]); + net =rtnl_get_net_ns_capable (sk, fillargs->netnsid); +if (IS_ERR (net)) { +NL_SET_ERR_MSG_MOD (extack,"Invalid target network namespace id" ); +return PTR_ERR (net); + } + *tgt_net = net; + }else { +NL_SET_ERR_MSG_MOD (extack,"Unsupported attribute in dump request" ); +return -EINVAL ; + } + } + +return 0 ; +} +static int inet6_dump_addr (struct sk_buff *skb,struct netlink_callback *cb,enum addr_type_t type) { +const struct nlmsghdr *nlh = cb->nlh;struct inet6_fill_args fillargs = { .portid =NETLINK_CB (cb->skb).portid, .seq = cb->nlh->nlmsg_seq,
@@ -5009,7 +5062,6 @@ static int inet6_dump_addr(struct sk_buff *skb, struct netlink_callback *cb, .type = type, };struct net *net =sock_net (skb->sk); -struct nlattr *tb[IFA_MAX +1 ];struct net *tgt_net = net;int h, s_h;int idx, ip_idx;
@@ -5022,16 +5074,13 @@ static int inet6_dump_addr(struct sk_buff *skb, struct netlink_callback *cb, s_idx = idx = cb->args[1 ]; s_ip_idx = ip_idx = cb->args[2 ]; -if (nlmsg_parse (cb->nlh,sizeof (struct ifaddrmsg ), tb,IFA_MAX , - ifa_ipv6_policy, cb->extack) >=0 ) { -if (tb[IFA_TARGET_NETNSID ]) { - fillargs.netnsid =nla_get_s32 (tb[IFA_TARGET_NETNSID ]); +if (cb->strict_check) { +int err; - tgt_net =rtnl_get_net_ns_capable (skb->sk, - fillargs.netnsid); -if (IS_ERR (tgt_net)) -return PTR_ERR (tgt_net); - } + err =inet6_valid_dump_ifaddr_req (nlh, &fillargs, &tgt_net, + skb->sk, cb->extack); +if (err <0 ) +return err; }rcu_read_lock ();
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 08/23] net/ipv6: Update inet6_dump_addr for strict data checking
Quoted 11 lines · David Ahern
From: David Ahern <[email protected]>
Update
inet6_dump_addrfor strict data checking. If the flag is set, the dump request is expected to have an ifaddrmsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values suppored by the dump handler are allowed to be non-0 or set in the request. At the moment only theIFA_TARGET_NETNSIDattribute is supported. Follow on patches can add support for other fields (e.g., honorifa_indexand only return data for the given device index).
Quoted 1 line
Signed-off-by David Ahern <[email protected]>
Same as ipv4, looks way cleaner with the new *_strict() helper! :)
Quoted 105 lines
--- net/ipv6/addrconf.c | 69 +++++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 59 insertions(+), 10 deletions(-)net/ipv6/addrconf.c +59
-10@@ -4998,9 +4998,62 @@ static int in6_dump_addrs(struct inet6_dev *idev, struct sk_buff *skb,return err; } +static int inet6_valid_dump_ifaddr_req (const struct nlmsghdr *nlh, +struct inet6_fill_args *fillargs, +struct net **tgt_net,struct sock *sk, +struct netlink_ext_ack *extack) +{ +struct nlattr *tb[IFA_MAX +1 ]; +struct ifaddrmsg *ifm; +int err, i; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for address dump request" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->ifa_prefixlen || ifm->ifa_flags || ifm->ifa_scope) { +NL_SET_ERR_MSG_MOD (extack,"Invalid values in header for address dump request" ); +return -EINVAL ; + } +if (ifm->ifa_index) { +NL_SET_ERR_MSG_MOD (extack,"Filter by device index not supported for address dump" ); +return -EINVAL ; + } + + err =nlmsg_parse_strict (nlh,sizeof (*ifm), tb,IFA_MAX , + ifa_ipv6_policy, extack); +if (err <0 ) +return err; + +for (i =0 ; i <=IFA_MAX ; ++i) { +if (!tb[i]) +continue ; + +if (i ==IFA_TARGET_NETNSID ) { +struct net *net; + + fillargs->netnsid =nla_get_s32 (tb[i]); + net =rtnl_get_net_ns_capable (sk, fillargs->netnsid); +if (IS_ERR (net)) { +NL_SET_ERR_MSG_MOD (extack,"Invalid target network namespace id" ); +return PTR_ERR (net); + } + *tgt_net = net; + }else { +NL_SET_ERR_MSG_MOD (extack,"Unsupported attribute in dump request" ); +return -EINVAL ; + } + } + +return 0 ; +} +static int inet6_dump_addr (struct sk_buff *skb,struct netlink_callback *cb,enum addr_type_t type) { +const struct nlmsghdr *nlh = cb->nlh;struct inet6_fill_args fillargs = { .portid =NETLINK_CB (cb->skb).portid, .seq = cb->nlh->nlmsg_seq,@@ -5009,7 +5062,6 @@ static int inet6_dump_addr(struct sk_buff *skb, struct netlink_callback *cb, .type = type, };struct net *net =sock_net (skb->sk); -struct nlattr *tb[IFA_MAX +1 ];struct net *tgt_net = net;int h, s_h;int idx, ip_idx;@@ -5022,16 +5074,13 @@ static int inet6_dump_addr(struct sk_buff *skb, struct netlink_callback *cb, s_idx = idx = cb->args[1 ]; s_ip_idx = ip_idx = cb->args[2 ]; -if (nlmsg_parse (cb->nlh,sizeof (struct ifaddrmsg ), tb,IFA_MAX , - ifa_ipv6_policy, cb->extack) >=0 ) { -if (tb[IFA_TARGET_NETNSID ]) { - fillargs.netnsid =nla_get_s32 (tb[IFA_TARGET_NETNSID ]); +if (cb->strict_check) { +int err; - tgt_net =rtnl_get_net_ns_capable (skb->sk, - fillargs.netnsid); -if (IS_ERR (tgt_net)) -return PTR_ERR (tgt_net); - } + err =inet6_valid_dump_ifaddr_req (nlh, &fillargs, &tgt_net, + skb->sk, cb->extack); +if (err <0 ) +return err; }rcu_read_lock ();Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 9/23 rtnetlink: Update rtnl_dump_ifinfo for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update rtnl_dump_ifinfo for strict data checking. If the flag is set, the dump request is expected to have an ifinfomsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values supported by the dump handler are allowed to be non-0 or set in the request. At the moment only the IFA_TARGET_NETNSID, IFLA_EXT_MASK, IFLA_MASTER, and IFLA_LINKINFO attributes are supported.
Existing code does not fail the dump if nlmsg_parse fails. That behavior is kept for non-strict checking.
--- net/core/rtnetlink.c | 113 +++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 83 insertions(+), 30 deletions(-)
net/core/rtnetlink.c +83 -30
@@ -1878,8 +1878,52 @@ struct net *rtnl_get_net_ns_capable(struct sock *sk, int netnsid) }EXPORT_SYMBOL_GPL (rtnl_get_net_ns_capable); +static int rtnl_valid_dump_ifinfo_req (const struct nlmsghdr *nlh, +bool strict_check,struct nlattr **tb, +struct netlink_ext_ack *extack) +{ +int hdrlen; + +if (strict_check) { +struct ifinfomsg *ifm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG (extack,"Invalid header for link dump" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->__ifi_pad || ifm->ifi_type || ifm->ifi_flags || + ifm->ifi_change) { +NL_SET_ERR_MSG (extack,"Invalid values in header for link dump request" ); +return -EINVAL ; + } +if (ifm->ifi_index) { +NL_SET_ERR_MSG (extack,"Filter by device index not supported for link dumps" ); +return -EINVAL ; + } + +return nlmsg_parse_strict (nlh,sizeof (*ifm), tb,IFLA_MAX , + ifla_policy, extack); + } + +/* A hack to preserve kernel<->userspace interface. +* The correct header is ifinfomsg. It is consistent with rtnl_getlink. +* However, before Linux v3.9 the code here assumed rtgenmsg and that's +* what iproute2 < v3.9.0 used. +* We can detect the old iproute2. Even including the IFLA_EXT_MASK +* attribute, its netlink message is shorter than struct ifinfomsg. +*/ + hdrlen =nlmsg_len (nlh) <sizeof (struct ifinfomsg ) ? +sizeof (struct rtgenmsg ) :sizeof (struct ifinfomsg ); + +return nlmsg_parse (nlh, hdrlen, tb,IFLA_MAX , ifla_policy, extack); +} +static int rtnl_dump_ifinfo (struct sk_buff *skb,struct netlink_callback *cb) { +struct netlink_ext_ack *extack = cb->extack; +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct net *tgt_net = net;int h, s_h;
@@ -1892,44 +1936,54 @@ static int rtnl_dump_ifinfo(struct sk_buff *skb, struct netlink_callback *cb)unsigned int flags =NLM_F_MULTI ;int master_idx =0 ;int netnsid =-1 ; -int err; -int hdrlen; +int err, i; s_h = cb->args[0 ]; s_idx = cb->args[1 ]; -/* A hack to preserve kernel<->userspace interface. -* The correct header is ifinfomsg. It is consistent with rtnl_getlink. -* However, before Linux v3.9 the code here assumed rtgenmsg and that's -* what iproute2 < v3.9.0 used. -* We can detect the old iproute2. Even including the IFLA_EXT_MASK -* attribute, its netlink message is shorter than struct ifinfomsg. -*/ - hdrlen =nlmsg_len (cb->nlh) <sizeof (struct ifinfomsg ) ? -sizeof (struct rtgenmsg ) :sizeof (struct ifinfomsg ); + err =rtnl_valid_dump_ifinfo_req (nlh, cb->strict_check, tb, extack); +if (err <0 ) { +if (cb->strict_check) +return err; + + goto walk_entries; + } + +for (i =0 ; i <=IFLA_MAX ; ++i) { +if (!tb[i]) +continue ; -if (nlmsg_parse (cb->nlh, hdrlen, tb,IFLA_MAX , - ifla_policy, cb->extack) >=0 ) { -if (tb[IFLA_TARGET_NETNSID ]) { - netnsid =nla_get_s32 (tb[IFLA_TARGET_NETNSID ]); +/* new attributes should only be added with strict checking */ +switch (i) { +case IFLA_TARGET_NETNSID : + netnsid =nla_get_s32 (tb[i]); tgt_net =rtnl_get_net_ns_capable (skb->sk, netnsid); -if (IS_ERR (tgt_net)) +if (IS_ERR (tgt_net)) { +NL_SET_ERR_MSG (extack,"Invalid target network namespace id" );return PTR_ERR (tgt_net); + } +break ; +case IFLA_EXT_MASK : + ext_filter_mask =nla_get_u32 (tb[i]); +break ; +case IFLA_MASTER : + master_idx =nla_get_u32 (tb[i]); +break ; +case IFLA_LINKINFO : + kind_ops =linkinfo_to_kind_ops (tb[i]); +break ; +default : +if (cb->strict_check) { +NL_SET_ERR_MSG (extack,"Unsupported attribute in link dump request" ); +return -EINVAL ; + } } - -if (tb[IFLA_EXT_MASK ]) - ext_filter_mask =nla_get_u32 (tb[IFLA_EXT_MASK ]); - -if (tb[IFLA_MASTER ]) - master_idx =nla_get_u32 (tb[IFLA_MASTER ]); - -if (tb[IFLA_LINKINFO ]) - kind_ops =linkinfo_to_kind_ops (tb[IFLA_LINKINFO ]); - -if (master_idx || kind_ops) - flags |=NLM_F_DUMP_FILTERED ; } +if (master_idx || kind_ops) + flags |=NLM_F_DUMP_FILTERED ; + +walk_entries:for (h = s_h; h <NETDEV_HASHENTRIES ; h++, s_idx =0 ) { idx =0 ; head = &tgt_net->dev_index_head[h];
@@ -1941,8 +1995,7 @@ static int rtnl_dump_ifinfo(struct sk_buff *skb, struct netlink_callback *cb) err =rtnl_fill_ifinfo (skb, dev, net,RTM_NEWLINK ,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq,0 , - flags, + nlh->nlmsg_seq,0 , flags, ext_filter_mask,0 ,NULL ,0 , netnsid);
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 09/23] rtnetlink: Update rtnl_dump_ifinfo for strict data checking
Quoted 10 lines · David Ahern
From: David Ahern <[email protected]>
Update
rtnl_dump_ifinfofor strict data checking. If the flag is set, the dump request is expected to have an ifinfomsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values supported by the dump handler are allowed to be non-0 or set in the request. At the moment only theIFA_TARGET_NETNSID,IFLA_EXT_MASK,IFLA_MASTER, andIFLA_LINKINFOattributes are supported.
Quoted 4 lines
Existing code does not fail the dump if
nlmsg_parsefails. That behavior is kept for non-strict checking.Signed-off-by David Ahern <[email protected]>
Quoted 157 lines
--- net/core/rtnetlink.c | 113 +++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 83 insertions(+), 30 deletions(-)net/core/rtnetlink.c +83
-30@@ -1878,8 +1878,52 @@ struct net *rtnl_get_net_ns_capable(struct sock *sk, int netnsid) }EXPORT_SYMBOL_GPL (rtnl_get_net_ns_capable); +static int rtnl_valid_dump_ifinfo_req (const struct nlmsghdr *nlh, +bool strict_check,struct nlattr **tb, +struct netlink_ext_ack *extack) +{ +int hdrlen; + +if (strict_check) { +struct ifinfomsg *ifm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG (extack,"Invalid header for link dump" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->__ifi_pad || ifm->ifi_type || ifm->ifi_flags || + ifm->ifi_change) { +NL_SET_ERR_MSG (extack,"Invalid values in header for link dump request" ); +return -EINVAL ; + } +if (ifm->ifi_index) { +NL_SET_ERR_MSG (extack,"Filter by device index not supported for link dumps" ); +return -EINVAL ; + } + +return nlmsg_parse_strict (nlh,sizeof (*ifm), tb,IFLA_MAX , + ifla_policy, extack); + } + +/* A hack to preserve kernel<->userspace interface. +* The correct header is ifinfomsg. It is consistent with rtnl_getlink. +* However, before Linux v3.9 the code here assumed rtgenmsg and that's +* what iproute2 < v3.9.0 used. +* We can detect the old iproute2. Even including the IFLA_EXT_MASK +* attribute, its netlink message is shorter than struct ifinfomsg. +*/ + hdrlen =nlmsg_len (nlh) <sizeof (struct ifinfomsg ) ? +sizeof (struct rtgenmsg ) :sizeof (struct ifinfomsg ); + +return nlmsg_parse (nlh, hdrlen, tb,IFLA_MAX , ifla_policy, extack); +} +static int rtnl_dump_ifinfo (struct sk_buff *skb,struct netlink_callback *cb) { +struct netlink_ext_ack *extack = cb->extack; +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct net *tgt_net = net;int h, s_h;@@ -1892,44 +1936,54 @@ static int rtnl_dump_ifinfo(struct sk_buff *skb, struct netlink_callback *cb)unsigned int flags =NLM_F_MULTI ;int master_idx =0 ;int netnsid =-1 ; -int err; -int hdrlen; +int err, i; s_h = cb->args[0 ]; s_idx = cb->args[1 ]; -/* A hack to preserve kernel<->userspace interface. -* The correct header is ifinfomsg. It is consistent with rtnl_getlink. -* However, before Linux v3.9 the code here assumed rtgenmsg and that's -* what iproute2 < v3.9.0 used. -* We can detect the old iproute2. Even including the IFLA_EXT_MASK -* attribute, its netlink message is shorter than struct ifinfomsg. -*/ - hdrlen =nlmsg_len (cb->nlh) <sizeof (struct ifinfomsg ) ? -sizeof (struct rtgenmsg ) :sizeof (struct ifinfomsg ); + err =rtnl_valid_dump_ifinfo_req (nlh, cb->strict_check, tb, extack); +if (err <0 ) { +if (cb->strict_check) +return err; + + goto walk_entries; + } + +for (i =0 ; i <=IFLA_MAX ; ++i) { +if (!tb[i]) +continue ; -if (nlmsg_parse (cb->nlh, hdrlen, tb,IFLA_MAX , - ifla_policy, cb->extack) >=0 ) { -if (tb[IFLA_TARGET_NETNSID ]) { - netnsid =nla_get_s32 (tb[IFLA_TARGET_NETNSID ]); +/* new attributes should only be added with strict checking */ +switch (i) { +case IFLA_TARGET_NETNSID : + netnsid =nla_get_s32 (tb[i]); tgt_net =rtnl_get_net_ns_capable (skb->sk, netnsid); -if (IS_ERR (tgt_net)) +if (IS_ERR (tgt_net)) { +NL_SET_ERR_MSG (extack,"Invalid target network namespace id" );return PTR_ERR (tgt_net); + } +break ; +case IFLA_EXT_MASK : + ext_filter_mask =nla_get_u32 (tb[i]); +break ; +case IFLA_MASTER : + master_idx =nla_get_u32 (tb[i]); +break ; +case IFLA_LINKINFO : + kind_ops =linkinfo_to_kind_ops (tb[i]); +break ; +default : +if (cb->strict_check) { +NL_SET_ERR_MSG (extack,"Unsupported attribute in link dump request" ); +return -EINVAL ; + } } - -if (tb[IFLA_EXT_MASK ]) - ext_filter_mask =nla_get_u32 (tb[IFLA_EXT_MASK ]); - -if (tb[IFLA_MASTER ]) - master_idx =nla_get_u32 (tb[IFLA_MASTER ]); - -if (tb[IFLA_LINKINFO ]) - kind_ops =linkinfo_to_kind_ops (tb[IFLA_LINKINFO ]); - -if (master_idx || kind_ops) - flags |=NLM_F_DUMP_FILTERED ; } +if (master_idx || kind_ops) + flags |=NLM_F_DUMP_FILTERED ; + +walk_entries:for (h = s_h; h <NETDEV_HASHENTRIES ; h++, s_idx =0 ) { idx =0 ; head = &tgt_net->dev_index_head[h];@@ -1941,8 +1995,7 @@ static int rtnl_dump_ifinfo(struct sk_buff *skb, struct netlink_callback *cb) err =rtnl_fill_ifinfo (skb, dev, net,RTM_NEWLINK ,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq,0 , - flags, + nlh->nlmsg_seq,0 , flags, ext_filter_mask,0 ,NULL ,0 , netnsid);Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 10/23 rtnetlink: Update rtnl_bridge_getlink for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update rtnl_bridge_getlink for strict data checking. If the flag is set, the dump request is expected to have an ifinfomsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values supported by the dump handler are allowed to be non-0 or set in the request. At the moment only the IFLA_EXT_MASK attribute is supported.
--- net/core/rtnetlink.c | 70 ++++++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 57 insertions(+), 13 deletions(-)
net/core/rtnetlink.c +57 -13
@@ -4021,28 +4021,72 @@ int ndo_dflt_bridge_getlink(struct sk_buff *skb, u32 pid, u32 seq, }EXPORT_SYMBOL_GPL (ndo_dflt_bridge_getlink); +static int valid_bridge_getlink_req (const struct nlmsghdr *nlh, +bool strict_check,u32 *filter_mask, +struct netlink_ext_ack *extack) +{ +struct nlattr *tb[IFLA_MAX +1 ]; +int err, i; + +if (strict_check) { +struct ifinfomsg *ifm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG (extack,"Invalid header for bridge link dump" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->__ifi_pad || ifm->ifi_type || ifm->ifi_flags || + ifm->ifi_change || ifm->ifi_index) { +NL_SET_ERR_MSG (extack,"Invalid values in header for bridge link dump request" ); +return -EINVAL ; + } + + err =nlmsg_parse_strict (nlh,sizeof (struct ifinfomsg ), tb, +IFLA_MAX , ifla_policy, extack); + }else { + err =nlmsg_parse (nlh,sizeof (struct ifinfomsg ), tb, +IFLA_MAX , ifla_policy, extack); + } +if (err <0 ) +return err; + +/* new attributes should only be added with strict checking */ +for (i =0 ; i <=IFLA_MAX ; ++i) { +if (!tb[i]) +continue ; + +switch (i) { +case IFLA_EXT_MASK : + *filter_mask =nla_get_u32 (tb[i]); +break ; +default : +if (strict_check) { +NL_SET_ERR_MSG (extack,"Unsupported attribute in bridge link dump request" ); +return -EINVAL ; + } + } + } + +return 0 ; +} +static int rtnl_bridge_getlink (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct net_device *dev;int idx =0 ;u32 portid =NETLINK_CB (cb->skb).portid; -u32 seq = cb->nlh->nlmsg_seq; +u32 seq = nlh->nlmsg_seq;u32 filter_mask =0 ;int err; -if (nlmsg_len (cb->nlh) >sizeof (struct ifinfomsg )) { -struct nlattr *extfilt; - - extfilt =nlmsg_find_attr (cb->nlh,sizeof (struct ifinfomsg ), -IFLA_EXT_MASK ); -if (extfilt) { -if (nla_len (extfilt) <sizeof (filter_mask)) -return -EINVAL ; - - filter_mask =nla_get_u32 (extfilt); - } - } + err =valid_bridge_getlink_req (nlh, cb->strict_check, &filter_mask, + cb->extack); +if (err <0 && cb->strict_check) +return err;rcu_read_lock ();for_each_netdev_rcu (net, dev) {
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 10/23] rtnetlink: Update rtnl_bridge_getlink for strict data checking
Quoted 11 lines · David Ahern
From: David Ahern <[email protected]>
Update
rtnl_bridge_getlinkfor strict data checking. If the flag is set, the dump request is expected to have an ifinfomsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values supported by the dump handler are allowed to be non-0 or set in the request. At the moment only theIFLA_EXT_MASKattribute is supported.Signed-off-by David Ahern <[email protected]>
Quoted 97 lines
--- net/core/rtnetlink.c | 70 ++++++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 57 insertions(+), 13 deletions(-)net/core/rtnetlink.c +57
-13@@ -4021,28 +4021,72 @@ int ndo_dflt_bridge_getlink(struct sk_buff *skb, u32 pid, u32 seq, }EXPORT_SYMBOL_GPL (ndo_dflt_bridge_getlink); +static int valid_bridge_getlink_req (const struct nlmsghdr *nlh, +bool strict_check,u32 *filter_mask, +struct netlink_ext_ack *extack) +{ +struct nlattr *tb[IFLA_MAX +1 ]; +int err, i; + +if (strict_check) { +struct ifinfomsg *ifm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG (extack,"Invalid header for bridge link dump" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->__ifi_pad || ifm->ifi_type || ifm->ifi_flags || + ifm->ifi_change || ifm->ifi_index) { +NL_SET_ERR_MSG (extack,"Invalid values in header for bridge link dump request" ); +return -EINVAL ; + } + + err =nlmsg_parse_strict (nlh,sizeof (struct ifinfomsg ), tb, +IFLA_MAX , ifla_policy, extack); + }else { + err =nlmsg_parse (nlh,sizeof (struct ifinfomsg ), tb, +IFLA_MAX , ifla_policy, extack); + } +if (err <0 ) +return err; + +/* new attributes should only be added with strict checking */ +for (i =0 ; i <=IFLA_MAX ; ++i) { +if (!tb[i]) +continue ; + +switch (i) { +case IFLA_EXT_MASK : + *filter_mask =nla_get_u32 (tb[i]); +break ; +default : +if (strict_check) { +NL_SET_ERR_MSG (extack,"Unsupported attribute in bridge link dump request" ); +return -EINVAL ; + } + } + } + +return 0 ; +} +static int rtnl_bridge_getlink (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct net_device *dev;int idx =0 ;u32 portid =NETLINK_CB (cb->skb).portid; -u32 seq = cb->nlh->nlmsg_seq; +u32 seq = nlh->nlmsg_seq;u32 filter_mask =0 ;int err; -if (nlmsg_len (cb->nlh) >sizeof (struct ifinfomsg )) { -struct nlattr *extfilt; - - extfilt =nlmsg_find_attr (cb->nlh,sizeof (struct ifinfomsg ), -IFLA_EXT_MASK ); -if (extfilt) { -if (nla_len (extfilt) <sizeof (filter_mask)) -return -EINVAL ; - - filter_mask =nla_get_u32 (extfilt); - } - } + err =valid_bridge_getlink_req (nlh, cb->strict_check, &filter_mask, + cb->extack); +if (err <0 && cb->strict_check) +return err;rcu_read_lock ();for_each_netdev_rcu (net, dev) {Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 11/23 rtnetlink: Update rtnl_stats_dump for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update rtnl_stats_dump for strict data checking. If the flag is set, the dump request is expected to have an if_stats_msg struct as the header. All elements of the struct are expected to be 0 except filter_mask which must be non-0 (legacy behavior). No attributes are supported.
--- net/core/rtnetlink.c | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-)
net/core/rtnetlink.c +22 -2
@@ -4680,6 +4680,7 @@ static int rtnl_stats_get(struct sk_buff *skb, struct nlmsghdr *nlh,static int rtnl_stats_dump (struct sk_buff *skb,struct netlink_callback *cb) { +struct netlink_ext_ack *extack = cb->extack;int h, s_h, err, s_idx, s_idxattr, s_prividx;struct net *net =sock_net (skb->sk);unsigned int flags =NLM_F_MULTI ;
@@ -4696,13 +4697,32 @@ static int rtnl_stats_dump(struct sk_buff *skb, struct netlink_callback *cb) cb->seq = net->dev_base_seq; -if (nlmsg_len (cb->nlh) <sizeof (*ifsm)) +if (nlmsg_len (cb->nlh) <sizeof (*ifsm)) { +NL_SET_ERR_MSG (extack,"Invalid header for stats dump" );return -EINVAL ; + } ifsm =nlmsg_data (cb->nlh); + +/* only requests using NLM_F_DUMP_PROPER_HDR can pass data to +* influence the dump. The legacy exception is filter_mask. +*/ +if (cb->strict_check) { +if (ifsm->pad1 || ifsm->pad2 || ifsm->ifindex) { +NL_SET_ERR_MSG (extack,"Invalid values in header for stats dump request" ); +return -EINVAL ; + } +if (nlmsg_attrlen (cb->nlh,sizeof (*ifsm))) { +NL_SET_ERR_MSG (extack,"Invalid attributes after stats header" ); +return -EINVAL ; + } + } + filter_mask = ifsm->filter_mask; -if (!filter_mask) +if (!filter_mask) { +NL_SET_ERR_MSG (extack,"Filter mask must be set for stats dump" );return -EINVAL ; + }for (h = s_h; h <NETDEV_HASHENTRIES ; h++, s_idx =0 ) { idx =0 ;
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 11/23] rtnetlink: Update rtnl_stats_dump for strict data checking
Quoted 27 lines · David Ahern
From: David Ahern <[email protected]>
Update
rtnl_stats_dumpfor strict data checking. If the flag is set, the dump request is expected to have anif_stats_msgstruct as the header. All elements of the struct are expected to be 0 exceptfilter_maskwhich must be non-0 (legacy behavior). No attributes are supported.Signed-off-by David Ahern <[email protected]>--- net/core/rtnetlink.c | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-)net/core/rtnetlink.c +1
-0@@ -4680,6 +4680,7 @@ static int rtnl_stats_get(struct sk_buff *skb, struct nlmsghdr *nlh,static int rtnl_stats_dump (struct sk_buff *skb,struct netlink_callback *cb) { +struct netlink_ext_ack *extack = cb->extack;int h, s_h, err, s_idx, s_idxattr, s_prividx;struct net *net =sock_net (skb->sk);unsigned int flags =NLM_F_MULTI ;@@ -4696,13 +4697,32 @@ static int rtnl_stats_dump(struct sk_buff *skb, struct netlink_callback *cb) cb->seq = net->dev_base_seq;
net/core/rtnetlink.c static int rtnl_stats_dump(struct sk_buff *skb, struct netlink_callback *cb) · line 4707
Quoted 10 lines
net/core/rtnetlink.c +5
-1-if (nlmsg_len (cb->nlh) <sizeof (*ifsm)) +if (nlmsg_len (cb->nlh) <sizeof (*ifsm)) { +NL_SET_ERR_MSG (extack,"Invalid header for stats dump" );return -EINVAL ; + } ifsm =nlmsg_data (cb->nlh); + +/* only requests using NLM_F_DUMP_PROPER_HDR can pass data to
That looks like an accidental leftover before we changed this to a socket option. :)
Quoted 25 lines
net/core/rtnetlink.c +16
-1+* influence the dump. The legacy exception is filter_mask. +*/ +if (cb->strict_check) { +if (ifsm->pad1 || ifsm->pad2 || ifsm->ifindex) { +NL_SET_ERR_MSG (extack,"Invalid values in header for stats dump request" ); +return -EINVAL ; + } +if (nlmsg_attrlen (cb->nlh,sizeof (*ifsm))) { +NL_SET_ERR_MSG (extack,"Invalid attributes after stats header" ); +return -EINVAL ; + } + } + filter_mask = ifsm->filter_mask; -if (!filter_mask) +if (!filter_mask) { +NL_SET_ERR_MSG (extack,"Filter mask must be set for stats dump" );return -EINVAL ; + }for (h = s_h; h <NETDEV_HASHENTRIES ; h++, s_idx =0 ) { idx =0 ;Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 11/23] rtnetlink: Update rtnl_stats_dump for strict data checking
Quoted 10 lines · Christian Brauner
Quoted 10 lines
net/core/rtnetlink.c +3
-1@@ -4696,13 +4697,32 @@ static int rtnl_stats_dump(struct sk_buff *skb, struct netlink_callback *cb) cb->seq = net->dev_base_seq; -if (nlmsg_len (cb->nlh) <sizeof (*ifsm)) +if (nlmsg_len (cb->nlh) <sizeof (*ifsm)) { +NL_SET_ERR_MSG (extack,"Invalid header for stats dump" );return -EINVAL ; + }
Quoted 7 lines
net/core/rtnetlink.c static int rtnl_stats_dump(struct sk_buff *skb, struct netlink_callback *cb) · line 4707
Quoted 3 lines
net/core/rtnetlink.c +2
-0ifsm =nlmsg_data (cb->nlh); + +/* only requests using NLM_F_DUMP_PROPER_HDR can pass data to That looks like an accidental leftover before we changed this to a socket option. :)
ugh. thanks for noticing.
David Miller
maintainerRe: [PATCH v2 net-next 11/23] rtnetlink: Update rtnl_stats_dump for strict data checking
From: David Ahern <[email protected]>
Date: Mon, 8 Oct 2018 07:25:34 -0600
Quoted 19 lines · Christian Brauner
Quoted 10 lines
Quoted 10 lines
net/core/rtnetlink.c +3
-1@@ -4696,13 +4697,32 @@ static int rtnl_stats_dump(struct sk_buff *skb, struct netlink_callback *cb) cb->seq = net->dev_base_seq; -if (nlmsg_len (cb->nlh) <sizeof (*ifsm)) +if (nlmsg_len (cb->nlh) <sizeof (*ifsm)) { +NL_SET_ERR_MSG (extack,"Invalid header for stats dump" );return -EINVAL ; + }Quoted 7 lines
net/core/rtnetlink.c static int rtnl_stats_dump(struct sk_buff *skb, struct netlink_callback *cb) · line 4707
Quoted 3 lines
net/core/rtnetlink.c +2
-0ifsm =nlmsg_data (cb->nlh); + +/* only requests using NLM_F_DUMP_PROPER_HDR can pass data to That looks like an accidental leftover before we changed this to a socket option. :)
Quoted 1 line
ugh. thanks for noticing.
David, I applied this series, please send me relative fixups at this point if necessary.
Thanks.
David Ahern
maintainerPATCH v2 12/23 rtnetlink: Update inet6_dump_ifinfo for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update inet6_dump_ifinfo for strict data checking. If the flag is set, the dump request is expected to have an ifinfomsg struct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.
--- net/ipv6/addrconf.c | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+)
net/ipv6/addrconf.c +35 -0
@@ -5644,6 +5644,31 @@ static int inet6_fill_ifinfo(struct sk_buff *skb, struct inet6_dev *idev,return -EMSGSIZE ; } +static int inet6_valid_dump_ifinfo (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct ifinfomsg *ifm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for link dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ifm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid data after header" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->__ifi_pad || ifm->ifi_type || ifm->ifi_flags || + ifm->ifi_change || ifm->ifi_index) { +NL_SET_ERR_MSG_MOD (extack,"Invalid values in header for dump request" ); +return -EINVAL ; + } + +return 0 ; +} +static int inet6_dump_ifinfo (struct sk_buff *skb,struct netlink_callback *cb) {struct net *net =sock_net (skb->sk);
@@ -5653,6 +5678,16 @@ static int inet6_dump_ifinfo(struct sk_buff *skb, struct netlink_callback *cb)struct inet6_dev *idev;struct hlist_head *head; +/* only requests using strict checking can pass data to +* influence the dump +*/ +if (cb->strict_check) { +int err =inet6_valid_dump_ifinfo (cb->nlh, cb->extack); + +if (err <0 ) +return err; + } + s_h = cb->args[0 ]; s_idx = cb->args[1 ];
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 12/23] rtnetlink: Update inet6_dump_ifinfo for strict data checking
Quoted 8 lines · David Ahern
From: David Ahern <[email protected]>
Update
inet6_dump_ifinfofor strict data checking. If the flag is set, the dump request is expected to have an ifinfomsg struct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.Signed-off-by David Ahern <[email protected]>
Quoted 60 lines
--- net/ipv6/addrconf.c | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+)net/ipv6/addrconf.c +35
-0@@ -5644,6 +5644,31 @@ static int inet6_fill_ifinfo(struct sk_buff *skb, struct inet6_dev *idev,return -EMSGSIZE ; } +static int inet6_valid_dump_ifinfo (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct ifinfomsg *ifm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for link dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ifm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid data after header" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->__ifi_pad || ifm->ifi_type || ifm->ifi_flags || + ifm->ifi_change || ifm->ifi_index) { +NL_SET_ERR_MSG_MOD (extack,"Invalid values in header for dump request" ); +return -EINVAL ; + } + +return 0 ; +} +static int inet6_dump_ifinfo (struct sk_buff *skb,struct netlink_callback *cb) {struct net *net =sock_net (skb->sk);@@ -5653,6 +5678,16 @@ static int inet6_dump_ifinfo(struct sk_buff *skb, struct netlink_callback *cb)struct inet6_dev *idev;struct hlist_head *head; +/* only requests using strict checking can pass data to +* influence the dump +*/ +if (cb->strict_check) { +int err =inet6_valid_dump_ifinfo (cb->nlh, cb->extack); + +if (err <0 ) +return err; + } + s_h = cb->args[0 ]; s_idx = cb->args[1 ];Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 13/23 rtnetlink: Update ipmr_rtm_dumplink for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update ipmr_rtm_dumplink for strict data checking. If the flag is set, the dump request is expected to have an ifinfomsg struct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.
--- net/ipv4/ipmr.c | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+)
net/ipv4/ipmr.c +32 -0
@@ -2710,6 +2710,31 @@ static bool ipmr_fill_vif(struct mr_table *mrt, u32 vifid, struct sk_buff *skb)return true; } +static int ipmr_valid_dumplink (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct ifinfomsg *ifm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid header for ipmr link dump" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ifm))) { +NL_SET_ERR_MSG (extack,"Invalid data after header in ipmr link dump" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->__ifi_pad || ifm->ifi_type || ifm->ifi_flags || + ifm->ifi_change || ifm->ifi_index) { +NL_SET_ERR_MSG (extack,"Invalid values in header for ipmr link dump request" ); +return -EINVAL ; + } + +return 0 ; +} +static int ipmr_rtm_dumplink (struct sk_buff *skb,struct netlink_callback *cb) {struct net *net =sock_net (skb->sk);
@@ -2718,6 +2743,13 @@ static int ipmr_rtm_dumplink(struct sk_buff *skb, struct netlink_callback *cb)unsigned int e =0 , s_e;struct mr_table *mrt; +if (cb->strict_check) { +int err =ipmr_valid_dumplink (cb->nlh, cb->extack); + +if (err <0 ) +return err; + } + s_t = cb->args[0 ]; s_e = cb->args[1 ];
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 13/23] rtnetlink: Update ipmr_rtm_dumplink for strict data checking
Quoted 8 lines · David Ahern
From: David Ahern <[email protected]>
Update
ipmr_rtm_dumplinkfor strict data checking. If the flag is set, the dump request is expected to have an ifinfomsg struct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.Signed-off-by David Ahern <[email protected]>
Quoted 57 lines
--- net/ipv4/ipmr.c | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+)net/ipv4/ipmr.c +32
-0@@ -2710,6 +2710,31 @@ static bool ipmr_fill_vif(struct mr_table *mrt, u32 vifid, struct sk_buff *skb)return true; } +static int ipmr_valid_dumplink (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct ifinfomsg *ifm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifm))) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid header for ipmr link dump" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ifm))) { +NL_SET_ERR_MSG (extack,"Invalid data after header in ipmr link dump" ); +return -EINVAL ; + } + + ifm =nlmsg_data (nlh); +if (ifm->__ifi_pad || ifm->ifi_type || ifm->ifi_flags || + ifm->ifi_change || ifm->ifi_index) { +NL_SET_ERR_MSG (extack,"Invalid values in header for ipmr link dump request" ); +return -EINVAL ; + } + +return 0 ; +} +static int ipmr_rtm_dumplink (struct sk_buff *skb,struct netlink_callback *cb) {struct net *net =sock_net (skb->sk);@@ -2718,6 +2743,13 @@ static int ipmr_rtm_dumplink(struct sk_buff *skb, struct netlink_callback *cb)unsigned int e =0 , s_e;struct mr_table *mrt; +if (cb->strict_check) { +int err =ipmr_valid_dumplink (cb->nlh, cb->extack); + +if (err <0 ) +return err; + } + s_t = cb->args[0 ]; s_e = cb->args[1 ];Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 14/23 rtnetlink: Update fib dumps for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Add helper to check netlink message for route dumps. If the strict flag is set the dump request is expected to have an rtmsg struct as the header. All elements of the struct are expected to be 0 with the exception of rtm_flags (which is used by both ipv4 and ipv6 dumps) and no attributes can be appended. rtm_flags can only have RTM_F_CLONED and RTM_F_PREFIX set.
Update inet_dump_fib, inet6_dump_fib, mpls_dump_routes, ipmr_rtm_dumproute, and ip6mr_rtm_dumproute to call this helper if strict data checking is enabled.
--- include/net/ip_fib.h | 2 ++ net/ipv4/fib_frontend.c | 42 ++++++++++++++++++++++++++++++++++++++++-- net/ipv4/ipmr.c | 7 +++++++ net/ipv6/ip6_fib.c | 8 ++++++++ net/ipv6/ip6mr.c | 9 +++++++++ net/mpls/af_mpls.c | 8 ++++++++ 6 files changed, 74 insertions(+), 2 deletions(-)
include/net/ip_fib.h +2 -0
@@ -452,4 +452,6 @@ static inline void fib_proc_exit(struct net *net)u32 ip_mtu_from_fib_result (struct fib_result *res,__be32 daddr); +int ip_valid_fib_dump_req (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack);#endif /* _NET_FIB_H */
net/ipv4/fib_frontend.c +40 -2
56 lines not on this page · raw message
net/ipv4/ipmr.c +7 -0
@@ -2527,6 +2527,13 @@ static int ipmr_rtm_getroute(struct sk_buff *in_skb, struct nlmsghdr *nlh,static int ipmr_rtm_dumproute (struct sk_buff *skb,struct netlink_callback *cb) { +if (cb->strict_check) { +int err =ip_valid_fib_dump_req (cb->nlh, cb->extack); + +if (err <0 ) +return err; + } +return mr_rtm_dumproute (skb, cb, ipmr_mr_table_iter, _ipmr_fill_mroute, &mfc_unres_lock); }
net/ipv6/ip6_fib.c +8 -0
@@ -564,6 +564,7 @@ static int fib6_dump_table(struct fib6_table *table, struct sk_buff *skb,static int inet6_dump_fib (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);unsigned int h, s_h;unsigned int e =0 , s_e;
@@ -573,6 +574,13 @@ static int inet6_dump_fib(struct sk_buff *skb, struct netlink_callback *cb)struct hlist_head *head;int res =0 ; +if (cb->strict_check) { +int err =ip_valid_fib_dump_req (nlh, cb->extack); + +if (err <0 ) +return err; + } + s_h = cb->args[0 ]; s_e = cb->args[1 ];
net/ipv6/ip6mr.c +9 -0
@@ -2457,6 +2457,15 @@ static void mrt6msg_netlink_event(struct mr_table *mrt, struct sk_buff *pkt)static int ip6mr_rtm_dumproute (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh; + +if (cb->strict_check) { +int err =ip_valid_fib_dump_req (nlh, cb->extack); + +if (err <0 ) +return err; + } +return mr_rtm_dumproute (skb, cb, ip6mr_mr_table_iter, _ip6mr_fill_mroute, &mfc_unres_lock); }
net/mpls/af_mpls.c +8 -0
@@ -2017,6 +2017,7 @@ static int mpls_dump_route(struct sk_buff *skb, u32 portid, u32 seq, int event,static int mpls_dump_routes (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct mpls_route __rcu **platform_label;size_t platform_labels;
@@ -2024,6 +2025,13 @@ static int mpls_dump_routes(struct sk_buff *skb, struct netlink_callback *cb)ASSERT_RTNL (); +if (cb->strict_check) { +int err =ip_valid_fib_dump_req (nlh, cb->extack); + +if (err <0 ) +return err; + } + index = cb->args[0 ];if (index <MPLS_LABEL_FIRST_UNRESERVED ) index =MPLS_LABEL_FIRST_UNRESERVED ;
Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 15/23 net/neighbor: Update neigh_dump_info for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update neigh_dump_info for strict data checking. If the flag is set, the dump request is expected to have an ndmsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values supported by the dump handler are allowed to be non-0 or set in the request. At the moment only the NDA_IFINDEX and NDA_MASTER attributes are supported.
Existing code does not fail the dump if nlmsg_parse fails. That behavior is kept for non-strict checking.
--- net/core/neighbour.c | 82 ++++++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 67 insertions(+), 15 deletions(-)
net/core/neighbour.c +67 -15
@@ -2426,11 +2426,73 @@ static int pneigh_dump_table(struct neigh_table *tbl, struct sk_buff *skb, } +static int neigh_valid_dump_req (const struct nlmsghdr *nlh, +bool strict_check, +struct neigh_dump_filter *filter, +struct netlink_ext_ack *extack) +{ +struct nlattr *tb[NDA_MAX +1 ]; +int err, i; + +if (strict_check) { +struct ndmsg *ndm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ndm))) { +NL_SET_ERR_MSG (extack,"Invalid header for neighbor dump request" ); +return -EINVAL ; + } + + ndm =nlmsg_data (nlh); +if (ndm->ndm_pad1 || ndm->ndm_pad2 || ndm->ndm_ifindex || + ndm->ndm_state || ndm->ndm_flags || ndm->ndm_type) { +NL_SET_ERR_MSG (extack,"Invalid values in header for neighbor dump request" ); +return -EINVAL ; + } + + err =nlmsg_parse_strict (nlh,sizeof (struct ndmsg ), tb,NDA_MAX , +NULL , extack); + }else { + err =nlmsg_parse (nlh,sizeof (struct ndmsg ), tb,NDA_MAX , +NULL , extack); + } +if (err <0 ) +return err; + +for (i =0 ; i <=NDA_MAX ; ++i) { +if (!tb[i]) +continue ; + +/* all new attributes should require strict_check */ +switch (i) { +case NDA_IFINDEX : +if (nla_len (tb[i]) !=sizeof (u32)) { +NL_SET_ERR_MSG (extack,"Invalid IFINDEX attribute in neighbor dump request" ); +return -EINVAL ; + } + filter->dev_idx =nla_get_u32 (tb[i]); +break ; +case NDA_MASTER : +if (nla_len (tb[i]) !=sizeof (u32)) { +NL_SET_ERR_MSG (extack,"Invalid MASTER attribute in neighbor dump request" ); +return -EINVAL ; + } + filter->master_idx =nla_get_u32 (tb[i]); +break ; +default : +if (strict_check) { +NL_SET_ERR_MSG (extack,"Unsupported attribute in neighbor dump request" ); +return -EINVAL ; + } + } + } + +return 0 ; +} +static int neigh_dump_info (struct sk_buff *skb,struct netlink_callback *cb) {const struct nlmsghdr *nlh = cb->nlh;struct neigh_dump_filter filter = {}; -struct nlattr *tb[NDA_MAX +1 ];struct neigh_table *tbl;int t, family, s_t;int proxy =0 ;
@@ -2445,20 +2507,10 @@ static int neigh_dump_info(struct sk_buff *skb, struct netlink_callback *cb) ((struct ndmsg *)nlmsg_data(nlh))->ndm_flags == NTF_PROXY) proxy =1 ; - err =nlmsg_parse (nlh,sizeof (struct ndmsg ), tb,NDA_MAX ,NULL , - cb->extack); -if (!err) { -if (tb[NDA_IFINDEX ]) { -if (nla_len (tb[NDA_IFINDEX ]) !=sizeof (u32)) -return -EINVAL ; - filter.dev_idx =nla_get_u32 (tb[NDA_IFINDEX ]); - } -if (tb[NDA_MASTER ]) { -if (nla_len (tb[NDA_MASTER ]) !=sizeof (u32)) -return -EINVAL ; - filter.master_idx =nla_get_u32 (tb[NDA_MASTER ]); - } - } + err =neigh_valid_dump_req (nlh, cb->strict_check, &filter, cb->extack); +if (err <0 && cb->strict_check) +return err; + s_t = cb->args[0 ];for (t =0 ; t <NEIGH_NR_TABLES ; t++) {
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 15/23] net/neighbor: Update neigh_dump_info for strict data checking
Quoted 10 lines · David Ahern
From: David Ahern <[email protected]>
Update
neigh_dump_infofor strict data checking. If the flag is set, the dump request is expected to have an ndmsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values supported by the dump handler are allowed to be non-0 or set in the request. At the moment only theNDA_IFINDEXandNDA_MASTERattributes are supported.
Quoted 4 lines
Existing code does not fail the dump if
nlmsg_parsefails. That behavior is kept for non-strict checking.Signed-off-by David Ahern <[email protected]>
Quoted 111 lines
--- net/core/neighbour.c | 82 ++++++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 67 insertions(+), 15 deletions(-)net/core/neighbour.c +67
-15@@ -2426,11 +2426,73 @@ static int pneigh_dump_table(struct neigh_table *tbl, struct sk_buff *skb, } +static int neigh_valid_dump_req (const struct nlmsghdr *nlh, +bool strict_check, +struct neigh_dump_filter *filter, +struct netlink_ext_ack *extack) +{ +struct nlattr *tb[NDA_MAX +1 ]; +int err, i; + +if (strict_check) { +struct ndmsg *ndm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ndm))) { +NL_SET_ERR_MSG (extack,"Invalid header for neighbor dump request" ); +return -EINVAL ; + } + + ndm =nlmsg_data (nlh); +if (ndm->ndm_pad1 || ndm->ndm_pad2 || ndm->ndm_ifindex || + ndm->ndm_state || ndm->ndm_flags || ndm->ndm_type) { +NL_SET_ERR_MSG (extack,"Invalid values in header for neighbor dump request" ); +return -EINVAL ; + } + + err =nlmsg_parse_strict (nlh,sizeof (struct ndmsg ), tb,NDA_MAX , +NULL , extack); + }else { + err =nlmsg_parse (nlh,sizeof (struct ndmsg ), tb,NDA_MAX , +NULL , extack); + } +if (err <0 ) +return err; + +for (i =0 ; i <=NDA_MAX ; ++i) { +if (!tb[i]) +continue ; + +/* all new attributes should require strict_check */ +switch (i) { +case NDA_IFINDEX : +if (nla_len (tb[i]) !=sizeof (u32)) { +NL_SET_ERR_MSG (extack,"Invalid IFINDEX attribute in neighbor dump request" ); +return -EINVAL ; + } + filter->dev_idx =nla_get_u32 (tb[i]); +break ; +case NDA_MASTER : +if (nla_len (tb[i]) !=sizeof (u32)) { +NL_SET_ERR_MSG (extack,"Invalid MASTER attribute in neighbor dump request" ); +return -EINVAL ; + } + filter->master_idx =nla_get_u32 (tb[i]); +break ; +default : +if (strict_check) { +NL_SET_ERR_MSG (extack,"Unsupported attribute in neighbor dump request" ); +return -EINVAL ; + } + } + } + +return 0 ; +} +static int neigh_dump_info (struct sk_buff *skb,struct netlink_callback *cb) {const struct nlmsghdr *nlh = cb->nlh;struct neigh_dump_filter filter = {}; -struct nlattr *tb[NDA_MAX +1 ];struct neigh_table *tbl;int t, family, s_t;int proxy =0 ;@@ -2445,20 +2507,10 @@ static int neigh_dump_info(struct sk_buff *skb, struct netlink_callback *cb) ((struct ndmsg *)nlmsg_data(nlh))->ndm_flags == NTF_PROXY) proxy =1 ; - err =nlmsg_parse (nlh,sizeof (struct ndmsg ), tb,NDA_MAX ,NULL , - cb->extack); -if (!err) { -if (tb[NDA_IFINDEX ]) { -if (nla_len (tb[NDA_IFINDEX ]) !=sizeof (u32)) -return -EINVAL ; - filter.dev_idx =nla_get_u32 (tb[NDA_IFINDEX ]); - } -if (tb[NDA_MASTER ]) { -if (nla_len (tb[NDA_MASTER ]) !=sizeof (u32)) -return -EINVAL ; - filter.master_idx =nla_get_u32 (tb[NDA_MASTER ]); - } - } + err =neigh_valid_dump_req (nlh, cb->strict_check, &filter, cb->extack); +if (err <0 && cb->strict_check) +return err; + s_t = cb->args[0 ];for (t =0 ; t <NEIGH_NR_TABLES ; t++) {Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 16/23 net/neighbor: Update neightbl_dump_info for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update neightbl_dump_info for strict data checking. If the flag is set, the dump request is expected to have an ndtmsg struct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.
--- net/core/neighbour.c | 38 +++++++++++++++++++++++++++++++++++--- 1 file changed, 35 insertions(+), 3 deletions(-)
net/core/neighbour.c +35 -3
@@ -2164,15 +2164,47 @@ static int neightbl_set(struct sk_buff *skb, struct nlmsghdr *nlh,return err; } +static int neightbl_valid_dump_info (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct ndtmsg *ndtm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ndtm))) { +NL_SET_ERR_MSG (extack,"Invalid header for neighbor table dump request" ); +return -EINVAL ; + } + + ndtm =nlmsg_data (nlh); +if (ndtm->ndtm_pad1 || ndtm->ndtm_pad2) { +NL_SET_ERR_MSG (extack,"Invalid values in header for neighbor table dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ndtm))) { +NL_SET_ERR_MSG (extack,"Invalid data after header in neighbor table dump request" ); +return -EINVAL ; + } + +return 0 ; +} +static int neightbl_dump_info (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);int family, tidx, nidx =0 ;int tbl_skip = cb->args[0 ];int neigh_skip = cb->args[1 ];struct neigh_table *tbl; - family = ((struct rtgenmsg *)nlmsg_data (cb->nlh))->rtgen_family; +if (cb->strict_check) { +int err =neightbl_valid_dump_info (nlh, cb->extack); + +if (err <0 ) +return err; + } + + family = ((struct rtgenmsg *)nlmsg_data (nlh))->rtgen_family;for (tidx =0 ; tidx <NEIGH_NR_TABLES ; tidx++) {struct neigh_parms *p;
@@ -2185,7 +2217,7 @@ static int neightbl_dump_info(struct sk_buff *skb, struct netlink_callback *cb)continue ;if (neightbl_fill_info (skb, tbl,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq,RTM_NEWNEIGHTBL , + nlh->nlmsg_seq,RTM_NEWNEIGHTBL ,NLM_F_MULTI ) <0 )break ;
@@ -2200,7 +2232,7 @@ static int neightbl_dump_info(struct sk_buff *skb, struct netlink_callback *cb)if (neightbl_fill_param_info (skb, tbl, p,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNEIGHTBL ,NLM_F_MULTI ) <0 ) goto out;
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 16/23] net/neighbor: Update neightbl_dump_info for strict data checking
Quoted 8 lines · David Ahern
From: David Ahern <[email protected]>
Update
neightbl_dump_infofor strict data checking. If the flag is set, the dump request is expected to have an ndtmsg struct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.Signed-off-by David Ahern <[email protected]>
Quoted 78 lines
--- net/core/neighbour.c | 38 +++++++++++++++++++++++++++++++++++--- 1 file changed, 35 insertions(+), 3 deletions(-)net/core/neighbour.c +35
-3@@ -2164,15 +2164,47 @@ static int neightbl_set(struct sk_buff *skb, struct nlmsghdr *nlh,return err; } +static int neightbl_valid_dump_info (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct ndtmsg *ndtm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ndtm))) { +NL_SET_ERR_MSG (extack,"Invalid header for neighbor table dump request" ); +return -EINVAL ; + } + + ndtm =nlmsg_data (nlh); +if (ndtm->ndtm_pad1 || ndtm->ndtm_pad2) { +NL_SET_ERR_MSG (extack,"Invalid values in header for neighbor table dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ndtm))) { +NL_SET_ERR_MSG (extack,"Invalid data after header in neighbor table dump request" ); +return -EINVAL ; + } + +return 0 ; +} +static int neightbl_dump_info (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);int family, tidx, nidx =0 ;int tbl_skip = cb->args[0 ];int neigh_skip = cb->args[1 ];struct neigh_table *tbl; - family = ((struct rtgenmsg *)nlmsg_data (cb->nlh))->rtgen_family; +if (cb->strict_check) { +int err =neightbl_valid_dump_info (nlh, cb->extack); + +if (err <0 ) +return err; + } + + family = ((struct rtgenmsg *)nlmsg_data (nlh))->rtgen_family;for (tidx =0 ; tidx <NEIGH_NR_TABLES ; tidx++) {struct neigh_parms *p;@@ -2185,7 +2217,7 @@ static int neightbl_dump_info(struct sk_buff *skb, struct netlink_callback *cb)continue ;if (neightbl_fill_info (skb, tbl,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq,RTM_NEWNEIGHTBL , + nlh->nlmsg_seq,RTM_NEWNEIGHTBL ,NLM_F_MULTI ) <0 )break ;@@ -2200,7 +2232,7 @@ static int neightbl_dump_info(struct sk_buff *skb, struct netlink_callback *cb)if (neightbl_fill_param_info (skb, tbl, p,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNEIGHTBL ,NLM_F_MULTI ) <0 ) goto out;Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 17/23 net/namespace: Update rtnl_net_dumpid for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update rtnl_net_dumpid for strict data checking. If the flag is set, the dump request is expected to have an rtgenmsg struct as the header which has the family as the only element. No data may be appended.
--- net/core/net_namespace.c | 6 ++++++ 1 file changed, 6 insertions(+)
net/core/net_namespace.c +6 -0
@@ -853,6 +853,12 @@ static int rtnl_net_dumpid(struct sk_buff *skb, struct netlink_callback *cb) .s_idx = cb->args[0], }; +if (cb->strict_check && +nlmsg_attrlen (cb->nlh,sizeof (struct rtgenmsg ))) { +NL_SET_ERR_MSG (cb->extack,"Unknown data in network namespace id dump request" ); +return -EINVAL ; + } +spin_lock_bh (&net->nsid_lock);idr_for_each (&net->netns_ids, rtnl_net_dumpid_one, &net_cb);spin_unlock_bh (&net->nsid_lock);
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 17/23] net/namespace: Update rtnl_net_dumpid for strict data checking
Quoted 16 lines · David Ahern
From: David Ahern <[email protected]>
Update
rtnl_net_dumpidfor strict data checking. If the flag is set, the dump request is expected to have an rtgenmsg struct as the header which has the family as the only element. No data may be appended.Signed-off-by David Ahern <[email protected]>--- net/core/net_namespace.c | 6 ++++++ 1 file changed, 6 insertions(+)net/core/net_namespace.c +0
-0
net/core/net_namespace.c static int rtnl_net_dumpid(struct sk_buff *skb, struct netlink_callback *cb) · line 856
Quoted 4 lines
net/core/net_namespace.c +1
-0@@ -853,6 +853,12 @@ static int rtnl_net_dumpid(struct sk_buff *skb, struct netlink_callback *cb) .s_idx = cb->args[0], }; + if (cb->strict_check &&
Hm, shouldn't this also verify that the passed header is indeed struct rtgenmsg before checking whether there are any attributes?
Quoted 11 lines
net/core/net_namespace.c +5
-0+ nlmsg_attrlen(cb->nlh, sizeof(struct rtgenmsg))) { +NL_SET_ERR_MSG (cb->extack,"Unknown data in network namespace id dump request" ); +return -EINVAL ; + } +spin_lock_bh (&net->nsid_lock);idr_for_each (&net->netns_ids, rtnl_net_dumpid_one, &net_cb);spin_unlock_bh (&net->nsid_lock);Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 17/23] net/namespace: Update rtnl_net_dumpid for strict data checking
Quoted 20 lines · Christian Brauner
Quoted 19 lines · David Ahern
From: David Ahern <[email protected]>
Update
rtnl_net_dumpidfor strict data checking. If the flag is set, the dump request is expected to have an rtgenmsg struct as the header which has the family as the only element. No data may be appended.Signed-off-by David Ahern <[email protected]>--- net/core/net_namespace.c | 6 ++++++ 1 file changed, 6 insertions(+)net/core/net_namespace.c +0
-0@@ -853,6 +853,12 @@ static int rtnl_net_dumpid(struct sk_buff *skb, struct netlink_callback *cb) .s_idx = cb->args[0], };
Quoted 4 lines
net/core/net_namespace.c static int rtnl_net_dumpid(struct sk_buff *skb, struct netlink_callback *cb) · line 856
Quoted 1 line
net/core/net_namespace.c +1
-0+ if (cb->strict_check &&Hm, shouldn't this also verify that the passed header is indeed struct rtgenmsg before checking whether there are any attributes?
rtgenmsg is only a struct with only the family as an element. rtnetlink_rcv_msg has already verified that the nl msg header contains at least the rtgenmsg struct.
Quoted 12 lines
Quoted 12 lines
net/core/net_namespace.c +5
-0+ nlmsg_attrlen(cb->nlh, sizeof(struct rtgenmsg))) { +NL_SET_ERR_MSG (cb->extack,"Unknown data in network namespace id dump request" ); +return -EINVAL ; + } +spin_lock_bh (&net->nsid_lock);idr_for_each (&net->netns_ids, rtnl_net_dumpid_one, &net_cb);spin_unlock_bh (&net->nsid_lock);Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 17/23] net/namespace: Update rtnl_net_dumpid for strict data checking
Quoted 21 lines · David Ahern
Quoted 20 lines · Christian Brauner
Quoted 19 lines · David Ahern
From: David Ahern <[email protected]>
Update
rtnl_net_dumpidfor strict data checking. If the flag is set, the dump request is expected to have an rtgenmsg struct as the header which has the family as the only element. No data may be appended.Signed-off-by David Ahern <[email protected]>--- net/core/net_namespace.c | 6 ++++++ 1 file changed, 6 insertions(+)net/core/net_namespace.c +0
-0@@ -853,6 +853,12 @@ static int rtnl_net_dumpid(struct sk_buff *skb, struct netlink_callback *cb) .s_idx = cb->args[0], };
Quoted 4 lines
Quoted 4 lines
net/core/net_namespace.c static int rtnl_net_dumpid(struct sk_buff *skb, struct netlink_callback *cb) · line 856
Quoted 1 line
net/core/net_namespace.c +1
-0+ if (cb->strict_check &&Hm, shouldn't this also verify that the passed header is indeed struct rtgenmsg before checking whether there are any attributes?
Thanks!
Quoted 19 lines
rtgenmsg is only a struct with only the family as an element.
rtnetlink_rcv_msghas already verified that the nl msg header contains at least the rtgenmsg struct.Quoted 12 lines
Quoted 12 lines
net/core/net_namespace.c +5
-0+ nlmsg_attrlen(cb->nlh, sizeof(struct rtgenmsg))) { +NL_SET_ERR_MSG (cb->extack,"Unknown data in network namespace id dump request" ); +return -EINVAL ; + } +spin_lock_bh (&net->nsid_lock);idr_for_each (&net->netns_ids, rtnl_net_dumpid_one, &net_cb);spin_unlock_bh (&net->nsid_lock);Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 18/23 net/fib_rules: Update fib_nl_dumprule for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update fib_nl_dumprule for strict data checking. If the flag is set, the dump request is expected to have fib_rule_hdr struct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.
--- net/core/fib_rules.c | 36 +++++++++++++++++++++++++++++++++++- 1 file changed, 35 insertions(+), 1 deletion(-)
net/core/fib_rules.c +35 -1
@@ -1063,13 +1063,47 @@ static int dump_rules(struct sk_buff *skb, struct netlink_callback *cb,return err; } +static int fib_valid_dumprule_req (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct fib_rule_hdr *frh; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*frh))) { +NL_SET_ERR_MSG (extack,"Invalid header for fib rule dump request" ); +return -EINVAL ; + } + + frh =nlmsg_data (nlh); +if (frh->dst_len || frh->src_len || frh->tos || frh->table || + frh->res1 || frh->res2 || frh->action || frh->flags) { +NL_SET_ERR_MSG (extack, +"Invalid values in header for fib rule dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*frh))) { +NL_SET_ERR_MSG (extack,"Invalid data after header in fib rule dump request" ); +return -EINVAL ; + } + +return 0 ; +} +static int fib_nl_dumprule (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct fib_rules_ops *ops;int idx =0 , family; - family =rtnl_msg_family (cb->nlh); +if (cb->strict_check) { +int err =fib_valid_dumprule_req (nlh, cb->extack); + +if (err <0 ) +return err; + } + + family =rtnl_msg_family (nlh);if (family !=AF_UNSPEC ) {/* Protocol specific dump request */ ops =lookup_rules_ops (net, family);
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 18/23] net/fib_rules: Update fib_nl_dumprule for strict data checking
Quoted 8 lines · David Ahern
From: David Ahern <[email protected]>
Update
fib_nl_dumprulefor strict data checking. If the flag is set, the dump request is expected to havefib_rule_hdrstruct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.Signed-off-by David Ahern <[email protected]>
Quoted 60 lines
--- net/core/fib_rules.c | 36 +++++++++++++++++++++++++++++++++++- 1 file changed, 35 insertions(+), 1 deletion(-)net/core/fib_rules.c +35
-1@@ -1063,13 +1063,47 @@ static int dump_rules(struct sk_buff *skb, struct netlink_callback *cb,return err; } +static int fib_valid_dumprule_req (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct fib_rule_hdr *frh; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*frh))) { +NL_SET_ERR_MSG (extack,"Invalid header for fib rule dump request" ); +return -EINVAL ; + } + + frh =nlmsg_data (nlh); +if (frh->dst_len || frh->src_len || frh->tos || frh->table || + frh->res1 || frh->res2 || frh->action || frh->flags) { +NL_SET_ERR_MSG (extack, +"Invalid values in header for fib rule dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*frh))) { +NL_SET_ERR_MSG (extack,"Invalid data after header in fib rule dump request" ); +return -EINVAL ; + } + +return 0 ; +} +static int fib_nl_dumprule (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct fib_rules_ops *ops;int idx =0 , family; - family =rtnl_msg_family (cb->nlh); +if (cb->strict_check) { +int err =fib_valid_dumprule_req (nlh, cb->extack); + +if (err <0 ) +return err; + } + + family =rtnl_msg_family (nlh);if (family !=AF_UNSPEC ) {/* Protocol specific dump request */ ops =lookup_rules_ops (net, family);Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 19/23 net/ipv6: Update ip6addrlbl_dump for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update ip6addrlbl_dump for strict data checking. If the flag is set, the dump request is expected to have an ifaddrlblmsg struct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.
--- net/ipv6/addrlabel.c | 34 +++++++++++++++++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-)
net/ipv6/addrlabel.c +33 -1
@@ -458,20 +458,52 @@ static int ip6addrlbl_fill(struct sk_buff *skb,return 0 ; } +static int ip6addrlbl_valid_dump_req (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct ifaddrlblmsg *ifal; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifal))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for address label dump request" ); +return -EINVAL ; + } + + ifal =nlmsg_data (nlh); +if (ifal->__ifal_reserved || ifal->ifal_prefixlen || + ifal->ifal_flags || ifal->ifal_index || ifal->ifal_seq) { +NL_SET_ERR_MSG_MOD (extack,"Invalid values in header for address label dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ifal))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid data after header for address label dump requewst" ); +return -EINVAL ; + } + +return 0 ; +} +static int ip6addrlbl_dump (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct ip6addrlbl_entry *p;int idx =0 , s_idx = cb->args[0 ];int err; +if (cb->strict_check) { + err =ip6addrlbl_valid_dump_req (nlh, cb->extack); +if (err <0 ) +return err; + } +rcu_read_lock ();hlist_for_each_entry_rcu (p, &net->ipv6.ip6addrlbl_table.head, list) {if (idx >= s_idx) { err =ip6addrlbl_fill (skb, p, net->ipv6.ip6addrlbl_table.seq,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWADDRLABEL ,NLM_F_MULTI );if (err <0 )
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 19/23] net/ipv6: Update ip6addrlbl_dump for strict data checking
Quoted 8 lines · David Ahern
From: David Ahern <[email protected]>
Update
ip6addrlbl_dumpfor strict data checking. If the flag is set, the dump request is expected to have an ifaddrlblmsg struct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.Signed-off-by David Ahern <[email protected]>
Quoted 65 lines
--- net/ipv6/addrlabel.c | 34 +++++++++++++++++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-)net/ipv6/addrlabel.c +33
-1@@ -458,20 +458,52 @@ static int ip6addrlbl_fill(struct sk_buff *skb,return 0 ; } +static int ip6addrlbl_valid_dump_req (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct ifaddrlblmsg *ifal; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ifal))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for address label dump request" ); +return -EINVAL ; + } + + ifal =nlmsg_data (nlh); +if (ifal->__ifal_reserved || ifal->ifal_prefixlen || + ifal->ifal_flags || ifal->ifal_index || ifal->ifal_seq) { +NL_SET_ERR_MSG_MOD (extack,"Invalid values in header for address label dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ifal))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid data after header for address label dump requewst" ); +return -EINVAL ; + } + +return 0 ; +} +static int ip6addrlbl_dump (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct ip6addrlbl_entry *p;int idx =0 , s_idx = cb->args[0 ];int err; +if (cb->strict_check) { + err =ip6addrlbl_valid_dump_req (nlh, cb->extack); +if (err <0 ) +return err; + } +rcu_read_lock ();hlist_for_each_entry_rcu (p, &net->ipv6.ip6addrlbl_table.head, list) {if (idx >= s_idx) { err =ip6addrlbl_fill (skb, p, net->ipv6.ip6addrlbl_table.seq,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWADDRLABEL ,NLM_F_MULTI );if (err <0 )Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 20/23 net: Update netconf dump handlers for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update inet_netconf_dump_devconf, inet6_netconf_dump_devconf, and mpls_netconf_dump_devconf for strict data checking. If the flag is set, the dump request is expected to have an netconfmsg struct as the header. The struct only has the family member and no attributes can be appended.
--- net/ipv4/devinet.c | 22 +++++++++++++++++++--- net/ipv6/addrconf.c | 22 +++++++++++++++++++--- net/mpls/af_mpls.c | 18 +++++++++++++++++- 3 files changed, 55 insertions(+), 7 deletions(-)
net/ipv4/devinet.c +19 -3
@@ -2086,6 +2086,7 @@ static int inet_netconf_get_devconf(struct sk_buff *in_skb,static int inet_netconf_dump_devconf (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);int h, s_h;int idx, s_idx;
@@ -2093,6 +2094,21 @@ static int inet_netconf_dump_devconf(struct sk_buff *skb,struct in_device *in_dev;struct hlist_head *head; +if (cb->strict_check) { +struct netlink_ext_ack *extack = cb->extack; +struct netconfmsg *ncm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ncm))) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid header for netconf dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ncm))) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid data after header in netconf dump request" ); +return -EINVAL ; + } + } + s_h = cb->args[0 ]; s_idx = idx = cb->args[1 ];
@@ -2112,7 +2128,7 @@ static int inet_netconf_dump_devconf(struct sk_buff *skb,if (inet_netconf_fill_devconf (skb, dev->ifindex, &in_dev->cnf,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) {
@@ -2129,7 +2145,7 @@ static int inet_netconf_dump_devconf(struct sk_buff *skb,if (inet_netconf_fill_devconf (skb,NETCONFA_IFINDEX_ALL , net->ipv4.devconf_all,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) goto done;
@@ -2140,7 +2156,7 @@ static int inet_netconf_dump_devconf(struct sk_buff *skb,if (inet_netconf_fill_devconf (skb,NETCONFA_IFINDEX_DEFAULT , net->ipv4.devconf_dflt,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) goto done;
net/ipv6/addrconf.c +19 -3
@@ -666,6 +666,7 @@ static int inet6_netconf_get_devconf(struct sk_buff *in_skb,static int inet6_netconf_dump_devconf (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);int h, s_h;int idx, s_idx;
@@ -673,6 +674,21 @@ static int inet6_netconf_dump_devconf(struct sk_buff *skb,struct inet6_dev *idev;struct hlist_head *head; +if (cb->strict_check) { +struct netlink_ext_ack *extack = cb->extack; +struct netconfmsg *ncm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ncm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for netconf dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ncm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid data after header in netconf dump request" ); +return -EINVAL ; + } + } + s_h = cb->args[0 ]; s_idx = idx = cb->args[1 ];
@@ -692,7 +708,7 @@ static int inet6_netconf_dump_devconf(struct sk_buff *skb,if (inet6_netconf_fill_devconf (skb, dev->ifindex, &idev->cnf,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) {
@@ -709,7 +725,7 @@ static int inet6_netconf_dump_devconf(struct sk_buff *skb,if (inet6_netconf_fill_devconf (skb,NETCONFA_IFINDEX_ALL , net->ipv6.devconf_all,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) goto done;
@@ -720,7 +736,7 @@ static int inet6_netconf_dump_devconf(struct sk_buff *skb,if (inet6_netconf_fill_devconf (skb,NETCONFA_IFINDEX_DEFAULT , net->ipv6.devconf_dflt,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) goto done;
net/mpls/af_mpls.c +17 -1
@@ -1263,6 +1263,7 @@ static int mpls_netconf_get_devconf(struct sk_buff *in_skb,static int mpls_netconf_dump_devconf (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct hlist_head *head;struct net_device *dev;
@@ -1270,6 +1271,21 @@ static int mpls_netconf_dump_devconf(struct sk_buff *skb,int idx, s_idx;int h, s_h; +if (cb->strict_check) { +struct netlink_ext_ack *extack = cb->extack; +struct netconfmsg *ncm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ncm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for netconf dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ncm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid data after header in netconf dump request" ); +return -EINVAL ; + } + } + s_h = cb->args[0 ]; s_idx = idx = cb->args[1 ];
@@ -1286,7 +1302,7 @@ static int mpls_netconf_dump_devconf(struct sk_buff *skb, goto cont;if (mpls_netconf_fill_devconf (skb, mdev,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) {
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 20/23] net: Update netconf dump handlers for strict data checking
Quoted 8 lines · David Ahern
From: David Ahern <[email protected]>
Update
inet_netconf_dump_devconf,inet6_netconf_dump_devconf, andmpls_netconf_dump_devconffor strict data checking. If the flag is set, the dump request is expected to have an netconfmsg struct as the header. The struct only has the family member and no attributes can be appended.Signed-off-by David Ahern <[email protected]>
Quoted 174 lines
--- net/ipv4/devinet.c | 22 +++++++++++++++++++--- net/ipv6/addrconf.c | 22 +++++++++++++++++++--- net/mpls/af_mpls.c | 18 +++++++++++++++++- 3 files changed, 55 insertions(+), 7 deletions(-)net/ipv4/devinet.c +19
-3@@ -2086,6 +2086,7 @@ static int inet_netconf_get_devconf(struct sk_buff *in_skb,static int inet_netconf_dump_devconf (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);int h, s_h;int idx, s_idx;@@ -2093,6 +2094,21 @@ static int inet_netconf_dump_devconf(struct sk_buff *skb,struct in_device *in_dev;struct hlist_head *head; +if (cb->strict_check) { +struct netlink_ext_ack *extack = cb->extack; +struct netconfmsg *ncm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ncm))) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid header for netconf dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ncm))) { +NL_SET_ERR_MSG (extack,"ipv4: Invalid data after header in netconf dump request" ); +return -EINVAL ; + } + } + s_h = cb->args[0 ]; s_idx = idx = cb->args[1 ];@@ -2112,7 +2128,7 @@ static int inet_netconf_dump_devconf(struct sk_buff *skb,if (inet_netconf_fill_devconf (skb, dev->ifindex, &in_dev->cnf,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) {@@ -2129,7 +2145,7 @@ static int inet_netconf_dump_devconf(struct sk_buff *skb,if (inet_netconf_fill_devconf (skb,NETCONFA_IFINDEX_ALL , net->ipv4.devconf_all,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) goto done;@@ -2140,7 +2156,7 @@ static int inet_netconf_dump_devconf(struct sk_buff *skb,if (inet_netconf_fill_devconf (skb,NETCONFA_IFINDEX_DEFAULT , net->ipv4.devconf_dflt,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) goto done;net/ipv6/addrconf.c +19
-3@@ -666,6 +666,7 @@ static int inet6_netconf_get_devconf(struct sk_buff *in_skb,static int inet6_netconf_dump_devconf (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);int h, s_h;int idx, s_idx;@@ -673,6 +674,21 @@ static int inet6_netconf_dump_devconf(struct sk_buff *skb,struct inet6_dev *idev;struct hlist_head *head; +if (cb->strict_check) { +struct netlink_ext_ack *extack = cb->extack; +struct netconfmsg *ncm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ncm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for netconf dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ncm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid data after header in netconf dump request" ); +return -EINVAL ; + } + } + s_h = cb->args[0 ]; s_idx = idx = cb->args[1 ];@@ -692,7 +708,7 @@ static int inet6_netconf_dump_devconf(struct sk_buff *skb,if (inet6_netconf_fill_devconf (skb, dev->ifindex, &idev->cnf,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) {@@ -709,7 +725,7 @@ static int inet6_netconf_dump_devconf(struct sk_buff *skb,if (inet6_netconf_fill_devconf (skb,NETCONFA_IFINDEX_ALL , net->ipv6.devconf_all,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) goto done;@@ -720,7 +736,7 @@ static int inet6_netconf_dump_devconf(struct sk_buff *skb,if (inet6_netconf_fill_devconf (skb,NETCONFA_IFINDEX_DEFAULT , net->ipv6.devconf_dflt,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) goto done;net/mpls/af_mpls.c +17
-1@@ -1263,6 +1263,7 @@ static int mpls_netconf_get_devconf(struct sk_buff *in_skb,static int mpls_netconf_dump_devconf (struct sk_buff *skb,struct netlink_callback *cb) { +const struct nlmsghdr *nlh = cb->nlh;struct net *net =sock_net (skb->sk);struct hlist_head *head;struct net_device *dev;@@ -1270,6 +1271,21 @@ static int mpls_netconf_dump_devconf(struct sk_buff *skb,int idx, s_idx;int h, s_h; +if (cb->strict_check) { +struct netlink_ext_ack *extack = cb->extack; +struct netconfmsg *ncm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ncm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for netconf dump request" ); +return -EINVAL ; + } + +if (nlmsg_attrlen (nlh,sizeof (*ncm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid data after header in netconf dump request" ); +return -EINVAL ; + } + } + s_h = cb->args[0 ]; s_idx = idx = cb->args[1 ];@@ -1286,7 +1302,7 @@ static int mpls_netconf_dump_devconf(struct sk_buff *skb, goto cont;if (mpls_netconf_fill_devconf (skb, mdev,NETLINK_CB (cb->skb).portid, - cb->nlh->nlmsg_seq, + nlh->nlmsg_seq,RTM_NEWNETCONF ,NLM_F_MULTI ,NETCONFA_ALL ) <0 ) {Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 21/23 net/bridge: Update br_mdb_dump for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update br_mdb_dump for strict data checking. If the flag is set, the dump request is expected to have a br_port_msg struct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.
--- net/bridge/br_mdb.c | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+)
net/bridge/br_mdb.c +30 -0
@@ -162,6 +162,29 @@ static int br_mdb_fill_info(struct sk_buff *skb, struct netlink_callback *cb,return err; } +static int br_mdb_valid_dump_req (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct br_port_msg *bpm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*bpm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for mdb dump request" ); +return -EINVAL ; + } + + bpm =nlmsg_data (nlh); +if (bpm->ifindex) { +NL_SET_ERR_MSG_MOD (extack,"Filtering by device index is not supported for mdb dump request" ); +return -EINVAL ; + } +if (nlmsg_attrlen (nlh,sizeof (*bpm))) { +NL_SET_ERR_MSG (extack,"Invalid data after header in mdb dump request" ); +return -EINVAL ; + } + +return 0 ; +} +static int br_mdb_dump (struct sk_buff *skb,struct netlink_callback *cb) {struct net_device *dev;
@@ -169,6 +192,13 @@ static int br_mdb_dump(struct sk_buff *skb, struct netlink_callback *cb)struct nlmsghdr *nlh =NULL ;int idx =0 , s_idx; +if (cb->strict_check) { +int err =br_mdb_valid_dump_req (cb->nlh, cb->extack); + +if (err <0 ) +return err; + } + s_idx = cb->args[0 ];rcu_read_lock ();
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 21/23] net/bridge: Update br_mdb_dump for strict data checking
Quoted 8 lines · David Ahern
From: David Ahern <[email protected]>
Update
br_mdb_dumpfor strict data checking. If the flag is set, the dump request is expected to have abr_port_msgstruct as the header. All elements of the struct are expected to be 0 and no attributes can be appended.Signed-off-by David Ahern <[email protected]>
Quoted 55 lines
--- net/bridge/br_mdb.c | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+)net/bridge/br_mdb.c +30
-0@@ -162,6 +162,29 @@ static int br_mdb_fill_info(struct sk_buff *skb, struct netlink_callback *cb,return err; } +static int br_mdb_valid_dump_req (const struct nlmsghdr *nlh, +struct netlink_ext_ack *extack) +{ +struct br_port_msg *bpm; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*bpm))) { +NL_SET_ERR_MSG_MOD (extack,"Invalid header for mdb dump request" ); +return -EINVAL ; + } + + bpm =nlmsg_data (nlh); +if (bpm->ifindex) { +NL_SET_ERR_MSG_MOD (extack,"Filtering by device index is not supported for mdb dump request" ); +return -EINVAL ; + } +if (nlmsg_attrlen (nlh,sizeof (*bpm))) { +NL_SET_ERR_MSG (extack,"Invalid data after header in mdb dump request" ); +return -EINVAL ; + } + +return 0 ; +} +static int br_mdb_dump (struct sk_buff *skb,struct netlink_callback *cb) {struct net_device *dev;@@ -169,6 +192,13 @@ static int br_mdb_dump(struct sk_buff *skb, struct netlink_callback *cb)struct nlmsghdr *nlh =NULL ;int idx =0 , s_idx; +if (cb->strict_check) { +int err =br_mdb_valid_dump_req (cb->nlh, cb->extack); + +if (err <0 ) +return err; + } + s_idx = cb->args[0 ];rcu_read_lock ();Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 22/23 rtnetlink: Move input checking for rtnl_fdb_dump to helper
In reply to David AhernFrom: David Ahern <[email protected]>
Move the existing input checking for rtnl_fdb_dump into a helper, valid_fdb_dump_legacy. This function will retain the current logic that works around the 2 headers that userspace has been allowed to send up to this point.
--- net/core/rtnetlink.c | 53 ++++++++++++++++++++++++++++++++-------------------- 1 file changed, 33 insertions(+), 20 deletions(-)
net/core/rtnetlink.c +33 -20
@@ -3799,22 +3799,13 @@ int ndo_dflt_fdb_dump(struct sk_buff *skb, }EXPORT_SYMBOL (ndo_dflt_fdb_dump); -static int rtnl_fdb_dump (struct sk_buff *skb,struct netlink_callback *cb) +static int valid_fdb_dump_legacy (const struct nlmsghdr *nlh, +int *br_idx,int *brport_idx, +struct netlink_ext_ack *extack) { -struct net_device *dev; +struct ifinfomsg *ifm =nlmsg_data (nlh);struct nlattr *tb[IFLA_MAX +1 ]; -struct net_device *br_dev =NULL ; -const struct net_device_ops *ops =NULL ; -const struct net_device_ops *cops =NULL ; -struct ifinfomsg *ifm =nlmsg_data (cb->nlh); -struct net *net =sock_net (skb->sk); -struct hlist_head *head; -int brport_idx =0 ; -int br_idx =0 ; -int h, s_h; -int idx =0 , s_idx; -int err =0 ; -int fidx =0 ; +int err;/* A hack to preserve kernel<->userspace interface. * Before Linux v4.12 this code accepted ndmsg since iproute2 v3.3.0.
@@ -3823,20 +3814,42 @@ static int rtnl_fdb_dump(struct sk_buff *skb, struct netlink_callback *cb)* Fortunately these sizes don't conflict with the size of ifinfomsg * with an optional attribute. */ -if (nlmsg_len (cb->nlh) !=sizeof (struct ndmsg ) && - (nlmsg_len (cb->nlh) !=sizeof (struct ndmsg ) + +if (nlmsg_len (nlh) !=sizeof (struct ndmsg ) && + (nlmsg_len (nlh) !=sizeof (struct ndmsg ) +nla_attr_size (sizeof (u32)))) { - err =nlmsg_parse (cb->nlh,sizeof (struct ifinfomsg ), tb, -IFLA_MAX , ifla_policy, cb->extack); + err =nlmsg_parse (nlh,sizeof (struct ifinfomsg ), tb,IFLA_MAX , + ifla_policy, extack);if (err <0 ) {return -EINVAL ; }else if (err ==0 ) {if (tb[IFLA_MASTER ]) - br_idx =nla_get_u32 (tb[IFLA_MASTER ]); + *br_idx =nla_get_u32 (tb[IFLA_MASTER ]); } - brport_idx = ifm->ifi_index; + *brport_idx = ifm->ifi_index; } +return 0 ; +} + +static int rtnl_fdb_dump (struct sk_buff *skb,struct netlink_callback *cb) +{ +struct net_device *dev; +struct net_device *br_dev =NULL ; +const struct net_device_ops *ops =NULL ; +const struct net_device_ops *cops =NULL ; +struct net *net =sock_net (skb->sk); +struct hlist_head *head; +int brport_idx =0 ; +int br_idx =0 ; +int h, s_h; +int idx =0 , s_idx; +int err =0 ; +int fidx =0 ; + + err =valid_fdb_dump_legacy (cb->nlh, &br_idx, &brport_idx, + cb->extack); +if (err <0 ) +return err;if (br_idx) { br_dev =__dev_get_by_index (net, br_idx);
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 22/23] rtnetlink: Move input checking for rtnl_fdb_dump to helper
Quoted 8 lines · David Ahern
From: David Ahern <[email protected]>
Move the existing input checking for
rtnl_fdb_dumpinto a helper,valid_fdb_dump_legacy. This function will retain the current logic that works around the 2 headers that userspace has been allowed to send up to this point.Signed-off-by David Ahern <[email protected]>
Quoted 9 lines
--- net/core/rtnetlink.c | 53 ++++++++++++++++++++++++++++++++-------------------- 1 file changed, 33 insertions(+), 20 deletions(-)net/core/rtnetlink.c +0
-0
net/core/rtnetlink.c int ndo_dflt_fdb_dump(struct sk_buff *skb, · line 3806
Quoted 10 lines
net/core/rtnetlink.c +4
-2@@ -3799,22 +3799,13 @@ int ndo_dflt_fdb_dump(struct sk_buff *skb, }EXPORT_SYMBOL (ndo_dflt_fdb_dump); -static int rtnl_fdb_dump (struct sk_buff *skb,struct netlink_callback *cb) +static int valid_fdb_dump_legacy (const struct nlmsghdr *nlh, +int *br_idx,int *brport_idx, +struct netlink_ext_ack *extack) { -struct net_device *dev; +struct ifinfomsg *ifm =nlmsg_data (nlh);
You could move this cast after the
if (nlmsg_len(nlh) != sizeof(struct ndmsg) &&
(nlmsg_len(nlh) != sizeof(struct ndmsg) +
check. It doesn't matter that much but it minimizes the risk of someone accidently accessing struct ifinfomsg *ifm when it's an invalid cast.
Quoted 69 lines
net/core/rtnetlink.c +29
-18struct nlattr *tb[IFLA_MAX +1 ]; -struct net_device *br_dev =NULL ; -const struct net_device_ops *ops =NULL ; -const struct net_device_ops *cops =NULL ; -struct ifinfomsg *ifm =nlmsg_data (cb->nlh); -struct net *net =sock_net (skb->sk); -struct hlist_head *head; -int brport_idx =0 ; -int br_idx =0 ; -int h, s_h; -int idx =0 , s_idx; -int err =0 ; -int fidx =0 ; +int err;/* A hack to preserve kernel<->userspace interface. * Before Linux v4.12 this code accepted ndmsg since iproute2 v3.3.0. @@ -3823,20 +3814,42 @@ static int rtnl_fdb_dump(struct sk_buff *skb, struct netlink_callback *cb)* Fortunately these sizes don't conflict with the size of ifinfomsg * with an optional attribute. */ -if (nlmsg_len (cb->nlh) !=sizeof (struct ndmsg ) && - (nlmsg_len (cb->nlh) !=sizeof (struct ndmsg ) + +if (nlmsg_len (nlh) !=sizeof (struct ndmsg ) && + (nlmsg_len (nlh) !=sizeof (struct ndmsg ) +nla_attr_size (sizeof (u32)))) { - err =nlmsg_parse (cb->nlh,sizeof (struct ifinfomsg ), tb, -IFLA_MAX , ifla_policy, cb->extack); + err =nlmsg_parse (nlh,sizeof (struct ifinfomsg ), tb,IFLA_MAX , + ifla_policy, extack);if (err <0 ) {return -EINVAL ; }else if (err ==0 ) {if (tb[IFLA_MASTER ]) - br_idx =nla_get_u32 (tb[IFLA_MASTER ]); + *br_idx =nla_get_u32 (tb[IFLA_MASTER ]); } - brport_idx = ifm->ifi_index; + *brport_idx = ifm->ifi_index; } +return 0 ; +} + +static int rtnl_fdb_dump (struct sk_buff *skb,struct netlink_callback *cb) +{ +struct net_device *dev; +struct net_device *br_dev =NULL ; +const struct net_device_ops *ops =NULL ; +const struct net_device_ops *cops =NULL ; +struct net *net =sock_net (skb->sk); +struct hlist_head *head; +int brport_idx =0 ; +int br_idx =0 ; +int h, s_h; +int idx =0 , s_idx; +int err =0 ; +int fidx =0 ; + + err =valid_fdb_dump_legacy (cb->nlh, &br_idx, &brport_idx, + cb->extack); +if (err <0 ) +return err;if (br_idx) { br_dev =__dev_get_by_index (net, br_idx);Signature · 1 line
2.11.0
David Ahern
maintainerPATCH v2 23/23 rtnetlink: Update rtnl_fdb_dump for strict data checking
In reply to David AhernFrom: David Ahern <[email protected]>
Update rtnl_fdb_dump for strict data checking. If the flag is set, the dump request is expected to have an ndmsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values supported by the dump handler are allowed to be non-0 or set in the request. At the moment only the NDA_IFINDEX and NDA_MASTER attributes are supported.
--- net/core/rtnetlink.c | 62 ++++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 60 insertions(+), 2 deletions(-)
net/core/rtnetlink.c +60 -2
@@ -3799,6 +3799,60 @@ int ndo_dflt_fdb_dump(struct sk_buff *skb, }EXPORT_SYMBOL (ndo_dflt_fdb_dump); +static int valid_fdb_dump_strict (const struct nlmsghdr *nlh, +int *br_idx,int *brport_idx, +struct netlink_ext_ack *extack) +{ +struct nlattr *tb[NDA_MAX +1 ]; +struct ndmsg *ndm; +int err, i; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ndm))) { +NL_SET_ERR_MSG (extack,"Invalid header for fdb dump request" ); +return -EINVAL ; + } + + ndm =nlmsg_data (nlh); +if (ndm->ndm_pad1 || ndm->ndm_pad2 || ndm->ndm_state || + ndm->ndm_flags || ndm->ndm_type) { +NL_SET_ERR_MSG (extack,"Invalid values in header for fbd dump request" ); +return -EINVAL ; + } + + err =nlmsg_parse_strict (nlh,sizeof (struct ndmsg ), tb,NDA_MAX , +NULL , extack); +if (err <0 ) +return err; + + *brport_idx = ndm->ndm_ifindex; +for (i =0 ; i <=NDA_MAX ; ++i) { +if (!tb[i]) +continue ; + +switch (i) { +case NDA_IFINDEX : +if (nla_len (tb[i]) !=sizeof (u32)) { +NL_SET_ERR_MSG (extack,"Invalid IFINDEX attribute in fdb dump request" ); +return -EINVAL ; + } + *brport_idx =nla_get_u32 (tb[NDA_IFINDEX ]); +break ; +case NDA_MASTER : +if (nla_len (tb[i]) !=sizeof (u32)) { +NL_SET_ERR_MSG (extack,"Invalid MASTER attribute in fdb dump request" ); +return -EINVAL ; + } + *br_idx =nla_get_u32 (tb[NDA_MASTER ]); +break ; +default : +NL_SET_ERR_MSG (extack,"Unsupported attribute in fdb dump request" ); +return -EINVAL ; + } + } + +return 0 ; +} +static int valid_fdb_dump_legacy (const struct nlmsghdr *nlh,int *br_idx,int *brport_idx,struct netlink_ext_ack *extack)
@@ -3846,8 +3900,12 @@ static int rtnl_fdb_dump(struct sk_buff *skb, struct netlink_callback *cb)int err =0 ;int fidx =0 ; - err =valid_fdb_dump_legacy (cb->nlh, &br_idx, &brport_idx, - cb->extack); +if (cb->strict_check) + err =valid_fdb_dump_strict (cb->nlh, &br_idx, &brport_idx, + cb->extack); +else + err =valid_fdb_dump_legacy (cb->nlh, &br_idx, &brport_idx, + cb->extack);if (err <0 )return err;
Signature · 1 line
2.11.0
Re: [PATCH v2 net-next 23/23] rtnetlink: Update rtnl_fdb_dump for strict data checking
Quoted 11 lines · David Ahern
From: David Ahern <[email protected]>
Update
rtnl_fdb_dumpfor strict data checking. If the flag is set, the dump request is expected to have an ndmsg struct as the header potentially followed by one or more attributes. Any data passed in the header or as an attribute is taken as a request to influence the data returned. Only values supported by the dump handler are allowed to be non-0 or set in the request. At the moment only theNDA_IFINDEXandNDA_MASTERattributes are supported.Signed-off-by David Ahern <[email protected]>
Quoted 87 lines
--- net/core/rtnetlink.c | 62 ++++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 60 insertions(+), 2 deletions(-)net/core/rtnetlink.c +60
-2@@ -3799,6 +3799,60 @@ int ndo_dflt_fdb_dump(struct sk_buff *skb, }EXPORT_SYMBOL (ndo_dflt_fdb_dump); +static int valid_fdb_dump_strict (const struct nlmsghdr *nlh, +int *br_idx,int *brport_idx, +struct netlink_ext_ack *extack) +{ +struct nlattr *tb[NDA_MAX +1 ]; +struct ndmsg *ndm; +int err, i; + +if (nlh->nlmsg_len <nlmsg_msg_size (sizeof (*ndm))) { +NL_SET_ERR_MSG (extack,"Invalid header for fdb dump request" ); +return -EINVAL ; + } + + ndm =nlmsg_data (nlh); +if (ndm->ndm_pad1 || ndm->ndm_pad2 || ndm->ndm_state || + ndm->ndm_flags || ndm->ndm_type) { +NL_SET_ERR_MSG (extack,"Invalid values in header for fbd dump request" ); +return -EINVAL ; + } + + err =nlmsg_parse_strict (nlh,sizeof (struct ndmsg ), tb,NDA_MAX , +NULL , extack); +if (err <0 ) +return err; + + *brport_idx = ndm->ndm_ifindex; +for (i =0 ; i <=NDA_MAX ; ++i) { +if (!tb[i]) +continue ; + +switch (i) { +case NDA_IFINDEX : +if (nla_len (tb[i]) !=sizeof (u32)) { +NL_SET_ERR_MSG (extack,"Invalid IFINDEX attribute in fdb dump request" ); +return -EINVAL ; + } + *brport_idx =nla_get_u32 (tb[NDA_IFINDEX ]); +break ; +case NDA_MASTER : +if (nla_len (tb[i]) !=sizeof (u32)) { +NL_SET_ERR_MSG (extack,"Invalid MASTER attribute in fdb dump request" ); +return -EINVAL ; + } + *br_idx =nla_get_u32 (tb[NDA_MASTER ]); +break ; +default : +NL_SET_ERR_MSG (extack,"Unsupported attribute in fdb dump request" ); +return -EINVAL ; + } + } + +return 0 ; +} +static int valid_fdb_dump_legacy (const struct nlmsghdr *nlh,int *br_idx,int *brport_idx,struct netlink_ext_ack *extack)@@ -3846,8 +3900,12 @@ static int rtnl_fdb_dump(struct sk_buff *skb, struct netlink_callback *cb)int err =0 ;int fidx =0 ; - err =valid_fdb_dump_legacy (cb->nlh, &br_idx, &brport_idx, - cb->extack); +if (cb->strict_check) + err =valid_fdb_dump_strict (cb->nlh, &br_idx, &brport_idx, + cb->extack); +else + err =valid_fdb_dump_legacy (cb->nlh, &br_idx, &brport_idx, + cb->extack);if (err <0 )return err;Signature · 1 line
2.11.0
Quoted 119 lines · David Ahern
From: David Ahern <[email protected]>
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 interest to userspace, reducing the cpu overhead of both kernel and userspace. Unfortunately, the kernel has historically not been strict with checking for the proper header or checking the values passed in the header. This lenient implementation has allowed iproute2 and other packages to pass any struct or data in the dump request as long as the family is the first byte. For example, ifinfomsg struct is used by iproute2 for all generic dump requests - links, addresses, routes and rules when it is really only valid for link requests.
There is 1 is example where the kernel deals with the wrong struct: link dumps after VF support was added. Older iproute2 was sending rtgenmsg as the header instead of ifinfomsg so a patch was added to try and detect old userspace vs new:
e5eca6d41f53("rtnetlink: fix userspace API breakage for iproute2 < v3.9.0")The latest example is Christian's patch set wanting to return addresses for a target namespace. It guesses the header struct is an ifaddrmsg and if it guesses wrong a netlink warning is generated in the kernel log on every address dump which is unacceptable.
Another example where the kernel is a bit lenient is route dumps: iproute2 can send either a request with either ifinfomsg or a rtmsg as the header struct, yet the kernel always treats the header as an rtmsg (see
inet_dump_fibandrtm_flagscheck). The header inconsistency impacts the ability to add kernel side filters for route dumps - a necessary feature for scale setups with 100k+ routes.How to resolve the problem of not breaking old userspace yet be able to move forward with new features such as kernel side filtering which are crucial for efficient operation at high scale?
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 ability to use kernel side filters as they are added.Kernel side, the dump handlers are updated to verify the message contains at least the expected header struct:
RTM_GETLINK: ifinfomsg RTM_GETADDR: ifaddrmsg RTM_GETMULTICAST: ifaddrmsg RTM_GETANYCAST: ifaddrmsg RTM_GETADDRLABEL: ifaddrlblmsg RTM_GETROUTE: rtmsg RTM_GETSTATS: if_stats_msg RTM_GETNEIGH: ndmsg RTM_GETNEIGHTBL: ndtmsg RTM_GETNSID: rtgenmsg RTM_GETRULE: fib_rule_hdr RTM_GETNETCONF: netconfmsg RTM_GETMDB: br_port_msgAnd then every field in the header struct should be 0 with the exception of the family. There are a few exceptions to this rule where the kernel already influences the data returned by values in the struct. Next the message should not contain attributes unless the kernel implements filtering for it. Any unexpected data causes the dump to fail with EINVAL. If the new flag is honored by the kernel and the dump contents adjusted by any data passed in the request, the dump handler can set the
NLM_F_DUMP_FILTEREDflag in the netlink message header.For old userspace on new kernel there is no impact as all checks are wrapped in a check on the new strict flag. For new userspace on old kernel, the data in the headers and any appended attributes are silently ignored though the setsockopt failing is the clue to userspace the feature is not supported. New userspace on new kernel gets the requested data dump.
iproute2 patches can be found here:
https://github.com/dsahern/iproute2 dump-enhancementsMajor changes since v1
- inner header is supposed to be 4-bytes aligned. So for dumps that should not have attributes appended changed the check to use:
if (nlmsg_attrlen(nlh, sizeof(hdr)))
Only impacts patches with headers that are not multiples of 4-bytes (rtgenmsg, netconfmsg), but applied the change to all patches not callingnlmsg_parsefor consistency.- Added
nlmsg_parse_strictandnla_parse_strictfor tighter control on attribute parsing. There should be no unknown attribute types or extra bytes.- Moved validation to a helper in most cases
Changes since rfc-v2
- dropped theNLM_F_DUMP_FILTEREDflag from target nsid dumps per Jiri's objections
- changed the opt-in uapi from a netlink message flag to a socket flag. setsockopt provides an api for userspace to definitively know if the kernel supports strict checking on dumps.
- re-ordered patches to peel off the extack on dumps if needed to keep this set size within limits
- misc cleanups in patches based on testingDavid Ahern (23):
netlink: Pass extack to dump handlers
netlink: Add extack message tonlmsg_parsefor invalid header length
net: Add extack tonlmsg_parse
netlink: Add strict version ofnlmsg_parseandnla_parsenet/ipv6: Refactor address dump to pushinet6_fill_argsto
in6_dump_addrs
netlink: Add new socket option to enable strict checking on dumps net/ipv4: Updateinet_dump_ifaddrfor strict data checking net/ipv6: Updateinet6_dump_addrfor strict data checking
rtnetlink: Updatertnl_dump_ifinfofor strict data checking
rtnetlink: Updatertnl_bridge_getlinkfor strict data checking
rtnetlink: Updatertnl_stats_dumpfor strict data checking
rtnetlink: Updateinet6_dump_ifinfofor strict data checking
rtnetlink: Updateipmr_rtm_dumplinkfor strict data checking
rtnetlink: Update fib dumps for strict data checking net/neighbor: Updateneigh_dump_infofor strict data checking
Quoted 8 lines
net/neighbor: Update
neightbl_dump_infofor strict data checking net/namespace: Updatertnl_net_dumpidfor strict data checkingnet/fib_rules: Updatefib_nl_dumprulefor strict data checking net/ipv6: Updateip6addrlbl_dumpfor strict data checking
net: Update netconf dump handlers for strict data checking net/bridge: Updatebr_mdb_dumpfor strict data checking
rtnetlink: Move input checking forrtnl_fdb_dumpto helper
rtnetlink: Updatertnl_fdb_dumpfor strict data checking
At this point it's all nits so it's got my ACK but keener eyes than mine might see other issues.
Quoted 33 lines
include/linux/netlink.h | 2 + include/net/ip_fib.h | 2 + include/net/netlink.h | 21 ++- include/uapi/linux/netlink.h | 1 + lib/nlattr.c | 48 +++++-- net/bridge/br_mdb.c | 30 ++++ net/core/devlink.c | 2 +- net/core/fib_rules.c | 36 ++++- net/core/neighbour.c | 119 ++++++++++++--- net/core/net_namespace.c | 6 + net/core/rtnetlink.c | 318 ++++++++++++++++++++++++++++++++--------- net/ipv4/devinet.c | 101 ++++++++++--- net/ipv4/fib_frontend.c | 42 +++++- net/ipv4/ipmr.c | 39 +++++ net/ipv6/addrconf.c | 177 ++++++++++++++++++----- net/ipv6/addrlabel.c | 34 ++++- net/ipv6/ip6_fib.c | 8 ++ net/ipv6/ip6mr.c | 9 ++ net/ipv6/route.c | 2 +- net/mpls/af_mpls.c | 28 +++- net/netfilter/ipvs/ip_vs_ctl.c | 2 +- net/netlink/af_netlink.c | 33 ++++- net/netlink/af_netlink.h | 1 + net/sched/act_api.c | 2 +- net/sched/cls_api.c | 6 +- net/sched/sch_api.c | 2 +- net/xfrm/xfrm_user.c | 2 +- 27 files changed, 908 insertions(+), 165 deletions(-)Signature · 1 line
2.11.0
David Miller
maintainerFrom: Christian Brauner <[email protected]>
Date: Mon, 8 Oct 2018 13:04:13 +0200
Quoted 43 lines · David Ahern
Quoted 42 lines
From: David Ahern <[email protected]>
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 interest to userspace, reducing the cpu overhead of both kernel and userspace. Unfortunately, the kernel has historically not been strict with checking for the proper header or checking the values passed in the header. This lenient implementation has allowed iproute2 and other packages to pass any struct or data in the dump request as long as the family is the first byte. For example, ifinfomsg struct is used by iproute2 for all generic dump requests - links, addresses, routes and rules when it is really only valid for link requests.
There is 1 is example where the kernel deals with the wrong struct: link dumps after VF support was added. Older iproute2 was sending rtgenmsg as the header instead of ifinfomsg so a patch was added to try and detect old userspace vs new:
e5eca6d41f53("rtnetlink: fix userspace API breakage for iproute2 < v3.9.0")The latest example is Christian's patch set wanting to return addresses for a target namespace. It guesses the header struct is an ifaddrmsg and if it guesses wrong a netlink warning is generated in the kernel log on every address dump which is unacceptable.
Another example where the kernel is a bit lenient is route dumps: iproute2 can send either a request with either ifinfomsg or a rtmsg as the header struct, yet the kernel always treats the header as an rtmsg (see
inet_dump_fibandrtm_flagscheck). The header inconsistency impacts the ability to add kernel side filters for route dumps - a necessary feature for scale setups with 100k+ routes.How to resolve the problem of not breaking old userspace yet be able to move forward with new features such as kernel side filtering which are crucial for efficient operation at high scale?
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 ability to use kernel side filters as they are added.
...
Quoted 4 lines
At this point it's all nits so it's got my ACK but keener eyes than mine might see other issues.
Series applied, thanks everyone.
Please be on the lookout for userspace regressions from this patch set.
Thanks.