Allow struct_ops to get bpf_map during #5668
Closed
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
Author
|
Upstream branch: e8d780d |
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
bpf-next_base
branch
from
9879802 to
dbe33e3
Compare
Author
|
Upstream branch: 821c9e5 |
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
series/987487=>bpf-next
branch
from
6b032f2 to
96d28b6
Compare
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
bpf-next_base
branch
from
dbe33e3 to
6409044
Compare
To allow struct_ops implementors to access the bpf_map during reg() and unreg(), return bpf_map from bpf_struct_ops_get() instead and let callers check the error. Additionally, expose bpf_struct_ops_get() and bpf_struct_ops_put() so that kernel modules can use them. Signed-off-by: Amery Hung <[email protected]>
Author
|
Upstream branch: a6923c0 |
Current struct_ops in bpf_testmod only support attaching single instance. Add multi_st_ops that supports multiple instances. The struct_ops uses map id as the struct_ops id and will reject attachment with an existing id. Signed-off-by: Amery Hung <[email protected]>
…ograms Test multi_st_ops and demonstrate how different bpf programs can call a kfuncs that refers to the struct_ops instance in the same source file by id. The id is defined as a global vairable and initialized before attaching the skeleton. Kfuncs that take the id can hide the argument with a macro to make it almost transparent to bpf program developers. The test involves two struct_ops returning different values from .test_1. In syscall and tracing programs, check if the correct value is returned by a kfunc that calls .test_1. Signed-off-by: Amery Hung <[email protected]>
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
series/987487=>bpf-next
branch
from
96d28b6 to
9ba0d13
Compare
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
bpf-next_base
branch
from
6409044 to
9db1c0b
Compare
Author
|
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=987487 expired. Closing PR. |
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.
Pull request for series with
subject: Allow struct_ops to get bpf_map during
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=987487