net: sched: crash on blocks with goto chain action
Subsystems (3)
PATCH v3 1/1 net: sched: crash on blocks with goto chain action
tcf_block_put_ext has assumed that all filters (and thus their goto actions) are destroyed in RCU callback and so can not race with our list iteration. However, that is not true during netns cleanup (see tcf_exts_get_net comment). The assumption was broken by the patch series c7e460ce5572..623859ae06b8 ("Merge branch 'net-sched-race-fix'").
Prevent the user after free by holding all chains (except 0, that one is already held) as it was done before822e86d997e4 ("net_sched: remove tcf_block_put_deferred()").
To reproduce, run the following in a netns and then delete the ns:
ip link add dtest type dummy
tc qdisc add dev dtest ingress
tc filter add dev dtest chain 1 parent ffff: handle 1 prio 1 flower action goto chain 2
---
v1 -> v2: Hold all chains instead of just the currently iterated one,
the code should be more clear this way.
v2 -> v3: Point out where the chains will be released.
Blame the correct patch series (the one that broke the assumption).
--
net/sched/cls_api.c | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-)
net/sched/cls_api.c +13 -5
@@ -336,7 +336,8 @@ static void tcf_block_put_final(struct work_struct *work)struct tcf_chain *chain, *tmp;rtnl_lock (); -/* Only chain 0 should be still here. */ + +/* At this point, all the chains should have refcnt == 1. */ list_for_each_entry_safe (chain, tmp, &block->chain_list, list)tcf_chain_put (chain);rtnl_unlock ();
@@ -344,15 +345,22 @@ static void tcf_block_put_final(struct work_struct *work) }/* XXX: Standalone actions are not allowed to jump to any chain, and bound -* actions should be all removed after flushing. However, filters are now -* destroyed in tc filter workqueue with RTNL lock, they can not race here. +* actions should be all removed after flushing. */ void tcf_block_put_ext (struct tcf_block *block,struct Qdisc *q,struct tcf_block_ext_info *ei) { -struct tcf_chain *chain, *tmp; +struct tcf_chain *chain; -list_for_each_entry_safe (chain, tmp, &block->chain_list, list) +/* Hold a refcnt for all chains, except 0 (which is held anyway), so +* that they don't disappear while we are iterating. We will release +* them in tcf_block_put_final, including finally releasing chain 0. +*/ +list_for_each_entry (chain, &block->chain_list, list) +if (chain->index) +tcf_chain_hold (chain); + +list_for_each_entry (chain, &block->chain_list, list)tcf_chain_flush (chain);tcf_block_offload_unbind (block, q, ei);
Signature · 1 line
2.15.0
David Miller
maintainerFrom: Roman Kapl <[email protected]>
Date: Wed, 29 Nov 2017 20:20:14 +0100
Quoted 10 lines
tcf_block_put_exthas assumed that all filters (and thus their goto actions) are destroyed in RCU callback and so can not race with our list iteration. However, that is not true during netns cleanup (seetcf_exts_get_netcomment). The assumption was broken by the patch seriesc7e460ce5572..623859ae06b8("Merge branch 'net-sched-race-fix'").Prevent the user after free by holding all chains (except 0, that one is already held) as it was done before
822e86d997e4("net_sched: removetcf_block_put_deferred()").
Quoted 7 lines
To reproduce, run the following in a netns and then delete the ns:
ip link add dtest type dummy
tc qdisc add dev dtest ingress
tc filter add dev dtest chain 1 parent ffff: handle 1 prio 1 flower action goto chain 2Fixes 623859ae06b8 ("Merge branch 'net-sched-race-fix'")Signed-off-by Roman Kapl <[email protected]>
This doesn't apply cleanly to 'net'.
Quoted 2 lines · David Miller
This doesn't apply cleanly to 'net'.
Dave, you already applied v2:
commit a60b3f515d30d0fe8537c64671926879a3548103
Author: Roman Kapl <[email protected]> Date: Fri Nov 24 12:27:58 2017 +0100
net: sched: crash on blocks with goto chain action
And the difference between v2 and v3 is only the Fixes tag, so not a big deal.