From: patchwork-bot+netdevbpf@kernel.org
To: Mahe Tardy <mahe.tardy@gmail.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
daniel@iogearbox.net, davem@davemloft.net, eddyz87@gmail.com,
edumazet@google.com, john.fastabend@gmail.com, kuba@kernel.org,
liamwisehart@meta.com, martin.lau@linux.dev, pabeni@redhat.com,
song@kernel.org, netdev@vger.kernel.org, sdf.kernel@gmail.com,
ameryhung@gmail.com, kuniyu@google.com, memxor@gmail.com,
jiayuan.chen@linux.dev, almagui@kernel.org
Subject: Re: [PATCH bpf-next v7 1/2] bpf: Allow ksock connect/send calls from wq
Date: Fri, 16 Oct 2026 17:00:04 +0000 [thread overview]
Message-ID: <179217000494.875581.6270942748112870456.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016133318.33999-1-mahe.tardy@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 16 Oct 2026 13:33:17 +0000 you wrote:
> The initial ksock implementation, commit 7ae4eb14c5f9 ("bpf: Add ksock
> kfuncs"), kept LSM checks from the kfunc calls and disallowed
> asynchronous workqueues because worker credentials differ from those of
> the triggering task. However, discussions at Plumbers 2026[^1] revealed
> that bypassing LSM checks for BPF-created sockets could be acceptable.
>
> This patch allows workqueue use while retaining LSM checks for now,
> paving the way to call bpf_ksock_connect() and bpf_ksock_send() from
> non-sleepable programs, such as tracing programs, in future patches.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/2] bpf: Allow ksock connect/send calls from wq
https://git.kernel.org/bpf/bpf-next/c/60bbe76a3f9e
- [bpf-next,v7,2/2] selftests/bpf: Test ksock connect/send calls from wq
https://git.kernel.org/bpf/bpf-next/c/242d8416f60c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-16 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 13:33 [PATCH bpf-next v7 1/2] bpf: Allow ksock connect/send calls from wq Mahe Tardy
2026-10-16 13:33 ` [PATCH bpf-next v7 2/2] selftests/bpf: Test " Mahe Tardy
2026-10-16 17:00 ` 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=179217000494.875581.6270942748112870456.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almagui@kernel.org \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=liamwisehart@meta.com \
--cc=mahe.tardy@gmail.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.com \
--cc=song@kernel.org \
/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