summaryrefslogtreecommitdiffstats
path: root/m4
diff options
context:
space:
mode:
authorPhil Sutter <phil@nwl.cc>2019-09-03 18:10:55 +0200
committerPhil Sutter <phil@nwl.cc>2019-09-30 08:11:45 +0200
commit760b35b46e4cc3aabe9214027959266df23a0122 (patch)
tree9d3501f3c76aced056493a2373c397b9e43fa9cf /m4
parentf51cae64e9064ae503586ab5a4572ee3bea97de2 (diff)
nft: Fix for add and delete of same rule in single batch
Another corner-case found when extending restore ordering test: If a delete command in a dump referenced a rule added earlier within the same dump, kernel would reject the resulting NFT_MSG_DELRULE command. Catch this by assigning the rule to delete a RULE_ID value if it doesn't have a handle yet. Since __nft_rule_del() does not duplicate the nftnl_rule object when creating the NFT_COMPAT_RULE_DELETE command, this RULE_ID value is added to both NEWRULE and DELRULE commands - exactly what is needed to establish the reference. Signed-off-by: Phil Sutter <phil@nwl.cc> Acked-by: Florian Westphal <fw@strlen.de>
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions