From: kbuild test robot <lkp@intel.com>
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Cc: kbuild-all@01.org, agk@redhat.com, snitzer@redhat.com,
herbert@gondor.apana.org.au, dm-devel@redhat.com,
linux-kernel@vger.kernel.org, wangxiongfeng2@huawei.com,
broonie@kernel.org, arnd@arndb.de, jonathan.cameron@huawei.com
Subject: Re: [PATCH 4/5] crypto: Add IV generation templates
Date: Fri, 20 Jul 2018 02:14:54 +0800 [thread overview]
Message-ID: <201807200243.21tygjmy%fengguang.wu@intel.com> (raw)
In-Reply-To: <1531899055-29362-5-git-send-email-wangxiongfeng2@huawei.com>
Hi Xiongfeng,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on cryptodev/master]
[also build test WARNING on v4.18-rc5 next-20180719]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Xiongfeng-Wang/crypto-add-IV-generation-templates/20180719-034438
base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> crypto/geniv.c:303:9: sparse: Variable length array is used.
crypto/geniv.c:568:9: sparse: Variable length array is used.
crypto/geniv.c:729:9: sparse: Variable length array is used.
include/linux/slab.h:631:13: sparse: undefined identifier '__builtin_mul_overflow'
include/linux/slab.h:631:13: sparse: not a function <noident>
>> crypto/geniv.c:1482:17: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [unsigned] [long] [long long] [usertype] <noident> @@ got long] [long long] [usertype] <noident> @@
crypto/geniv.c:1482:17: expected unsigned long long [unsigned] [long] [long long] [usertype] <noident>
crypto/geniv.c:1482:17: got restricted __le64 [usertype] <noident>
>> crypto/geniv.c:1543:17: sparse: cast to restricted __le64
crypto/geniv.c:1580:17: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [unsigned] [long] [long long] [usertype] <noident> @@ got long] [long long] [usertype] <noident> @@
crypto/geniv.c:1580:17: expected unsigned long long [unsigned] [long] [long long] [usertype] <noident>
crypto/geniv.c:1580:17: got restricted __le64 [usertype] <noident>
>> crypto/geniv.c:1912:32: sparse: expression using sizeof(void)
include/linux/slab.h:631:13: sparse: call with no type!
vim +303 crypto/geniv.c
298
299 /* Initialise ESSIV - compute salt but no local memory allocations */
300 static int crypt_iv_essiv_init(struct geniv_ctx *ctx)
301 {
302 struct geniv_essiv_private *essiv = &ctx->iv_gen_private.essiv;
> 303 AHASH_REQUEST_ON_STACK(req, essiv->hash_tfm);
304 struct scatterlist sg;
305 struct crypto_cipher *essiv_tfm;
306 int err;
307
308 sg_init_one(&sg, ctx->key, ctx->key_size);
309 ahash_request_set_tfm(req, essiv->hash_tfm);
310 ahash_request_set_callback(req, CRYPTO_TFM_REQ_MAY_SLEEP, NULL, NULL);
311 ahash_request_set_crypt(req, &sg, essiv->salt, ctx->key_size);
312
313 err = crypto_ahash_digest(req);
314 ahash_request_zero(req);
315 if (err)
316 return err;
317
318 essiv_tfm = ctx->iv_private;
319
320 return crypto_cipher_setkey(essiv_tfm, essiv->salt,
321 crypto_ahash_digestsize(essiv->hash_tfm));
322 }
323
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-07-19 18:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 7:30 [PATCH 0/5] crypto: add " Xiongfeng Wang
2018-07-18 7:30 ` [PATCH 1/5] crypto: api - introduce API to (un)register a array of templates Xiongfeng Wang
2018-07-18 7:30 ` [PATCH 2/5] crypto: ccm - use template array registering API to simplify the code Xiongfeng Wang
2018-07-18 7:30 ` [PATCH 3/5] crypto: gcm " Xiongfeng Wang
2018-07-18 7:30 ` [PATCH 4/5] crypto: Add IV generation templates Xiongfeng Wang
2018-07-18 8:16 ` Milan Broz
2018-07-18 8:48 ` Xiongfeng Wang
2018-07-18 13:11 ` Mike Snitzer
2018-07-18 16:46 ` Mark Brown
2018-07-18 17:17 ` Milan Broz
2018-07-18 17:47 ` Mark Brown
2018-07-19 1:46 ` Xiongfeng Wang
2018-07-19 8:50 ` Arnd Bergmann
2018-07-19 8:54 ` Herbert Xu
2018-07-19 13:30 ` Mark Brown
2018-07-19 18:14 ` kbuild test robot [this message]
2018-07-18 7:30 ` [PATCH 5/5] dm-crypt: modify dm-crypt to rely on " Xiongfeng Wang
2018-07-18 10:59 ` [PATCH 0/5] crypto: add " Arnd Bergmann
2018-07-18 15:34 ` Ard Biesheuvel
2018-07-19 10:55 ` Xiongfeng Wang
2018-07-19 14:08 ` Ard Biesheuvel
2018-07-19 15:50 ` Mark Brown
2018-07-20 1:02 ` Ard Biesheuvel
2018-07-20 11:45 ` Mark Brown
2018-07-20 12:23 ` Ard Biesheuvel
2018-07-20 12:32 ` Mark Brown
2018-07-22 13:39 ` Gilad Ben-Yossef
2018-07-23 0:13 ` Ard Biesheuvel
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=201807200243.21tygjmy%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=agk@redhat.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=dm-devel@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jonathan.cameron@huawei.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=wangxiongfeng2@huawei.com \
/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®