From: kernel test robot <lkp@intel.com>
To: Nayna Jain <nayna@linux.ibm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Eric Richter <erichte@linux.ibm.com>
Subject: security/integrity/platform_certs/keyring_handler.c:66:16: sparse: sparse: Using plain integer as NULL pointer
Date: Fri, 7 Aug 2020 12:15:52 +0800 [thread overview]
Message-ID: <202008071248.h8qM0KXu%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 86cfccb66937dd6cbf26ed619958b9e587e6a115
commit: ad723674d6758478829ee766e3f1a2a24d56236f x86/efi: move common keyring handler functions to new file
date: 9 months ago
config: x86_64-randconfig-s022-20200807 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-117-g8c7aee71-dirty
git checkout ad723674d6758478829ee766e3f1a2a24d56236f
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
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 >>)
>> security/integrity/platform_certs/keyring_handler.c:66:16: sparse: sparse: Using plain integer as NULL pointer
security/integrity/platform_certs/keyring_handler.c:79:16: sparse: sparse: Using plain integer as NULL pointer
vim +66 security/integrity/platform_certs/keyring_handler.c
57
58 /*
59 * Return the appropriate handler for particular signature list types found in
60 * the UEFI db and MokListRT tables.
61 */
62 __init efi_element_handler_t get_handler_for_db(const efi_guid_t *sig_type)
63 {
64 if (efi_guidcmp(*sig_type, efi_cert_x509_guid) == 0)
65 return add_to_platform_keyring;
> 66 return 0;
67 }
68
---
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: 34144 bytes --]
reply other threads:[~2020-08-07 4:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202008071248.h8qM0KXu%lkp@intel.com \
--to=lkp@intel.com \
--cc=erichte@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nayna@linux.ibm.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®