I don't find a scenario that trigger this case.

Fixes: 58d7de0181f6 ("xtables: handle concurrent ruleset modifications")
Signed-off-by: Pablo Neira Ayuso <pa...@netfilter.org>
---
 iptables/nft.c | 10 +---------
 1 file changed, 1 insertion(+), 9 deletions(-)

diff --git a/iptables/nft.c b/iptables/nft.c
index b9268b63c86d..43b9153c2d58 100644
--- a/iptables/nft.c
+++ b/iptables/nft.c
@@ -2794,15 +2794,6 @@ static void nft_refresh_transaction(struct nft_handle *h)
                        else if (!n->skip && !exists)
                                n->skip = 1;
                        break;
-               case NFT_COMPAT_TABLE_ADD:
-                       tablename = nftnl_table_get_str(n->table, 
NFTNL_TABLE_NAME);
-                       if (!tablename)
-                               continue;
-
-                       exists = nft_table_find(h, tablename);
-                       if (n->skip && !exists)
-                               n->skip = 0;
-                       break;
                case NFT_COMPAT_CHAIN_USER_ADD:
                        tablename = nftnl_chain_get_str(n->chain, 
NFTNL_CHAIN_TABLE);
                        if (!tablename)
@@ -2822,6 +2813,7 @@ static void nft_refresh_transaction(struct nft_handle *h)
                                n->skip = 0;
                        }
                        break;
+               case NFT_COMPAT_TABLE_ADD:
                case NFT_COMPAT_CHAIN_ADD:
                case NFT_COMPAT_CHAIN_ZERO:
                case NFT_COMPAT_CHAIN_USER_DEL:
-- 
2.11.0

Reply via email to