diff options
author | 2023-07-20 00:29:58 +0200 | |
---|---|---|
committer | 2023-07-20 11:56:50 +0200 | |
commit | ddbd8be68941985f166f5107109a90ce13147c44 (patch) | |
tree | d040cbc705cc1ab134dfc75e3e83ea87ec328fe7 /scripts/generate_rust_analyzer.py | |
parent | Merge branch 'net-support-stp-on-bridge-in-non-root-netns' (diff) | |
download | wireguard-linux-ddbd8be68941985f166f5107109a90ce13147c44.tar.xz wireguard-linux-ddbd8be68941985f166f5107109a90ce13147c44.zip |
netfilter: nf_tables: fix spurious set element insertion failure
On some platforms there is a padding hole in the nft_verdict
structure, between the verdict code and the chain pointer.
On element insertion, if the new element clashes with an existing one and
NLM_F_EXCL flag isn't set, we want to ignore the -EEXIST error as long as
the data associated with duplicated element is the same as the existing
one. The data equality check uses memcmp.
For normal data (NFT_DATA_VALUE) this works fine, but for NFT_DATA_VERDICT
padding area leads to spurious failure even if the verdict data is the
same.
This then makes the insertion fail with 'already exists' error, even
though the new "key : data" matches an existing entry and userspace
told the kernel that it doesn't want to receive an error indication.
Fixes: c016c7e45ddf ("netfilter: nf_tables: honor NLM_F_EXCL flag in set element insertion")
Signed-off-by: Florian Westphal <fw@strlen.de>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions