From: Phil Sutter <phil@xxxxxx> The commit this fixes added a new parameter to __nft_rule_flush() to mark a rule flush job as implicit or not. Yet the code added to that function ignores the parameter and instead always sets batch job's 'implicit' flag to 1. Fixes: 77e6a93d5c9dc ("xtables: add and set "implict" flag on transaction objects") Signed-off-by: Phil Sutter <phil@xxxxxx> Signed-off-by: Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx> --- iptables/nft.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/iptables/nft.c b/iptables/nft.c index 288ada4af3ca..b9268b63c86d 100644 --- a/iptables/nft.c +++ b/iptables/nft.c @@ -1778,7 +1778,7 @@ __nft_rule_flush(struct nft_handle *h, const char *table, return; } - obj->implicit = 1; + obj->implicit = implicit; } int nft_rule_flush(struct nft_handle *h, const char *chain, const char *table, -- 2.11.0