From: patchwork-bot+netdevbpf@kernel.org
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
memxor@gmail.com, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
sdf@fomichev.me, sashiko-bot@kernel.org, kernel-team@meta.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf, cgroup: Don't lose errors in effective BPF_LSM_CGROUP queries
Date: Sat, 14 Nov 2026 18:50:11 +0000 [thread overview]
Message-ID: <179468221178.2337414.12793151681977264587.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261112183804.1171535-1-shakeel.butt@linux.dev>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 12 Nov 2026 10:38:03 -0800 you wrote:
> An effective BPF_LSM_CGROUP query walks one attach type per LSM hook.
> __cgroup_bpf_query() sets ret to -ENOSPC before the loop when prog_cnt
> is too small, but the effective branch then overwrites ret with each
> type's copy result:
>
> - If the buffer runs out exactly at the end of a type, the last copy
> returns 0 and the query returns 0 instead of -ENOSPC.
> - If one type's copy faults and a later one succeeds, the query returns
> 0 instead of -EFAULT.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf, cgroup: Don't lose errors in effective BPF_LSM_CGROUP queries
https://git.kernel.org/bpf/bpf/c/e6cd32b8dbea
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-11-14 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 18:38 Shakeel Butt
2026-11-14 18:50 ` 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=179468221178.2337414.12793151681977264587.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sashiko-bot@kernel.org \
--cc=sdf@fomichev.me \
--cc=shakeel.butt@linux.dev \
--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
all inboxes | Powered by JetHome®