All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v4 3/9] nvme-auth: switch to use 'struct key'
Date: Sat, 21 Nov 2026 04:11:21 +0800	[thread overview]
Message-ID: <202611210433.kaUKHSYE-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "same reports for this branch"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20261120-dhchap-keyring-v4-v4-3-5f8c7d9926ee@kernel.org>
References: <20261120-dhchap-keyring-v4-v4-3-5f8c7d9926ee@kernel.org>
TO: Hannes Reinecke <hare@kernel.org>
TO: Keith Busch <kbusch@kernel.org>
TO: Jens Axboe <axboe@kernel.dk>
TO: Christoph Hellwig <hch@lst.de>
TO: Sagi Grimberg <sagi@grimberg.me>
TO: Hannes Reinecke <hare@suse.de>
TO: Chaitanya Kulkarni <kch@nvidia.com>
CC: linux-nvme@lists.infradead.org
CC: linux-kernel@vger.kernel.org

Hi Hannes,

kernel test robot noticed the following build errors:

[auto build test ERROR on 68099cf27253a8c89d703a282d3d811446d9453b]

url:    https://github.com/intel-lab-lkp/linux/commits/Hannes-Reinecke/nvme-auth-modify-nvme_auth_transform_key-to-return-status/20261120-121400
base:   68099cf27253a8c89d703a282d3d811446d9453b
patch link:    https://lore.kernel.org/r/20261120-dhchap-keyring-v4-v4-3-5f8c7d9926ee%40kernel.org
patch subject: [PATCH v4 3/9] nvme-auth: switch to use 'struct key'
:::::: branch date: 7 hours ago
:::::: commit date: 7 hours ago
config: nios2-randconfig-1000-20261120 (https://download.01.org/0day-ci/archive/20261121/202611210433.kaUKHSYE-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261121/202611210433.kaUKHSYE-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/r/202611210433.kaUKHSYE-lkp@intel.com/

All error/warnings (new ones prefixed by >>):

   In file included from drivers/nvme/host/fabrics.c:15:
>> include/linux/nvme-keyring.h:54:1: error: expected identifier or '(' before '{' token
      54 | {
         | ^
>> include/linux/nvme-keyring.h:57:4: warning: no previous prototype for 'nvme_dhchap_psk_hash' [-Wmissing-prototypes]
      57 | u8 nvme_dhchap_psk_hash(struct key *key)
         |    ^~~~~~~~~~~~~~~~~~~~
>> include/linux/nvme-keyring.h:52:27: warning: 'nvme_dhchap_psk_lookup' declared 'static' but never defined [-Wunused-function]
      52 | static inline struct key *nvme_dhchap_psk_lookup(struct key *keyring,
         |                           ^~~~~~~~~~~~~~~~~~~~~~


vim +54 include/linux/nvme-keyring.h

50d8f97114b492 Hannes Reinecke 2026-11-20  26  
9d77eb52778499 Hannes Reinecke 2023-08-24  27  #else
62eb89323cb08f Hannes Reinecke 2025-02-24  28  static inline struct key *nvme_tls_psk_refresh(struct key *keyring,
62eb89323cb08f Hannes Reinecke 2025-02-24  29  		u8 *data, size_t data_len, const char *digest)
62eb89323cb08f Hannes Reinecke 2025-02-24  30  {
50d8f97114b492 Hannes Reinecke 2026-11-20  31  	return ERR_PTR(-EOPNOTSUPP);
62eb89323cb08f Hannes Reinecke 2025-02-24  32  }
501cc6f4aca8dc Hannes Reinecke 2023-08-24  33  static inline key_serial_t nvme_tls_psk_default(struct key *keyring,
501cc6f4aca8dc Hannes Reinecke 2023-08-24  34  		const char *hostnqn, const char *subnqn)
501cc6f4aca8dc Hannes Reinecke 2023-08-24  35  {
501cc6f4aca8dc Hannes Reinecke 2023-08-24  36  	return 0;
501cc6f4aca8dc Hannes Reinecke 2023-08-24  37  }
9d77eb52778499 Hannes Reinecke 2023-08-24  38  static inline key_serial_t nvme_keyring_id(void)
9d77eb52778499 Hannes Reinecke 2023-08-24  39  {
9d77eb52778499 Hannes Reinecke 2023-08-24  40  	return 0;
9d77eb52778499 Hannes Reinecke 2023-08-24  41  }
5bc46b49c828a6 Hannes Reinecke 2024-07-22  42  static inline struct key *nvme_tls_key_lookup(key_serial_t key_id)
5bc46b49c828a6 Hannes Reinecke 2024-07-22  43  {
50d8f97114b492 Hannes Reinecke 2026-11-20  44  	return ERR_PTR(-EOPNOTSUPP);
50d8f97114b492 Hannes Reinecke 2026-11-20  45  }
50d8f97114b492 Hannes Reinecke 2026-11-20  46  static inline struct key *nvme_dhchap_psk_refresh(struct key *keyring,
50d8f97114b492 Hannes Reinecke 2026-11-20  47  		const char *hostnqn, const char *subnqn,
50d8f97114b492 Hannes Reinecke 2026-11-20  48  		u8 *data, size_t data_len)
50d8f97114b492 Hannes Reinecke 2026-11-20  49  {
50d8f97114b492 Hannes Reinecke 2026-11-20  50  	return ERR_PTR(-EOPNOTSUPP);
50d8f97114b492 Hannes Reinecke 2026-11-20  51  }
50d8f97114b492 Hannes Reinecke 2026-11-20 @52  static inline struct key *nvme_dhchap_psk_lookup(struct key *keyring,
50d8f97114b492 Hannes Reinecke 2026-11-20  53  		const char *hostnqn, const char *subnqn, u8 hmac);
50d8f97114b492 Hannes Reinecke 2026-11-20 @54  {
50d8f97114b492 Hannes Reinecke 2026-11-20  55  	return ERR_PTR(-EOPNOTSUPP);
50d8f97114b492 Hannes Reinecke 2026-11-20  56  }
50d8f97114b492 Hannes Reinecke 2026-11-20 @57  u8 nvme_dhchap_psk_hash(struct key *key)

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

             reply	other threads:[~2026-11-20 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 20:11 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-11-20 11:13 [PATCH v4 0/9] nvme-auth: switch to use the kernel keyring Hannes Reinecke
2026-11-20 11:14 ` [PATCH v4 3/9] nvme-auth: switch to use 'struct key' Hannes Reinecke
2026-11-20 11:31   ` sashiko-bot
2026-11-20 13:08     ` Hannes Reinecke
2026-11-20 19:24   ` kernel test robot
2026-11-20 19:37   ` 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=202611210433.kaUKHSYE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.