| Message ID | 20230424161104.3737-1-laoar.shao@gmail.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | bpf: Fix issues caused by bpf trampoline | expand |
Hello: This series was applied to bpf/bpf-next.git (master) by Alexei Starovoitov <ast@kernel.org>: On Mon, 24 Apr 2023 16:11:02 +0000 you wrote: > The panic caused by fentry[1] drives me to write a testcase[2] to check if > it safe to attach other kernel functions. Unsurprisingly it catches some > issues. This patchset fixes them. > > [1]. https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=c11bd046485d7bf1ca200db0e7d0bdc4bafdd395 > [2]. https://github.com/laoar/ebpf/tree/main/fentry > > [...] Here is the summary with links: - [bpf-next,1/2] bpf: Add __rcu_read_{lock,unlock} into btf id deny list https://git.kernel.org/bpf/bpf-next/c/a0c109dcafb1 - [bpf-next,2/2] fork: Rename mm_init to task_mm_init (no matching commit) You are awesome, thank you!
The panic caused by fentry[1] drives me to write a testcase[2] to check if it safe to attach other kernel functions. Unsurprisingly it catches some issues. This patchset fixes them. [1]. https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=c11bd046485d7bf1ca200db0e7d0bdc4bafdd395 [2]. https://github.com/laoar/ebpf/tree/main/fentry Yafang Shao (2): bpf: Add __rcu_read_{lock,unlock} into btf id deny list fork: Rename mm_init to task_mm_init kernel/bpf/verifier.c | 4 ++++ kernel/fork.c | 6 +++--- 2 files changed, 7 insertions(+), 3 deletions(-)