[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <969faf338b31962ef7b624f47a6fa887c04ab65c49e8470dc267658ecedcb07a@mail.kernel.org>
Date: Fri, 5 Dec 2025 18:05:41 +0000 (UTC)
From: bot+bpf-ci@...nel.org
To: git@...ielhodges.dev,ast@...nel.org,daniel@...earbox.net,andrii@...nel.org,vadim.fedorenko@...ux.dev
Cc: martin.lau@...ux.dev,eddyz87@...il.com,song@...nel.org,yonghong.song@...ux.dev,john.fastabend@...il.com,kpsingh@...nel.org,sdf@...ichev.me,haoluo@...gle.com,jolsa@...nel.org,herbert@...dor.apana.org.au,davem@...emloft.net,shuah@...nel.org,bpf@...r.kernel.org,linux-crypto@...r.kernel.org,linux-kselftest@...r.kernel.org,linux-kernel@...r.kernel.org,git@...ielhodges.dev,ast@...nel.org,andrii@...nel.org,daniel@...earbox.net,martin.lau@...nel.org,eddyz87@...il.com,yonghong.song@...ux.dev,clm@...a.com,ihor.solodrai@...ux.dev
Subject: Re: [PATCH bpf-next v2 1/5] crypto: Add BPF hash algorithm type registration module
> diff --git a/crypto/Makefile b/crypto/Makefile
> index 16a35649dd91..853dff375906 100644
> --- a/crypto/Makefile
> +++ b/crypto/Makefile
[ ... ]
> diff --git a/crypto/bpf_crypto_shash.c b/crypto/bpf_crypto_shash.c
> new file mode 100644
> index 000000000000..39032e7dd602
> --- /dev/null
> +++ b/crypto/bpf_crypto_shash.c
[ ... ]
> +static const struct bpf_crypto_type bpf_crypto_shash_type = {
> + .alloc_tfm = bpf_crypto_shash_alloc_tfm,
> + .free_tfm = bpf_crypto_shash_free_tfm,
> + .has_algo = bpf_crypto_shash_has_algo,
> + .hash = bpf_crypto_shash_hash,
> + .digestsize = bpf_crypto_shash_digestsize,
> + .get_flags = bpf_crypto_shash_get_flags,
> + .owner = THIS_MODULE,
> + .name = "hash",
> +};
Does this code compile? The struct bpf_crypto_type definition in
include/linux/bpf_crypto.h doesn't have .hash or .digestsize fields at
this commit. The commit message says "Update the bpf_crypto_type
interface with hash-specific callbacks" but the interface wasn't
actually updated in this commit.
Looking forward in the git history, commit 51e5f5be27dc adds these
fields to the interface. Should that commit come before this one for
bisectability?
---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
CI run summary: https://github.com/kernel-patches/bpf/actions/runs/19971392632
Powered by blists - more mailing lists