fix(ebpf): adjust inode struct to kernel v6.11 #4457
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
- Add support for three different ranges of kernel versions. - For kernel 6.11 and newer, struct inode uses the fields i_ctime_sec and i_ctime_nsec for time. - For kernels 6.6 to 6.10, struct inode uses __i_ctime. - For kernels 6.5 and older, struct inode uses i_ctime. - Align struct inode to the kernel 6.11 structure and mock the inode struct for kernels older than 6.11.
|
/fast-forward |
|
Sorry, I missed your feedback request over the holidays. Looks fine to me and you have merged it already. Thanks! |
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.
1. Explain what the PR does
b54f498 fix(ebpf): adjust inode struct to kernel v6.11
2. Explain how to test it
3. Other comments
Thank you, @agalauner-r7, for providing such a detailed issue report and proposing various solutions to address this issue.
fix: #4391