diff options
| author | Alexei Starovoitov <[email protected]> | 2024-07-22 17:33:28 -0700 |
|---|---|---|
| committer | Andrii Nakryiko <[email protected]> | 2024-07-29 13:09:48 -0700 |
| commit | 02d9fe1c4d987c4b3d272b5217da53280ffa71f5 (patch) | |
| tree | 1382ba050fce1d691687f8084a9615524fe2ae51 /tools/perf/scripts/python/flamegraph.py | |
| parent | e2854bc37344f40a47c6e04a222e65d2669e64dd (diff) | |
| parent | 04d8243b1f83251bd599fdd3ea91e89039b6a557 (diff) | |
Merge branch 'add-bpf-lsm-return-value-range-check-bpf-part'
Xu Kuohai says:
====================
Add BPF LSM return value range check, BPF part
From: Xu Kuohai <[email protected]>
LSM BPF prog may make kernel panic when returning an unexpected value,
such as returning positive value on hook file_alloc_security.
To fix it, series [1] refactored LSM hook return values and added
BPF return value check on top of that. Since the refactoring of LSM
hooks and checking BPF prog return value patches is not closely related,
this series separates BPF-related patches from [1].
v2:
- Update Shung-Hsi's patch with [3]
v1: https://lore.kernel.org/bpf/[email protected]/
Changes to [1]:
1. Extend LSM disabled list to include hooks refactored in [1] to avoid
dependency on the hooks return value refactoring patches.
2. Replace the special case patch for bitwise AND on [-1, 0] with Shung-Hsi's
general bitwise AND improvement patch [2].
3. Remove unused patches.
[1] https://lore.kernel.org/bpf/[email protected]
https://lore.kernel.org/bpf/[email protected]
[2] https://lore.kernel.org/bpf/ykuhustu7vt2ilwhl32kj655xfdgdlm2xkl5rff6tw2ycksovp@ss2n4gpjysnw
[3] https://lore.kernel.org/bpf/[email protected]/
Shung-Hsi Yu (1):
bpf, verifier: improve signed ranges inference for BPF_AND
====================
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Alexei Starovoitov <[email protected]>
Signed-off-by: Andrii Nakryiko <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions