bpf: lxc: always set identity mark on forwarded egressing traffic#42551
Merged
julianwiedmann merged 1 commit intomainfrom Nov 3, 2025
Merged
bpf: lxc: always set identity mark on forwarded egressing traffic#42551julianwiedmann merged 1 commit intomainfrom
julianwiedmann merged 1 commit intomainfrom
Conversation
Guessing which exact forward paths can benefit from the identity mark is fragile, and it's hard to overlook corner cases. Even when we BPF-redirect a packet to an external interface (with BPF Host Routing) it makes sense to have the mark, so that the cil_to_netdev can retrieve it without relying on endpoint map or ipcache. So let's always set the mark at the very start of the forwarding path. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
Member
Author
|
/test |
YutaroHayakawa
approved these changes
Nov 3, 2025
11 tasks
This was referenced Dec 5, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Guessing which exact forward paths can benefit from the identity mark is fragile, and it's hard to overlook corner cases. Even when we BPF-redirect a packet to an external interface (with BPF Host Routing) it makes sense to have the mark, so that the cil_to_netdev can retrieve it without relying on endpoint map or ipcache.
So let's always set the mark at the very start of the forwarding path.