From: sashiko-bot@kernel.org
To: "Blaise Boscaccy" <bboscaccy@linux.microsoft.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v7 03/10] crypto: pkcs7: add tests for pkcs7_get_authattr
Date: Fri, 08 May 2026 00:35:13 +0000 [thread overview]
Message-ID: <20260508003514.02A36C2BCB2@smtp.kernel.org> (raw)
In-Reply-To: <20260507191416.2984054-4-bboscaccy@linux.microsoft.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Test failures in `pkcs7_preparse` are silently masked because the function unconditionally returns 0 instead of propagating the error code.
--
commit 49875871a24595817e686cb5ad55b01eebf05536
Author: James Bottomley <James.Bottomley@HansenPartnership.com>
crypto: pkcs7: add tests for pkcs7_get_authattr
Add example code to the test module pkcs7_key_type.c that verifies a message
and then pulls out a known authenticated attribute.
> diff --git a/crypto/asymmetric_keys/pkcs7_key_type.c b/crypto/asymmetric_keys/pkcs7_key_type.c
> index b930d3bbf1af5..e0b1ce0202f6d 100644
> --- a/crypto/asymmetric_keys/pkcs7_key_type.c
> +++ b/crypto/asymmetric_keys/pkcs7_key_type.c
[ ... ]
> @@ -51,16 +52,57 @@ static int pkcs7_view_content(void *ctx, const void *data, size_t len,
> static int pkcs7_preparse(struct key_preparsed_payload *prep)
> {
[ ... ]
> + /*
> + * the parsed message has no trusted signer, so nothing should
> + * be returned here
> + */
> + ret = pkcs7_get_authattr(pkcs7, OID_messageDigest, &data, &len);
> + if (ret == 0) {
> + pr_err("OID returned when no trust in signer\n");
> + goto out;
If the test fails here, does this need to set ret to a negative error code
like -EINVAL before jumping to the out label? Since ret is 0 here, returning
ret at the end would still signal success.
> + }
> + /* add trust and check again */
> + ret = verify_pkcs7_message_sig(NULL, 0, pkcs7,
> + VERIFY_USE_SECONDARY_KEYRING, usage,
> + NULL, NULL);
> + if (ret) {
> + pr_err("verify_pkcs7_message_sig failed!!\n");
> + goto out;
> + }
> + /* now we should find the OID */
> + ret = pkcs7_get_authattr(pkcs7, OID_messageDigest, &data, &len);
> + if (ret) {
> + pr_err("Failed to get message digest\n");
> + goto out;
> + }
> + pr_info("Correctly Got message hash, size=%zu\n", len);
> +
> + out:
> + pkcs7_free_message(pkcs7);
> + return 0;
Should this return ret instead of 0? If any of the earlier assertions fail
and jump to the out label, returning 0 unconditionally discards the error
state and signals a successful key instantiation to the keys subsystem.
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260507191416.2984054-1-bboscaccy@linux.microsoft.com?part=3
next prev parent reply other threads:[~2026-05-08 0:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 19:13 [PATCH v7 00/10] Reintroduce Hornet LSM Blaise Boscaccy
2026-05-07 19:13 ` [PATCH v7 01/10] crypto: pkcs7: add flag for validated trust on a signed info block Blaise Boscaccy
2026-05-07 23:51 ` sashiko-bot
2026-05-07 19:13 ` [PATCH v7 02/10] crypto: pkcs7: add ability to extract signed attributes by OID Blaise Boscaccy
2026-05-08 0:14 ` sashiko-bot
2026-05-07 19:13 ` [PATCH v7 03/10] crypto: pkcs7: add tests for pkcs7_get_authattr Blaise Boscaccy
2026-05-08 0:35 ` sashiko-bot [this message]
2026-05-07 19:13 ` [PATCH v7 04/10] lsm: framework for BPF integrity verification Blaise Boscaccy
2026-05-08 1:09 ` sashiko-bot
2026-05-07 19:13 ` [PATCH v7 05/10] lsm: security: Add additional enum values for bpf integrity checks Blaise Boscaccy
2026-05-07 19:14 ` [PATCH v7 06/10] security: Hornet LSM Blaise Boscaccy
2026-05-08 2:07 ` sashiko-bot
2026-05-07 19:14 ` [PATCH v7 07/10] hornet: Introduce gen_sig Blaise Boscaccy
2026-05-08 2:22 ` sashiko-bot
2026-05-07 19:14 ` [PATCH v7 08/10] hornet: Add a light skeleton data extractor scripts Blaise Boscaccy
2026-05-08 2:35 ` sashiko-bot
2026-05-07 19:14 ` [PATCH v7 09/10] selftests/hornet: Add a selftest for the Hornet LSM Blaise Boscaccy
2026-05-08 2:58 ` sashiko-bot
2026-05-07 19:14 ` [PATCH v7 10/10] ipe: Add BPF program load policy enforcement via Hornet integration Blaise Boscaccy
2026-05-08 4:21 ` sashiko-bot
2026-05-08 18:40 ` Fan Wu
2026-05-07 20:57 ` [PATCH v7 00/10] Reintroduce Hornet LSM Paul Moore
2026-05-07 21:58 ` Eric Biggers
2026-05-07 22:22 ` Paul Moore
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=20260508003514.02A36C2BCB2@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bboscaccy@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=sashiko@lists.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