From: kernel test robot <lkp@intel.com>
To: Peter Gonda <pgonda@google.com>, thomas.lendacky@amd.com
Cc: kbuild-all@lists.01.org, David Rientjes <rientjes@google.com>,
Peter Gonda <pgonda@google.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Marc Orr <marcorr@google.com>, Joerg Roedel <jroedel@suse.de>,
Herbert Xu <herbert@gondor.apana.org.au>,
John Allen <john.allen@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 4/4] crypto: ccp - Add SEV_INIT_EX support
Date: Fri, 29 Oct 2021 17:27:03 +0800 [thread overview]
Message-ID: <202110291731.tcPzRu5q-lkp@intel.com> (raw)
In-Reply-To: <20211028175749.1219188-5-pgonda@google.com>
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
Hi Peter,
I love your patch! Perhaps something to improve:
[auto build test WARNING on herbert-crypto-2.6/master]
[also build test WARNING on linus/master v5.15-rc7]
[cannot apply to herbert-cryptodev-2.6/master next-20211028]
[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/Peter-Gonda/Add-SEV_INIT_EX-support/20211029-020022
base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git master
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/0day-ci/linux/commit/aa961b54617e0edd40b4df9d9d159014cabb7953
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Peter-Gonda/Add-SEV_INIT_EX-support/20211029-020022
git checkout aa961b54617e0edd40b4df9d9d159014cabb7953
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/crypto/ccp/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/crypto/ccp/sev-dev.c:187:68: sparse: sparse: Using plain integer as NULL pointer
vim +187 drivers/crypto/ccp/sev-dev.c
172
173 static int sev_read_nv_memory(void)
174 {
175 struct file *fp;
176 ssize_t nread;
177
178 if (!sev_init_ex_nv_address)
179 return -EOPNOTSUPP;
180
181 fp = filp_open(init_ex_path, O_RDONLY, 0);
182 if (IS_ERR(fp)) {
183 dev_err(psp_master->dev, "sev could not open file for read\n");
184 return PTR_ERR(fp);
185 }
186
> 187 nread = kernel_read(fp, sev_init_ex_nv_address, NV_LENGTH, 0);
188 dev_dbg(psp_master->dev, "sev NV read %d bytes\n", nread);
189 filp_close(fp, NULL);
190 return 0;
191 }
192
---
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: 42204 bytes --]
next prev parent reply other threads:[~2021-10-29 9:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 17:57 [PATCH 0/4] Add SEV_INIT_EX support Peter Gonda
2021-10-28 17:57 ` [PATCH 1/4] crypto: ccp - Fix SEV_INIT error logging on init Peter Gonda
2021-10-29 13:41 ` Tom Lendacky
2021-11-01 16:28 ` Marc Orr
2021-10-28 17:57 ` [PATCH 2/4] crypto: ccp - Move SEV_INIT retry for corrupted data Peter Gonda
2021-10-29 13:42 ` Tom Lendacky
2021-11-01 16:28 ` Marc Orr
2021-10-28 17:57 ` [PATCH 3/4] crypto: ccp - Refactor out sev_fw_alloc() Peter Gonda
2021-10-29 13:48 ` Tom Lendacky
2021-10-29 15:13 ` Peter Gonda
2021-11-01 16:29 ` Marc Orr
2021-10-28 17:57 ` [PATCH 4/4] crypto: ccp - Add SEV_INIT_EX support Peter Gonda
2021-10-29 9:27 ` kernel test robot [this message]
2021-10-29 14:45 ` Tom Lendacky
2021-10-29 17:26 ` Peter Gonda
2021-10-29 17:56 ` Tom Lendacky
2021-11-01 17:18 ` Peter Gonda
[not found] ` <SN6PR12MB27981792BC31C8FB0CB169B5F7879@SN6PR12MB2798.namprd12.prod.outlook.com>
2021-11-01 17:16 ` Peter Gonda
2021-11-01 16:30 ` Marc Orr
2021-11-01 16:31 ` [PATCH 0/4] " Marc Orr
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=202110291731.tcPzRu5q-lkp@intel.com \
--to=lkp@intel.com \
--cc=brijesh.singh@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=jroedel@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=marcorr@google.com \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=rientjes@google.com \
--cc=thomas.lendacky@amd.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