From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Yuqi Xu" <xuyuqiabc@gmail.com>, <bpf@vger.kernel.org>
Cc: "Vadim Fedorenko" <vadim.fedorenko@linux.dev>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Kumar Kartikeya Dwivedi" <memxor@gmail.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Song Liu" <song@kernel.org>,
"Yonghong Song" <yonghong.song@linux.dev>,
"Jiri Olsa" <jolsa@kernel.org>,
"Emil Tsalapatis" <emil@etsalapatis.com>,
"Ihor Solodrai" <ihor.solodrai@linux.dev>,
<stable@vger.kernel.org>, "Vega" <vega@nebusec.ai>,
"Ren Wei" <weir@nebusec.ai>, <xuyq21@lenovo.com>
Subject: Re: [PATCH bpf 1/1] bpf: crypto: check params size before reading reserved fields
Date: Sat, 19 Sep 2026 18:17:57 +0000 [thread overview]
Message-ID: <DLJHZR9N1C0I.JZ6KOM8H5DPG@gmail.com> (raw)
In-Reply-To: <4f3ab4b03e79017e215521743996555439bf0bb3.1789802413.git.xuyuqiabc@gmail.com>
On Sat, Sep 19, 2026 at 04:45 PM Yuqi Xu <xuyuqiabc@gmail.com> wrote:
> Fixes: 3e1c6f35409f ("bpf: make common crypto API for TC/XDP programs")
> Cc: stable@vger.kernel.org
bpf_crypto_ctx_create() is only available to syscall progs, so it's
CAP_BPF, and with a short params__sz both outcomes are -EINVAL.
The two bytes don't go anywhere. Fixes tag is enough.
No need to cc stable.
next prev parent reply other threads:[~2026-09-19 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 8:45 [PATCH bpf 0/1] bpf: crypto: check params size before reading reserved fields Yuqi Xu
2026-09-19 8:45 ` [PATCH bpf 1/1] " Yuqi Xu
2026-09-19 18:17 ` Alexei Starovoitov [this message]
2026-09-20 7:24 ` Yuqi Xu
2026-09-19 23:30 ` [PATCH bpf 0/1] " patchwork-bot+netdevbpf
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=DLJHZR9N1C0I.JZ6KOM8H5DPG@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@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=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vadim.fedorenko@linux.dev \
--cc=vega@nebusec.ai \
--cc=weir@nebusec.ai \
--cc=xuyq21@lenovo.com \
--cc=xuyuqiabc@gmail.com \
--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