[v1.17] bpf:wireguard: reuse MARK_MAGIC_ENCRYPT for encrypted packets #39652
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.
Manual backport of:
With this patch, we protect previous usages of MARK_MAGIC_ENCRYPT which refer only to the IPSec codepath.
In v1.18, we start using that mark to signal also WireGuard encrypted packets, replacing the old MARK_MAGIC_WG_ENCRYPTED that overlaps with the k8s mark space.
This means that v1.17 needs to be able to understand that mark too in the WireGuard codepaths.
Once this PR is merged, a GitHub action will update the labels of these PRs: