net: Fixups for recent dump filtering changes
Subsystems (3)
David Ahern
maintainercover net: Fixups for recent dump filtering changes
From: David Ahern <[email protected]>
Li RongQing noted that tgt_net is leaked in ipv4 due to the recent change to handle address dumps for a specific device. The report also applies to ipv6 and other error paths. Patches 1 and 2 fix those leaks.
Patch 3 stops route dumps from erroring out when dumping across address families and a table id is given. This is needed in preparation for patch 4.
Patch 4 updates the rtnl_dump_all to handle a failure in one of the dumpit functions. At the moment, if an address dump returns an error the dump all loop breaks but the error is dropped. The result can be no data is returned and no error either leaving the user wondering about the addresses.
Patches were tested with a modified iproute2 to add invalid data to the dump request causing each specific failure path to be hit in addition to positive testing that it works as it should when given valid data.
David Ahern (4):
net/ipv4: Put target net when address dump fails due to bad attributes net/ipv6: Put target net when address dump fails due to bad attributes
net: Don't return invalid table id error when dumping all families
net: rtnl_dump_all needs to propagate error from dumpit function
include/net/ip_fib.h | 1 + net/core/rtnetlink.c | 6 ++++-- net/ipv4/devinet.c | 13 ++++++++----- net/ipv4/fib_frontend.c | 4 ++++ net/ipv4/ipmr.c | 3 +++ net/ipv6/addrconf.c | 14 ++++++++------ net/ipv6/ip6_fib.c | 3 +++ net/ipv6/ip6mr.c | 3 +++ 8 files changed, 34 insertions(+), 13 deletions(-)
Signature · 1 line
2.11.0
David Ahern
maintainerPATCH 1/4 net/ipv4: Put target net when address dump fails due to bad attributes
From: David Ahern <[email protected]>
If tgt_net is set based on IFA_TARGET_NETNSID attribute in the dump request, make sure all error paths call put_net.
--- net/ipv4/devinet.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-)
net/ipv4/devinet.c +8 -5
@@ -1761,7 +1761,7 @@ static int inet_dump_ifaddr(struct sk_buff *skb, struct netlink_callback *cb)struct net_device *dev;struct in_device *in_dev;struct hlist_head *head; -int err; +int err =0 ; s_h = cb->args[0 ]; s_idx = idx = cb->args[1 ];
@@ -1771,12 +1771,15 @@ static int inet_dump_ifaddr(struct sk_buff *skb, struct netlink_callback *cb) err =inet_valid_dump_ifaddr_req (nlh, &fillargs, &tgt_net, skb->sk, cb);if (err <0 ) -return err; + goto put_tgt_net; + err =0 ;if (fillargs.ifindex) { dev =__dev_get_by_index (tgt_net, fillargs.ifindex); -if (!dev) -return -ENODEV ; +if (!dev) { + err = -ENODEV ; + goto put_tgt_net; + } in_dev =__in_dev_get_rtnl (dev);if (in_dev) {
@@ -1821,7 +1824,7 @@ static int inet_dump_ifaddr(struct sk_buff *skb, struct netlink_callback *cb)if (fillargs.netnsid >=0 )put_net (tgt_net); -return skb->len; +return err <0 ? err : skb->len; } static void rtmsg_ifa(int event, struct in_ifaddr *ifa, struct nlmsghdr *nlh,
Signature · 1 line
2.11.0
David Ahern
maintainerPATCH 2/4 net/ipv6: Put target net when address dump fails due to bad attributes
In reply to David AhernFrom: David Ahern <[email protected]>
If tgt_net is set based on IFA_TARGET_NETNSID attribute in the dump request, make sure all error paths call put_net.
--- net/ipv6/addrconf.c | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-)
net/ipv6/addrconf.c +8 -6
@@ -5089,23 +5089,25 @@ static int inet6_dump_addr(struct sk_buff *skb, struct netlink_callback *cb,struct net_device *dev;struct inet6_dev *idev;struct hlist_head *head; +int err =0 ; s_h = cb->args[0 ]; s_idx = idx = cb->args[1 ]; s_ip_idx = cb->args[2 ];if (cb->strict_check) { -int err; - err =inet6_valid_dump_ifaddr_req (nlh, &fillargs, &tgt_net, skb->sk, cb);if (err <0 ) -return err; + goto put_tgt_net; + err =0 ;if (fillargs.ifindex) { dev =__dev_get_by_index (tgt_net, fillargs.ifindex); -if (!dev) -return -ENODEV ; +if (!dev) { + err = -ENODEV ; + goto put_tgt_net; + } idev =__in6_dev_get (dev);if (idev) { err = in6_dump_addrs(idev, skb, cb, s_ip_idx,
@@ -5144,7 +5146,7 @@ static int inet6_dump_addr(struct sk_buff *skb, struct netlink_callback *cb,if (fillargs.netnsid >=0 )put_net (tgt_net); -return skb->len; +return err <0 ? err : skb->len; }static int inet6_dump_ifaddr (struct sk_buff *skb,struct netlink_callback *cb)
Signature · 1 line
2.11.0
David Ahern
maintainerPATCH 3/4 net: Don't return invalid table id error when dumping all families
In reply to David AhernFrom: David Ahern <[email protected]>
When doing a route dump across all address families, do not error out if the table does not exist. This allows a route dump for AF_UNSPEC with a table id that may only exist for some of the families.
Do return the table does not exist error if dumping routes for a specific family and the table does not exist.
--- include/net/ip_fib.h | 1 + net/ipv4/fib_frontend.c | 4 ++++ net/ipv4/ipmr.c | 3 +++ net/ipv6/ip6_fib.c | 3 +++ net/ipv6/ip6mr.c | 3 +++ 5 files changed, 14 insertions(+)
include/net/ip_fib.h +1 -0
@@ -226,6 +226,7 @@ struct fib_dump_filter {u32 table_id;/* filter_set is an optimization that an entry is set */ bool filter_set; +bool dump_all_families;unsigned char protocol;unsigned char rt_type;unsigned int flags;
net/ipv4/fib_frontend.c +4 -0
@@ -829,6 +829,7 @@ int ip_valid_fib_dump_req(struct net *net, const struct nlmsghdr *nlh,return -EINVAL ; } + filter->dump_all_families = (rtm->rtm_family ==AF_UNSPEC ); filter->flags = rtm->rtm_flags; filter->protocol = rtm->rtm_protocol; filter->rt_type = rtm->rtm_type;
@@ -899,6 +900,9 @@ static int inet_dump_fib(struct sk_buff *skb, struct netlink_callback *cb)if (filter.table_id) { tb =fib_get_table (net, filter.table_id);if (!tb) { +if (filter.dump_all_families) +return skb->len; +NL_SET_ERR_MSG (cb->extack,"ipv4: FIB table does not exist" );return -ENOENT ; }
net/ipv4/ipmr.c +3 -0
@@ -2542,6 +2542,9 @@ static int ipmr_rtm_dumproute(struct sk_buff *skb, struct netlink_callback *cb) mrt =ipmr_get_table (sock_net (skb->sk), filter.table_id);if (!mrt) { +if (filter.dump_all_families) +return skb->len; +NL_SET_ERR_MSG (cb->extack,"ipv4: MR table does not exist" );return -ENOENT ; }
net/ipv6/ip6_fib.c +3 -0
@@ -620,6 +620,9 @@ static int inet6_dump_fib(struct sk_buff *skb, struct netlink_callback *cb)if (arg.filter.table_id) { tb =fib6_get_table (net, arg.filter.table_id);if (!tb) { +if (arg.filter.dump_all_families) +return skb->len; +NL_SET_ERR_MSG_MOD (cb->extack,"FIB table does not exist" );return -ENOENT ; }
net/ipv6/ip6mr.c +3 -0
@@ -2473,6 +2473,9 @@ static int ip6mr_rtm_dumproute(struct sk_buff *skb, struct netlink_callback *cb) mrt =ip6mr_get_table (sock_net (skb->sk), filter.table_id);if (!mrt) { +if (filter.dump_all_families) +return skb->len; +NL_SET_ERR_MSG_MOD (cb->extack,"MR table does not exist" );return -ENOENT ; }
Signature · 1 line
2.11.0
David Ahern
maintainerPATCH 4/4 net: rtnl_dump_all needs to propagate error from dumpit function
In reply to David AhernFrom: David Ahern <[email protected]>
If an address, route or netconf dump request is sent for AF_UNSPEC, then rtnl_dump_all is used to do the dump across all address families. If one of the dumpit functions fails (e.g., invalid attributes in the dump request) then rtnl_dump_all needs to propagate that error so the user gets an appropriate response instead of just getting no data.
--- net/core/rtnetlink.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
net/core/rtnetlink.c +4 -2
@@ -3333,6 +3333,7 @@ static int rtnl_dump_all(struct sk_buff *skb, struct netlink_callback *cb)int idx;int s_idx = cb->family;int type = cb->nlh->nlmsg_type -RTM_BASE ; +int ret =0 ;if (s_idx ==0 ) s_idx =1 ;
@@ -3365,12 +3366,13 @@ static int rtnl_dump_all(struct sk_buff *skb, struct netlink_callback *cb) cb->prev_seq =0 ; cb->seq =0 ; } -if (dumpit (skb, cb)) + ret =dumpit (skb, cb); +if (ret <0 )break ; } cb->family = idx; -return skb->len; +return skb->len ? : ret; } struct sk_buff *rtmsg_ifinfo_build_skb(int type, struct net_device *dev,
Signature · 1 line
2.11.0
David Miller
maintainerFrom: David Ahern <[email protected]>
Date: Wed, 24 Oct 2018 12:58:58 -0700
Quoted 8 lines
Li RongQing noted that
tgt_netis leaked in ipv4 due to the recent change to handle address dumps for a specific device. The report also applies to ipv6 and other error paths. Patches 1 and 2 fix those leaks.Patch 3 stops route dumps from erroring out when dumping across address families and a table id is given. This is needed in preparation for patch 4.
Quoted 8 lines
Patch 4 updates the
rtnl_dump_allto handle a failure in one of the dumpit functions. At the moment, if an address dump returns an error the dump all loop breaks but the error is dropped. The result can be no data is returned and no error either leaving the user wondering about the addresses.Patches were tested with a modified iproute2 to add invalid data to the dump request causing each specific failure path to be hit in addition to positive testing that it works as it should when given valid data.
Series applied, thanks David.