diff options
| author | Florian Westphal <fw@strlen.de> | 2026-09-04 20:03:07 +0200 |
|---|---|---|
| committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2026-09-27 22:38:47 +0200 |
| commit | a442c8a89fb9c531f9d6ab86120c31decd778d51 (patch) | |
| tree | 1b9f895edea6ae36520934f6abdfb72a45751436 /tools/lib/python/kdoc/python_version.py | |
| parent | 9c572a83037a7dcd653ba3a9cc468c16b857d0c9 (diff) | |
| download | linux-next-a442c8a89fb9c531f9d6ab86120c31decd778d51.tar.gz linux-next-a442c8a89fb9c531f9d6ab86120c31decd778d51.zip | |
netfilter: ipset: do not update comments from kernel-side adds
'Fixes' commit stopped calling ip_set_init_comment() for hash types
from kernel-side-adds (xtables .. -j SET). ip_set_init_comment() says:
"The kadt functions don't use the comment extensions in any way."
But bitmap set type calls the function from kadt cb too.
While this appears to be safe (serialized via the set spinlock), it seems
better to not call the init function either, least of all to keep
behaviour consistent.
ip_set_list calls ip_set_init_comment() only from uadt cb, it can be
kept as-is.
This was triggered by yet another LLM review, hinting that the existing
rcu_dereference_protected() cannot be downgraded to only check if the
nfnl mutex is held.
Fixes: f30415929be8 ("netfilter: ipset: do not update comments from kernel-side hash adds")
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions