From: kbuild test robot <lkp@intel.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: kbuild-all@01.org, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/6] tpm: move tpm_validate_commmand() to tpm2-space.c
Date: Sat, 3 Nov 2018 19:11:37 +0800 [thread overview]
Message-ID: <201811031928.Eg204A1T%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181103040820.23360-5-jarkko.sakkinen@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2304 bytes --]
Hi Jarkko,
I love your patch! Perhaps something to improve:
[auto build test WARNING on jss-tpmdd/next]
[also build test WARNING on next-20181102]
[cannot apply to v4.19]
[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/Jarkko-Sakkinen/Detach-TPM-space-code-from-tpm_transmit-flow/20181103-183010
base: git://git.infradead.org/users/jjs/linux-tpmdd next
config: i386-randconfig-x002-201843 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
drivers/char/tpm/tpm2-space.c: In function 'tpm2_prepare_space':
>> drivers/char/tpm/tpm2-space.c:335:16: warning: 'cc' may be used uninitialized in this function [-Wmaybe-uninitialized]
chip->last_cc = cc;
~~~~~~~~~~~~~~^~~~
vim +/cc +335 drivers/char/tpm/tpm2-space.c
302
303 int tpm2_prepare_space(struct tpm_chip *chip, struct tpm_space *space, u8 *cmd,
304 size_t cmdsiz)
305 {
306 int rc;
307 int cc;
308
309 if (!space)
310 return 0;
311
312 cc = tpm_validate_command(chip, space, cmd, cmdsiz);
313 if (cc < 0)
314 return cc;
315
316 memcpy(&chip->work_space.context_tbl, &space->context_tbl,
317 sizeof(space->context_tbl));
318 memcpy(&chip->work_space.session_tbl, &space->session_tbl,
319 sizeof(space->session_tbl));
320 memcpy(chip->work_space.context_buf, space->context_buf, PAGE_SIZE);
321 memcpy(chip->work_space.session_buf, space->session_buf, PAGE_SIZE);
322
323 rc = tpm2_load_space(chip);
324 if (rc) {
325 tpm2_flush_space(chip);
326 return rc;
327 }
328
329 rc = tpm2_map_command(chip, cc, cmd);
330 if (rc) {
331 tpm2_flush_space(chip);
332 return rc;
333 }
334
> 335 chip->last_cc = cc;
336 return 0;
337 }
338
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31098 bytes --]
next prev parent reply other threads:[~2018-11-03 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 4:08 [PATCH 0/6] Detach TPM space code from tpm_transmit() flow Jarkko Sakkinen
2018-11-03 4:08 ` [PATCH 1/6] tpm: use tpm_buf in tpm_transmit_cmd() as the IO parameter Jarkko Sakkinen
2018-11-03 4:08 ` [PATCH 2/6] tpm: clean up tpm_try_transmit() error handling flow Jarkko Sakkinen
2018-11-03 4:08 ` [PATCH 3/6] tpm: access command header through struct in tpm_try_transmit() Jarkko Sakkinen
2018-11-03 4:08 ` [PATCH 4/6] tpm: move tpm_validate_commmand() to tpm2-space.c Jarkko Sakkinen
2018-11-03 11:11 ` kbuild test robot [this message]
2018-11-03 4:08 ` [PATCH 5/6] tpm: encapsulate tpm_dev_transmit() Jarkko Sakkinen
2018-11-03 4:08 ` [PATCH 6/6] tpm: move TPM space code out of tpm_transmit() Jarkko Sakkinen
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=201811031928.Eg204A1T%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=kbuild-all@01.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tomas.winkler@intel.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®