From: Eric Biggers <ebiggers@kernel.org>
To: bot+bpf-ci@kernel.org
Cc: bpf@vger.kernel.org, vadim.fedorenko@linux.dev, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, ihor.solodrai@linux.dev,
john.fastabend@gmail.com, kmehltretter@gmail.com,
martin.lau@kernel.org, mason@kernel.org
Subject: Re: [PATCH bpf-next] bpf: crypto: Use AES-CBC and AES-ECB libraries
Date: Mon, 31 Aug 2026 15:43:08 -0700 [thread overview]
Message-ID: <20260831224308.GJ86114@quark> (raw)
In-Reply-To: <20260831215937.GG86114@quark>
On Mon, Aug 31, 2026 at 02:59:39PM -0700, Eric Biggers wrote:
> Almost every kernel has CRYPTO and CRYPTO_SKCIPHER2 enabled anyway, and
> CRYPTO_SKCIPHER2 also enables ECB support. So the change isn't actually
> as drastic as the bot implies, but I'd be glad to give BPF_CRYPTO a
> prompt if the BPF folks are okay with that.
I don't see other examples of kfuncs with visible kconfig options. The
convention is to automatically enable them when the parent subsystem is
enabled.
It feels like bpf crypto is a de facto standalone feature, so I'm not
sure how well that applies here. Regardless, for now I'll use "depends
on CRYPTO_LIB_AES_CBC" and "depends on CRYPTO_LIB_AES_ECB".
- Eric
next prev parent reply other threads:[~2026-08-31 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 19:21 Eric Biggers
2026-08-31 20:29 ` bot+bpf-ci
2026-08-31 21:59 ` Eric Biggers
2026-08-31 22:43 ` Eric Biggers [this message]
2026-08-31 21:25 ` Karl Mehltretter
2026-08-31 21:48 ` Eric Biggers
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=20260831224308.GJ86114@quark \
--to=ebiggers@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kmehltretter@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mason@kernel.org \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=vadim.fedorenko@linux.dev \
--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®