-
Notifications
You must be signed in to change notification settings - Fork 5
bpftool: add kernel.kptr_restrict hint for no instructions #5709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bpftool: add kernel.kptr_restrict hint for no instructions #5709
Conversation
|
Upstream branch: fa47913 |
8821f0b to
71f5f86
Compare
|
Upstream branch: fa47913 |
5541bcb to
87358aa
Compare
|
Upstream branch: 0786654 |
dd1d8bc to
9984277
Compare
5e1a4c1 to
91606c1
Compare
|
Upstream branch: dc0fe95 |
9984277 to
1079ce9
Compare
91606c1 to
9e5d665
Compare
|
Upstream branch: c80d797 |
1079ce9 to
1c70667
Compare
9e5d665 to
f86fd37
Compare
|
Upstream branch: abdaf49 |
1c70667 to
4ef4b06
Compare
f86fd37 to
2842450
Compare
|
Upstream branch: 3ec8560 |
4ef4b06 to
739bf84
Compare
2842450 to
53b8665
Compare
|
Upstream branch: 1274163 |
739bf84 to
03b334e
Compare
53b8665 to
26f4a08
Compare
from bpftool github repo issue [0], when Linux distribution kernel.kptr_restrict is set to 2, bpftool prog dump jited returns "no instructions returned", this message can be puzzling to bpftool users who is not familiar with kernel BPF internal, so add small hint for bpftool users to check kernel.kptr_restrict setting. Set kernel.kptr_restrict to expose kernel address to allow bpftool prog dump jited to dump the jited bpf program instructions. [0]: libbpf/bpftool#184 Signed-off-by: Vincent Li <[email protected].
|
Upstream branch: d87fdb1 |
03b334e to
cd6deda
Compare
|
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=989432 expired. Closing PR. |
Pull request for series with
subject: bpftool: add kernel.kptr_restrict hint for no instructions
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=989432