Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Aditya Sharma <adi.sharma@zohomail.in>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
	martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
	jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
	kpsingh@kernel.org, matt@bobrowski.net, rostedt@goodmis.org,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	shuah@kernel.org, puranjay@kernel.org,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Fix bpf_send_signal_task() from kernel thread context
Date: Sat, 24 Oct 2026 05:10:07 +0000	[thread overview]
Message-ID: <179281860707.1477734.466775423559947933.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261001072449.1377267-1-adi.sharma@zohomail.in>

Hello:

This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu,  1 Oct 2026 12:54:47 +0530 you wrote:
> 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.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] bpf: Remove nmi_uaccess_okay() check in bpf_send_signal_common()
    https://git.kernel.org/bpf/bpf/c/93bd472336ac
  - [bpf-next,v2,2/2] selftests/bpf: Test bpf_send_signal_task() from kernel thread context
    https://git.kernel.org/bpf/bpf/c/2c79610f72bb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-24  5:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01  7:24 [PATCH bpf-next v2 0/2] bpf: Fix bpf_send_signal_task() from kernel thread context Aditya Sharma
2026-10-01  7:24 ` [PATCH bpf-next v2 1/2] bpf: Remove nmi_uaccess_okay() check in bpf_send_signal_common() Aditya Sharma
2026-10-01  7:24 ` [PATCH bpf-next v2 2/2] selftests/bpf: Test bpf_send_signal_task() from kernel thread context Aditya Sharma
2026-10-23 12:45 ` [PATCH bpf-next v2 0/2] bpf: Fix " Aditya Sharma
2026-10-23 21:47   ` Andrii Nakryiko
2026-10-24  5:10 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=179281860707.1477734.466775423559947933.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=adi.sharma@zohomail.in \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=matt@bobrowski.net \
    --cc=memxor@gmail.com \
    --cc=mhiramat@kernel.org \
    --cc=puranjay@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox