Hi Pablo, On Mon, Aug 26, 2024 at 10:54:53AM +0200, Pablo Neira Ayuso wrote: > Reset command does not utilize the cache infrastructure. This commit changes audit log output for some reason. At least I see tools/testing/selftests/net/netfilter/nft_audit.sh failing and git bisect pointed at it. The relevant kselftest output is: # testing for cmd: nft reset rules ... FAIL # table=t1 family=2 entries=3 op=nft_reset_rule # table=t2 family=2 entries=3 op=nft_reset_rule # table=t2 family=2 entries=3 op=nft_reset_rule # -table=t2 family=2 entries=180 op=nft_reset_rule # +table=t2 family=2 entries=186 op=nft_reset_rule # table=t2 family=2 entries=188 op=nft_reset_rule # -table=t2 family=2 entries=135 op=nft_reset_rule # +table=t2 family=2 entries=129 op=nft_reset_rule I don't know why entries value changes and whether it is expected or not. Could you perhaps have a look? Cheers, Phil
