diff options
author | Liping Zhang <zlpnobody@gmail.com> | 2017-04-29 16:59:49 +0300 |
---|---|---|
committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2017-05-01 12:48:49 +0300 |
commit | 8eeef2350453aa012d846457eb6ecd012a35d99b (patch) | |
tree | 75d509dec2c42b8ae71f8e511309802d6fc1053f /net/netfilter/ipvs/ip_vs_nfct.c | |
parent | d1908ca8dcb1a045cf0626be4513a28933f46d5e (diff) | |
download | linux-8eeef2350453aa012d846457eb6ecd012a35d99b.tar.xz |
netfilter: nf_ct_ext: invoke destroy even when ext is not attached
For NF_NAT_MANIP_SRC, we will insert the ct to the nat_bysource_table,
then remove it from the nat_bysource_table via nat_extend->destroy.
But now, the nat extension is attached on demand, so if the nat extension
is not attached, we will not be notified when the ct is destroyed, i.e.
we may fail to remove ct from the nat_bysource_table.
So just keep it simple, even if the extension is not attached, we will
still invoke the related ext->destroy. And this will also preserve the
flexibility for the future extension.
Fixes: 9a08ecfe74d7 ("netfilter: don't attach a nat extension by default")
Signed-off-by: Liping Zhang <zlpnobody@gmail.com>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'net/netfilter/ipvs/ip_vs_nfct.c')
0 files changed, 0 insertions, 0 deletions