From: kernel test robot <lkp@intel.com>
To: Kai Ye <yekai13@huawei.com>, herbert@gondor.apana.org.au
Cc: kbuild-all@lists.01.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, wangzhou1@hisilicon.com,
yekai13@huawei.com
Subject: Re: [PATCH 2/3] crypto: hisilicon/sec - add fallback tfm supporting for XTS mode
Date: Fri, 28 May 2021 22:13:40 +0800 [thread overview]
Message-ID: <202105282256.hUBoOJ3Z-lkp@intel.com> (raw)
In-Reply-To: <1622202126-19237-3-git-send-email-yekai13@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2915 bytes --]
Hi Kai,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on cryptodev/master]
[also build test ERROR on crypto/master linux/master linus/master v5.13-rc3 next-20210528]
[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]
url: https://github.com/0day-ci/linux/commits/Kai-Ye/crypto-hisilicon-supports-new-skciphers-for-new-hardware/20210528-194644
base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/60bae5ed49c53ea90c82125a8295fb72833a3b68
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Kai-Ye/crypto-hisilicon-supports-new-skciphers-for-new-hardware/20210528-194644
git checkout 60bae5ed49c53ea90c82125a8295fb72833a3b68
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=ia64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/crypto/hisilicon/sec2/sec_crypto.c: In function 'sec_aead_crypto':
>> drivers/crypto/hisilicon/sec2/sec_crypto.c:1751:40: error: 'sk_req' undeclared (first use in this function); did you mean 'a_req'?
1751 | return sec_skcipher_soft_crypto(ctx, sk_req, encrypt);
| ^~~~~~
| a_req
drivers/crypto/hisilicon/sec2/sec_crypto.c:1751:40: note: each undeclared identifier is reported only once for each function it appears in
vim +1751 drivers/crypto/hisilicon/sec2/sec_crypto.c
1733
1734 static int sec_aead_crypto(struct aead_request *a_req, bool encrypt)
1735 {
1736 struct crypto_aead *tfm = crypto_aead_reqtfm(a_req);
1737 struct sec_req *req = aead_request_ctx(a_req);
1738 struct sec_ctx *ctx = crypto_aead_ctx(tfm);
1739 int ret;
1740
1741 req->flag = a_req->base.flags;
1742 req->aead_req.aead_req = a_req;
1743 req->c_req.encrypt = encrypt;
1744 req->ctx = ctx;
1745
1746 ret = sec_aead_param_check(ctx, req);
1747 if (unlikely(ret))
1748 return -EINVAL;
1749
1750 if (unlikely(ctx->c_ctx.fallback))
> 1751 return sec_skcipher_soft_crypto(ctx, sk_req, encrypt);
1752
1753 return ctx->req_op->process(ctx, req);
1754 }
1755
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 64433 bytes --]
next prev parent reply other threads:[~2021-05-28 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 11:42 [PATCH 0/3] crypto: hisilicon - supports new skciphers for new hardware Kai Ye
2021-05-28 11:42 ` [PATCH 1/3] crypto: hisilicon/sec - add new skcipher mode for SEC Kai Ye
2021-05-28 11:42 ` [PATCH 2/3] crypto: hisilicon/sec - add fallback tfm supporting for XTS mode Kai Ye
2021-05-28 14:13 ` kernel test robot [this message]
2021-05-29 9:22 ` yekai(A)
2021-05-31 0:51 ` [kbuild-all] " Rong Chen
2021-05-31 1:22 ` yekai(A)
2021-05-28 11:42 ` [PATCH 3/3] crypto: hisilicon/sec - fixup 3des minimum key size declaration Kai Ye
2021-06-03 12:31 ` [PATCH 0/3] crypto: hisilicon - supports new skciphers for new hardware Herbert Xu
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=202105282256.hUBoOJ3Z-lkp@intel.com \
--to=lkp@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@lists.01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
--cc=yekai13@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