linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: kbuild-all@01.org, clang-built-linux@googlegroups.com,
	linux-kernel@vger.kernel.org,
	Palmer Dabbelt <palmerdabbelt@google.com>,
	Ard Biesheuvel <ardb@kernel.org>
Subject: security/integrity/platform_certs/keyring_handler.c:62:30: warning: no previous prototype for function 'get_handler_for_db'
Date: Fri, 5 Mar 2021 13:05:12 +0800	[thread overview]
Message-ID: <202103051308.wEuZoSCn-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4127 bytes --]

Hi Atish,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   3cb60ee6323968b694208c4cbd56a7176396e931
commit: d7071743db31b4f6898b1c742e4b451bb4bc4b02 RISC-V: Add EFI stub support.
date:   5 months ago
config: riscv-randconfig-r002-20210305 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 4d90e460bcc7b3e5ff6c7e2e05e974772489c4b8)
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
        # install riscv cross compiling tool for clang build
        # apt-get install binutils-riscv64-linux-gnu
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d7071743db31b4f6898b1c742e4b451bb4bc4b02
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout d7071743db31b4f6898b1c742e4b451bb4bc4b02
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=riscv 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> security/integrity/platform_certs/keyring_handler.c:62:30: warning: no previous prototype for function 'get_handler_for_db' [-Wmissing-prototypes]
   __init efi_element_handler_t get_handler_for_db(const efi_guid_t *sig_type)
                                ^
   security/integrity/platform_certs/keyring_handler.c:62:8: note: declare 'static' if the function is not intended to be used outside of this translation unit
   __init efi_element_handler_t get_handler_for_db(const efi_guid_t *sig_type)
          ^
          static 
>> security/integrity/platform_certs/keyring_handler.c:73:30: warning: no previous prototype for function 'get_handler_for_dbx' [-Wmissing-prototypes]
   __init efi_element_handler_t get_handler_for_dbx(const efi_guid_t *sig_type)
                                ^
   security/integrity/platform_certs/keyring_handler.c:73:8: note: declare 'static' if the function is not intended to be used outside of this translation unit
   __init efi_element_handler_t get_handler_for_dbx(const efi_guid_t *sig_type)
          ^
          static 
   2 warnings generated.


vim +/get_handler_for_db +62 security/integrity/platform_certs/keyring_handler.c

ad723674d67584 Nayna Jain 2019-11-10  57  
ad723674d67584 Nayna Jain 2019-11-10  58  /*
ad723674d67584 Nayna Jain 2019-11-10  59   * Return the appropriate handler for particular signature list types found in
ad723674d67584 Nayna Jain 2019-11-10  60   * the UEFI db and MokListRT tables.
ad723674d67584 Nayna Jain 2019-11-10  61   */
ad723674d67584 Nayna Jain 2019-11-10 @62  __init efi_element_handler_t get_handler_for_db(const efi_guid_t *sig_type)
ad723674d67584 Nayna Jain 2019-11-10  63  {
ad723674d67584 Nayna Jain 2019-11-10  64  	if (efi_guidcmp(*sig_type, efi_cert_x509_guid) == 0)
ad723674d67584 Nayna Jain 2019-11-10  65  		return add_to_platform_keyring;
ad723674d67584 Nayna Jain 2019-11-10  66  	return 0;
ad723674d67584 Nayna Jain 2019-11-10  67  }
ad723674d67584 Nayna Jain 2019-11-10  68  
ad723674d67584 Nayna Jain 2019-11-10  69  /*
ad723674d67584 Nayna Jain 2019-11-10  70   * Return the appropriate handler for particular signature list types found in
ad723674d67584 Nayna Jain 2019-11-10  71   * the UEFI dbx and MokListXRT tables.
ad723674d67584 Nayna Jain 2019-11-10  72   */
ad723674d67584 Nayna Jain 2019-11-10 @73  __init efi_element_handler_t get_handler_for_dbx(const efi_guid_t *sig_type)

:::::: The code at line 62 was first introduced by commit
:::::: ad723674d6758478829ee766e3f1a2a24d56236f x86/efi: move common keyring handler functions to new file

:::::: TO: Nayna Jain <nayna@linux.ibm.com>
:::::: CC: Michael Ellerman <mpe@ellerman.id.au>

---
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: 41811 bytes --]

             reply	other threads:[~2021-03-05  5:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05  5:05 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-03 19:34 security/integrity/platform_certs/keyring_handler.c:62:30: warning: no previous prototype for function 'get_handler_for_db' kernel test robot
2020-10-24  6:13 kernel test robot

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=202103051308.wEuZoSCn-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ardb@kernel.org \
    --cc=atish.patra@wdc.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=palmerdabbelt@google.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;
as well as URLs for NNTP newsgroup(s).