New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v1.13] bpf: nat: report detailed error from map_update_elem() for NAT entries #27652
Conversation
[ upstream commit 1f6c10d ] [ backporter's notes: as cilium#24716 is missing, manually add the needed ext_err bits into nat.h and switch the callers to send_drop_notify_error_ext(). ] snat_*_nat_handle_mapping() already takes an *ext_err parameter to pass up detailed error information from its CT logic. Use this to also report errors from map_update_elem() when creating the NAT entries. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
[ upstream commit 66e9579 ] [ backporter's notes: as cilium#24716 is missing, do the switch to send_drop_notify_error_ext() ] tail_nodeport_dsr_ingress_ipv*() already maintains an *ext_err parameter to report detailed error information from its CT logic. Use this to also report errors from map_update_elem() when creating the RevDNAT entry. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
/test-backport-1.13 |
/test-1.26-net-next |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#24716 is missing from v1.13 and way too intrusive to backport.
Those ext_errs would be also useful, it's a pity it wasn't straightforward to backport...
Yep, I had initially hoped to get them in as well. But it was too many conflicts piling up :/. Maybe it works better with a clean re-implementation, not trying to resolve the conflicts 1-by-1. |
Manual backport, as #24716 is missing from
v1.13
and way too intrusive to backport.Once this PR is merged, you can update the PR labels via:
or with