linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Keith Busch <kbusch@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-nvme@lists.infradead.org,
	Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>
Subject: [linux-nvme:nvme-6.19 21/21] drivers/nvme/common/auth.c:158:13: error: redefinition of 'nvme_auth_extract_key'
Date: Sat, 1 Nov 2025 23:08:21 +0800	[thread overview]
Message-ID: <202511012300.eAcEQQP5-lkp@intel.com> (raw)

tree:   git://git.infradead.org/nvme.git nvme-6.19
head:   453ba3089d4570c2be2e230e1e7a287eac4b306b
commit: 453ba3089d4570c2be2e230e1e7a287eac4b306b [21/21] nvme: fixup nvme auth host/target dependency
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20251101/202511012300.eAcEQQP5-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251101/202511012300.eAcEQQP5-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202511012300.eAcEQQP5-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/nvme/common/auth.c:158:13: error: redefinition of 'nvme_auth_extract_key'
     158 | struct key *nvme_auth_extract_key(struct key *keyring, const u8 *secret,
         |             ^
   include/linux/nvme-auth.h:25:27: note: previous definition is here
      25 | static inline struct key *nvme_auth_extract_key(struct key *keyring,
         |                           ^
   1 error generated.


vim +/nvme_auth_extract_key +158 drivers/nvme/common/auth.c

f50fff73d620cd6 Hannes Reinecke 2022-06-27  157  
e30cd923b3ed107 Hannes Reinecke 2025-05-28 @158  struct key *nvme_auth_extract_key(struct key *keyring, const u8 *secret,
592f87de2971040 Hannes Reinecke 2025-05-28  159  				  size_t secret_len, bool *generated)
3ebed3749f17679 Mark O'Donovan  2023-10-17  160  {
e30cd923b3ed107 Hannes Reinecke 2025-05-28  161  	struct key *key;
3ebed3749f17679 Mark O'Donovan  2023-10-17  162  
592f87de2971040 Hannes Reinecke 2025-05-28  163  	key = nvme_dhchap_psk_lookup(keyring, secret);
592f87de2971040 Hannes Reinecke 2025-05-28  164  	if (!IS_ERR(key)) {
592f87de2971040 Hannes Reinecke 2025-05-28  165  		*generated = false;
592f87de2971040 Hannes Reinecke 2025-05-28  166  		return key;
592f87de2971040 Hannes Reinecke 2025-05-28  167  	}
e30cd923b3ed107 Hannes Reinecke 2025-05-28  168  	key = nvme_dhchap_psk_refresh(keyring, secret, secret_len);
592f87de2971040 Hannes Reinecke 2025-05-28  169  	if (!IS_ERR(key)) {
592f87de2971040 Hannes Reinecke 2025-05-28  170  		*generated = true;
592f87de2971040 Hannes Reinecke 2025-05-28  171  		pr_debug("generated dhchap key %s\n",
592f87de2971040 Hannes Reinecke 2025-05-28  172  			 key->description);
592f87de2971040 Hannes Reinecke 2025-05-28  173  	}
f50fff73d620cd6 Hannes Reinecke 2022-06-27  174  	return key;
f50fff73d620cd6 Hannes Reinecke 2022-06-27  175  }
f50fff73d620cd6 Hannes Reinecke 2022-06-27  176  EXPORT_SYMBOL_GPL(nvme_auth_extract_key);
f50fff73d620cd6 Hannes Reinecke 2022-06-27  177  

:::::: The code at line 158 was first introduced by commit
:::::: e30cd923b3ed10791cb23e15804b0b74af21e074 nvme-auth: switch to use 'struct key'

:::::: TO: Hannes Reinecke <hare@kernel.org>
:::::: CC: Keith Busch <kbusch@kernel.org>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2025-11-01 15:10 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=202511012300.eAcEQQP5-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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).