elf: Apply same kern_version.SUBLEVEL clamping as done by kernel #309
Conversation
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
When SUBLEVEL of the kernel version approaches 255, it is clamped to 255 to avoid impacting the PATCHLEVEL. This is introduced in different versions depending on the branch. For example, for 4.19 kernel see the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a256aac5b7000 In order to avoid failing the kernel version check in the BPF syscall, the library must apply the same clamping. Signed-off-by: David Verbeiren <david.verbeiren@tessares.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
ELF BPF module loading is failing on kernel 4.19.222 (and probably similar fails on 4.14.252) because of the clamping done on the kern_version SUBLEVEL value (clamped to 255 starting at 222). The library must do the same in order to avoid failing the kernel version check in the BPF syscall.