From: patchwork-bot+netdevbpf@kernel.org
To: Weixie Cui <523516579@qq.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
cuiweixie@gmail.com
Subject: Re: [PATCH bpf] bpf: propagate kvmemdup_bpfptr errors from bpf_prog_verify_signature
Date: Tue, 24 Mar 2026 16:24:10 +0000 [thread overview]
Message-ID: <177436945061.1152246.118300165179191472.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_C9C5B2B28413D6303D505CD02BFEA4708C07@qq.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 21 Mar 2026 14:08:00 +0800 you wrote:
> From: Weixie Cui <cuiweixie@gmail.com>
>
> kvmemdup_bpfptr() returns -EFAULT when the user pointer cannot be
> copied, and -ENOMEM on allocation failure. The error path always
> returned -ENOMEM, misreporting bad addresses as out-of-memory.
>
> Return PTR_ERR(sig) so user space gets the correct errno.
>
> [...]
Here is the summary with links:
- [bpf] bpf: propagate kvmemdup_bpfptr errors from bpf_prog_verify_signature
https://git.kernel.org/bpf/bpf-next/c/ad2f7ed0ee91
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-03-24 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 6:08 [PATCH bpf] bpf: propagate kvmemdup_bpfptr errors from bpf_prog_verify_signature Weixie Cui
2026-03-21 9:11 ` Jiri Olsa
2026-03-24 16:24 ` 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=177436945061.1152246.118300165179191472.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=523516579@qq.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cuiweixie@gmail.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--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