Merged
Conversation
Encountered strange failures with kprobe tests. All kernel symbols had
non-0 suffixes, like memblock_find_in_range.constprop.13. Rebuilding
the kernel fixed that for some reason.
--- FAIL: TestKprobeOffset (0.27s)
--- FAIL: TestKprobeOffset/valid_offset#02 (0.11s)
kprobe_amd64_test.go:69: unexpected err: 'creating perf_kprobe PMU: symbol '__x64_inet6_release+0x17' not found: file does not exist'
--- FAIL: TestKprobeOffset/bad_insn_boundary#01 (0.01s)
kprobe_amd64_test.go:63: expected err 'file does not exist', got '<nil>'
--- FAIL: TestKprobe (0.21s)
--- FAIL: TestKprobe/async_resume.cold (0.04s)
kprobe_test.go:36: creating perf_kprobe PMU: symbol '__x64_async_resume.cold+0x0' not found: file does not exist
--- FAIL: TestKprobe/echo_char.isra.0 (0.04s)
kprobe_test.go:36: creating perf_kprobe PMU: symbol '__x64_echo_char.isra.0+0x0' not found: file does not exist
--- FAIL: TestKprobe/get_buffer.constprop.0 (0.04s)
kprobe_test.go:36: creating perf_kprobe PMU: symbol '__x64_get_buffer.constprop.0+0x0' not found: file does not exist
--- FAIL: TestKprobe/unregister_kprobes.part.0 (0.04s)
kprobe_test.go:36: creating perf_kprobe PMU: symbol '__x64_unregister_kprobes.part.0+0x0' not found: file does not exist
--- FAIL: TestKretprobe (0.19s)
--- FAIL: TestKretprobe/async_resume.cold (0.04s)
kprobe_test.go:64: creating perf_kprobe PMU: symbol '__x64_async_resume.cold+0x0' not found: file does not exist
--- FAIL: TestKretprobe/echo_char.isra.0 (0.04s)
kprobe_test.go:64: creating perf_kprobe PMU: symbol '__x64_echo_char.isra.0+0x0' not found: file does not exist
--- FAIL: TestKretprobe/get_buffer.constprop.0 (0.04s)
kprobe_test.go:64: creating perf_kprobe PMU: symbol '__x64_get_buffer.constprop.0+0x0' not found: file does not exist
--- FAIL: TestKretprobe/unregister_kprobes.part.0 (0.04s)
kprobe_test.go:64: creating perf_kprobe PMU: symbol '__x64_unregister_kprobes.part.0+0x0' not found: file does not exist
Time to Dockerize the build process.
Signed-off-by: Timo Beckers <[email protected]>
1 task
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
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.
Encountered strange failures with kprobe tests. All kernel symbols had non-0 suffixes, like
memblock_find_in_range.constprop.13. Rebuilding the kernel fixed that for some reason.Time to Dockerize the build process.
@lmb The 5.17 that's currently in the repo was built using the toolchain Dockerfile you were working on, which appears to contain gcc 8.3.0 and probably names optimized symbols a little differently from newer gcc. Let's discuss this offline.