diff options
| author | Alexei Starovoitov <ast@kernel.org> | 2026-10-24 04:00:57 +0000 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2026-10-24 04:00:58 +0000 |
| commit | 2f78620ca9529ef3e25f7ebaa4a1347cb4bcfed5 (patch) | |
| tree | 52567a5ee852dd9593022a8864ff945772bcb90a /include/linux/timerqueue.h | |
| parent | b93cf2c8a0552b544e90e25802e4bf989987d29d (diff) | |
| parent | 2c79610f72bb880cbb42adacec5a4b1b335040bf (diff) | |
Merge branch 'bpf-fix-bpf_send_signal_task-from-kernel-thread-context'
Aditya Sharma says:
====================
bpf: Fix bpf_send_signal_task() from kernel thread context
bpf_send_signal_task() returns -EPERM whenever the calling context is a
kernel thread, even when the signal is for a different task. The
cause is the nmi_uaccess_okay() check in bpf_send_signal_common(),
which is a statement about current and not about the target task.
Patch 1 removes the check, as the signal path does no user memory
access and the check has nothing to guard there.
Patch 2 adds a selftest that sends a signal to a user task from
tp_btf/workqueue_execute_start, where current is always a kworker.
Without patch 1, this test fails on x86.
v1 -> v2:
- Rebase onto current bpf-next.
- Add this cover letter (v1 was sent without one)
- Remove nmi_uaccess_okay() check (as per Andrii)
- Fixed a stale comment above checks in bpf_send_signal_common()
- Gate send_signal_kworker on a new kworker_test global that only this
test sets. (Sashiko AI review)
- Put /* of a multi line comment on its own line (Sashiko AI review)
v1: https://lore.kernel.org/bpf/20260902150439.692725-1-adi.sharma@zohomail.in/
====================
Link: https://patch.msgid.link/20261001072449.1377267-1-adi.sharma@zohomail.in
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'include/linux/timerqueue.h')
0 files changed, 0 insertions, 0 deletions
