-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
bpf: recreate CT entry if proxy_redirect is stale for non-tcp #33222
Merged
jrajahalme
merged 1 commit into
cilium:main
from
ysksuzuki:fix-state-proxy-redirect-non-tcp
Jun 21, 2024
Merged
bpf: recreate CT entry if proxy_redirect is stale for non-tcp #33222
jrajahalme
merged 1 commit into
cilium:main
from
ysksuzuki:fix-state-proxy-redirect-non-tcp
Jun 21, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/test |
This commit fixes the issue that datapath erroneously redirects (or doesn't redirect) the reply packets to the proxy if the packet hits the stale CT entry. The PR cilium#32653 fixed the issue when the TCP connection hits a closing stale entry by having __ct_lookup return CT_NEW in that case so that the caller can recreate an entry to update the proxy_redirect flag. This commit lets datapath recreate an entry in the case where non-TCP packets hit the stale CT entry with the proxy_redirect flag, or an active TCP connection suddenly comes into the scope of an L7 policy. Signed-off-by: Yusuke Suzuki <yusuke.suzuki@isovalent.com>
12a95e9
to
7d7d538
Compare
/test |
julianwiedmann
approved these changes
Jun 19, 2024
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.
looks good, thank you!
@jrajahalme if you're in agreement, please make sure to also add the |
jrajahalme
approved these changes
Jun 21, 2024
12 tasks
This was referenced Jul 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects/v1.13
This issue affects v1.13 branch
affects/v1.14
This issue affects v1.14 branch
area/proxy
Impacts proxy components, including DNS, Kafka, Envoy and/or XDS servers.
backport-done/1.15
The backport for Cilium 1.15.x for this PR is done.
feature/conntrack
kind/bug
This is a bug in the Cilium logic.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/bug
This PR fixes an issue in a previous release of Cilium.
sig/datapath
Impacts bpf/ or low-level forwarding details, including map management and monitor messages.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit fixes the issue that datapath erroneously redirects (or doesn't redirect) the reply packets to the proxy if the packet hits the stale CT entry.
The PR #32653 fixed the issue for TCP by having __ct_lookup return CT_NEW if the packet hits a closing stale entry so that the caller can recreate an entry to update the proxy_redirect flag.
This commit lets datapath recreate an entry for non-TCP in the similar case to update the proxy_redirect flag.
This problem can occur, for example, when using dns-proxy.