summaryrefslogtreecommitdiffstats
path: root/iptables/nft-bridge.h
diff options
context:
space:
mode:
authorPhil Sutter <phil@nwl.cc>2020-10-26 17:25:03 +0100
committerPhil Sutter <phil@nwl.cc>2020-10-27 18:07:46 +0100
commited8c8b9316451a4499eeb592d2cf7d782bbe4e9a (patch)
tree3db6242e0bc20ee9ac6648723b1e54b8acbd6b84 /iptables/nft-bridge.h
parentdac904bdcd9a18aabafee7275ccf0c2bd53800f3 (diff)
tests: shell: Improve concurrent noflush restore test a bitHEADmaster
The described issue happens only if chain FOO does not exist at program start so flush the ruleset after each iteration to make sure this is the case. Sadly the bug is still not 100% reproducible on my testing VM. While being at it, add a paragraph describing what exact situation the test is trying to provoke. Fixes: dac904bdcd9a1 ("nft: Fix for concurrent noflush restore calls") Signed-off-by: Phil Sutter <phil@nwl.cc>
Diffstat (limited to 'iptables/nft-bridge.h')
0 files changed, 0 insertions, 0 deletions