bpf: Fix VTEP compilation error #24152
Merged
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
Compilation fails when VTEP is enabled because two variables conflicts (have the same name). struct vtep_value *info conflicts with struct remote_endpoint_info *info. This commit fixes it. The compilation tests will be extended in a separate patchset to cover this. Fixes: e625cde ("bpf: Free packet mark on bpf_overlay recirculation") Signed-off-by: Paul Chaignon <paul@cilium.io>
pchaigno
added
sig/datapath
jibi
approved these changes
Mar 3, 2023
|
VTEP isn't covered in end-to-end tests. Marking ready to merge. |
pchaigno
added
the
ready-to-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Compilation fails when VTEP is enabled because two variables conflicts (have the same name).
struct vtep_value *infoconflicts withstruct remote_endpoint_info *info. This pull request fixes it.The compilation tests will be extended in a separate pull request (cf. #24122) to cover this.
The compilation error didn't make it into any release.
Fixes: #24030.