diff options
author | Florian Westphal <fw@strlen.de> | 2021-04-07 21:43:39 +0200 |
---|---|---|
committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2021-04-10 21:16:54 +0200 |
commit | 7ee3c61dcd28bf6e290e06ad382f13511dc790e9 (patch) | |
tree | f9c1f51fc326ec3afea31c578cddb99cf2396135 /net/bridge/br_mdb.c | |
parent | b895bdf5d643b6feb7c60856326dd4feb6981560 (diff) | |
download | linux-7ee3c61dcd28bf6e290e06ad382f13511dc790e9.tar.bz2 |
netfilter: bridge: add pre_exit hooks for ebtable unregistration
Just like ip/ip6/arptables, the hooks have to be removed, then
synchronize_rcu() has to be called to make sure no more packets are being
processed before the ruleset data is released.
Place the hook unregistration in the pre_exit hook, then call the new
ebtables pre_exit function from there.
Years ago, when first netns support got added for netfilter+ebtables,
this used an older (now removed) netfilter hook unregister API, that did
a unconditional synchronize_rcu().
Now that all is done with call_rcu, ebtable_{filter,nat,broute} pernet exit
handlers may free the ebtable ruleset while packets are still in flight.
This can only happens on module removal, not during netns exit.
The new function expects the table name, not the table struct.
This is because upcoming patch set (targeting -next) will remove all
net->xt.{nat,filter,broute}_table instances, this makes it necessary
to avoid external references to those member variables.
The existing APIs will be converted, so follow the upcoming scheme of
passing name + hook type instead.
Fixes: aee12a0a3727e ("ebtables: remove nf_hook_register usage")
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'net/bridge/br_mdb.c')
0 files changed, 0 insertions, 0 deletions