From: kernel test robot <lkp@intel.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-crypto@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
David Howells <dhowells@redhat.com>,
Blaise Boscaccy <bboscaccy@linux.microsoft.com>
Subject: Re: [PATCH v3 5/5] crypto: pkcs7: add tests for pkcs7_get_authattr
Date: Thu, 26 Feb 2026 09:12:32 +0800 [thread overview]
Message-ID: <202602260949.uDrsr8hd-lkp@intel.com> (raw)
In-Reply-To: <20260225211907.7368-6-James.Bottomley@HansenPartnership.com>
Hi James,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v7.0-rc1 next-20260225]
[cannot apply to herbert-cryptodev-2.6/master herbert-crypto-2.6/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/James-Bottomley/certs-break-out-pkcs7-check-into-its-own-function/20260226-052454
base: linus/master
patch link: https://lore.kernel.org/r/20260225211907.7368-6-James.Bottomley%40HansenPartnership.com
patch subject: [PATCH v3 5/5] crypto: pkcs7: add tests for pkcs7_get_authattr
config: i386-buildonly-randconfig-002-20260226 (https://download.01.org/0day-ci/archive/20260226/202602260949.uDrsr8hd-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260226/202602260949.uDrsr8hd-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202602260949.uDrsr8hd-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> crypto/asymmetric_keys/pkcs7_key_type.c:99:52: warning: format specifies type 'long' but the argument has type 'size_t' (aka 'unsigned int') [-Wformat]
99 | pr_info("Correctly Got message hash, size=%ld\n", len);
| ~~~ ^~~
| %zu
include/linux/printk.h:584:34: note: expanded from macro 'pr_info'
584 | printk(KERN_INFO pr_fmt(fmt), ##__VA_ARGS__)
| ~~~ ^~~~~~~~~~~
include/linux/printk.h:511:60: note: expanded from macro 'printk'
511 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
| ~~~ ^~~~~~~~~~~
include/linux/printk.h:483:19: note: expanded from macro 'printk_index_wrap'
483 | _p_func(_fmt, ##__VA_ARGS__); \
| ~~~~ ^~~~~~~~~~~
1 warning generated.
vim +99 crypto/asymmetric_keys/pkcs7_key_type.c
48
49 /*
50 * Preparse a PKCS#7 wrapped and validated data blob.
51 */
52 static int pkcs7_preparse(struct key_preparsed_payload *prep)
53 {
54 enum key_being_used_for usage = pkcs7_usage;
55 int ret;
56 struct pkcs7_message *pkcs7;
57 const void *data;
58 size_t len;
59
60 if (usage >= NR__KEY_BEING_USED_FOR) {
61 pr_err("Invalid usage type %d\n", usage);
62 return -EINVAL;
63 }
64
65 ret = verify_pkcs7_signature(NULL, 0,
66 prep->data, prep->datalen,
67 VERIFY_USE_SECONDARY_KEYRING, usage,
68 pkcs7_view_content, prep);
69 if (ret)
70 return ret;
71
72 pkcs7 = pkcs7_parse_message(prep->data, prep->datalen);
73 if (IS_ERR(pkcs7)) {
74 pr_err("pkcs7 parse error\n");
75 return PTR_ERR(pkcs7);
76 }
77
78 /*
79 * the parsed message has no trusted signer, so nothing should
80 * be returned here
81 */
82 ret = pkcs7_get_authattr(pkcs7, OID_messageDigest, &data, &len);
83 if (ret == 0) {
84 pr_err("OID returned when no trust in signer\n");
85 goto out;
86 }
87 /* add trust and check again */
88 ret = validate_pkcs7_trust(pkcs7, VERIFY_USE_SECONDARY_KEYRING);
89 if (ret) {
90 pr_err("validate_pkcs7_trust failed!!\n");
91 goto out;
92 }
93 /* now we should find the OID */
94 ret = pkcs7_get_authattr(pkcs7, OID_messageDigest, &data, &len);
95 if (ret) {
96 pr_err("Failed to get message digest\n");
97 goto out;
98 }
> 99 pr_info("Correctly Got message hash, size=%ld\n", len);
100
101 out:
102 pkcs7_free_message(pkcs7);
103 return 0;
104 }
105
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-26 1:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 21:19 [PATCH v3 0/5] pkcs7: better handling of signed attributes James Bottomley
2026-02-25 21:19 ` [PATCH v3 1/5] certs: break out pkcs7 check into its own function James Bottomley
2026-02-25 21:19 ` [PATCH v3 2/5] crypto: pkcs7: add flag for validated trust on a signed info block James Bottomley
2026-02-25 21:19 ` [PATCH v3 3/5] crypto: pkcs7: allow pkcs7_digest() to be called from pkcs7_trust James Bottomley
2026-02-26 20:31 ` Eric Biggers
2026-02-27 3:50 ` James Bottomley
2026-03-05 7:58 ` Eric Biggers
2026-03-05 14:53 ` James Bottomley
2026-03-05 18:50 ` Eric Biggers
2026-03-05 20:11 ` James Bottomley
2026-03-05 21:36 ` Eric Biggers
2026-03-05 22:06 ` James Bottomley
2026-02-25 21:19 ` [PATCH v3 4/5] crypto: pkcs7: add ability to extract signed attributes by OID James Bottomley
2026-02-25 21:19 ` [PATCH v3 5/5] crypto: pkcs7: add tests for pkcs7_get_authattr James Bottomley
2026-02-26 1:12 ` kernel test robot [this message]
2026-02-26 2:13 ` [PATCH v3 0/5] pkcs7: better handling of signed attributes Eric Biggers
2026-02-26 12:43 ` James Bottomley
2026-03-05 7:55 ` Eric Biggers
2026-03-05 14:46 ` James Bottomley
2026-03-05 18:51 ` Eric Biggers
2026-03-05 20:18 ` James Bottomley
2026-03-05 21:40 ` Eric Biggers
2026-03-05 22:11 ` James Bottomley
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=202602260949.uDrsr8hd-lkp@intel.com \
--to=lkp@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bboscaccy@linux.microsoft.com \
--cc=dhowells@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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