From 862818ac3a0de5642444dfc9aa06e0f6fbb3ef38 Mon Sep 17 00:00:00 2001 From: Florian Westphal Date: Tue, 23 Apr 2019 15:16:22 +0200 Subject: xtables: add and use nft_build_cache Will be used with the "generation id" infrastructure. When we're told that the commit failed because someone else made changes, we can use this to re-initialize the cache and then revalidate the transaction list (e.g. to detect that we now have to flush the user-defined chain 'foo' that we wanted to create, but was added just now by someone else). Signed-off-by: Florian Westphal Acked-by: Pablo Neira Ayuso --- iptables/xtables-restore.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (limited to 'iptables/xtables-restore.c') diff --git a/iptables/xtables-restore.c b/iptables/xtables-restore.c index b12ab6a6..a6a331d3 100644 --- a/iptables/xtables-restore.c +++ b/iptables/xtables-restore.c @@ -145,10 +145,7 @@ void xtables_restore_parse(struct nft_handle *h, if (p->tablename && (strcmp(p->tablename, table) != 0)) continue; - /* Fixme: Needed to init chain cache. - * Should create explicit function to do this. - */ - nft_chain_list_get(h, table); + nft_build_cache(h); if (h->noflush == 0) { DEBUGP("Cleaning all chains of table '%s'\n", -- cgit v1.2.3