CTA_NAT_SRC and CTA_NAT_DST are input-only. The only references to either
are cda[] reads in ctnetlink_setup_nat() and the rejection in
ctnetlink_change_conntrack(); no path ever puts them into a message, so
neither belongs in a reply. nat-dst was listed twice on top of that.
CTA_TIMESTAMP is the opposite case - both the do and the dump reach
ctnetlink_fill_info() with extinfo set, so ctnetlink_dump_extinfo() ->
ctnetlink_dump_timestamp() emits it, but the lists never named it.
Reported-by: Sashiko <netdev-bot+sashiko@kernel.org>
Closes: https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260826220444.4054714-1-i.maximets@ovn.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
Documentation/netlink/specs/conntrack.yaml | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/Documentation/netlink/specs/conntrack.yaml b/Documentation/netlink/specs/conntrack.yaml
index 2b7f16cc4133..174697ce125e 100644
--- a/Documentation/netlink/specs/conntrack.yaml
+++ b/Documentation/netlink/specs/conntrack.yaml
@@ -596,20 +596,18 @@ doc: >-
- status
- protoinfo
- help
- - nat-src
- - nat-dst
- timeout
- mark
- counters-orig
- counters-reply
- use
- id
- - nat-dst
- tuple-master
- seq-adj-orig
- seq-adj-reply
- zone
- secctx
+ - timestamp
- labels
- synproxy
dump:@@ -632,20 +630,18 @@ doc: >-
- status
- protoinfo
- help
- - nat-src
- - nat-dst
- timeout
- mark
- counters-orig
- counters-reply
- use
- id
- - nat-dst
- tuple-master
- seq-adj-orig
- seq-adj-reply
- zone
- secctx
+ - timestamp
- labels
- synproxy
---
2.55.0