link: expose syscall wrapper symbol helper#2033
Open
arunsingh wants to merge 1 commit into
Open
Conversation
Signed-off-by: Arun Singh <arunsingh.in@gmail.com>
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
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.
Fixes #1891
I have exposed a small helper for deriving platform-specific syscall wrapper symbols, then use it from the kprobe_multi syscall attach test.
Kprobe/Kretprobe can retry syscall symbols with the platform prefix, but doing the same automatically for kprobe_multi is ambiguous because a multi-attach list can contain both syscall entrypoints and ordinary kernel functions. The helper lets callers opt in per symbol without changing KprobeMulti attach semantics.
Tests:
Also attempted
go test -exec sudo ./...in the Ubuntu VM. The focused link tests passed; the broad run hit unrelatedcmd/bpf2gomodule-cache setup withGOPROXY=offand an unrelatedfeatures/LircMode2kernel capability failure.