From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@suse.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [hare-nvme:configfs-ns 3/9] drivers/nvme/host/fabrics.h:132:2: error: unknown type name 'key_ref_t'; did you mean 'key_perm_t'?
Date: Sat, 09 May 2026 06:52:26 +0800 [thread overview]
Message-ID: <202605090634.DZTgizp2-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hare/nvme.git configfs-ns
head: 509cbb083b05db0f02a3ceea68bb093f8725a6a5
commit: 2ea876cdebd3c84d7466f8d8f58a511ef4f6c317 [3/9] nvme: use key reference for persistent keys
config: i386-buildonly-randconfig-002-20260509 (https://download.01.org/0day-ci/archive/20260509/202605090634.DZTgizp2-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/20260509/202605090634.DZTgizp2-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/202605090634.DZTgizp2-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/nvme/host/fabrics.c:14:
>> drivers/nvme/host/fabrics.h:132:2: error: unknown type name 'key_ref_t'; did you mean 'key_perm_t'?
132 | key_ref_t keyring;
| ^~~~~~~~~
| key_perm_t
include/linux/key.h:31:18: note: 'key_perm_t' declared here
31 | typedef uint32_t key_perm_t;
| ^
In file included from drivers/nvme/host/fabrics.c:14:
drivers/nvme/host/fabrics.h:133:2: error: unknown type name 'key_ref_t'; did you mean 'key_perm_t'?
133 | key_ref_t tls_key;
| ^~~~~~~~~
| key_perm_t
include/linux/key.h:31:18: note: 'key_perm_t' declared here
31 | typedef uint32_t key_perm_t;
| ^
>> drivers/nvme/host/fabrics.c:725:2: error: unknown type name 'key_ref_t'; did you mean 'key_perm_t'?
725 | key_ref_t keyref;
| ^~~~~~~~~
| key_perm_t
include/linux/key.h:31:18: note: 'key_perm_t' declared here
31 | typedef uint32_t key_perm_t;
| ^
>> drivers/nvme/host/fabrics.c:739:16: error: incompatible pointer to integer conversion assigning to 'key_perm_t' (aka 'unsigned int') from 'void *' [-Wint-conversion]
739 | opts->tls_key = NULL;
| ^ ~~~~
drivers/nvme/host/fabrics.c:740:16: error: incompatible pointer to integer conversion assigning to 'key_perm_t' (aka 'unsigned int') from 'void *' [-Wint-conversion]
740 | opts->keyring = NULL;
| ^ ~~~~
drivers/nvme/host/fabrics.c:1005:11: error: incompatible pointer to integer conversion assigning to 'key_perm_t' (aka 'unsigned int') from 'void *' [-Wint-conversion]
1005 | keyref = make_key_ref(key, true);
| ^ ~~~~~~~~~~~~~~~~~~~~~~~
drivers/nvme/host/fabrics.c:1022:11: error: incompatible pointer to integer conversion assigning to 'key_perm_t' (aka 'unsigned int') from 'void *' [-Wint-conversion]
1022 | keyref = make_key_ref(key, true);
| ^ ~~~~~~~~~~~~~~~~~~~~~~~
7 errors generated.
--
In file included from drivers/nvme/host/fc.c:14:
>> drivers/nvme/host/fabrics.h:132:2: error: unknown type name 'key_ref_t'; did you mean 'key_perm_t'?
132 | key_ref_t keyring;
| ^~~~~~~~~
| key_perm_t
include/linux/key.h:31:18: note: 'key_perm_t' declared here
31 | typedef uint32_t key_perm_t;
| ^
In file included from drivers/nvme/host/fc.c:14:
drivers/nvme/host/fabrics.h:133:2: error: unknown type name 'key_ref_t'; did you mean 'key_perm_t'?
133 | key_ref_t tls_key;
| ^~~~~~~~~
| key_perm_t
include/linux/key.h:31:18: note: 'key_perm_t' declared here
31 | typedef uint32_t key_perm_t;
| ^
2 errors generated.
vim +132 drivers/nvme/host/fabrics.h
71
72 /**
73 * struct nvmf_ctrl_options - Used to hold the options specified
74 * with the parsing opts enum.
75 * @mask: Used by the fabrics library to parse through sysfs options
76 * on adding a NVMe controller.
77 * @max_reconnects: maximum number of allowed reconnect attempts before removing
78 * the controller, (-1) means reconnect forever, zero means remove
79 * immediately;
80 * @transport: Holds the fabric transport "technology name" (for a lack of
81 * better description) that will be used by an NVMe controller
82 * being added.
83 * @subsysnqn: Hold the fully qualified NQN subsystem name (format defined
84 * in the NVMe specification, "NVMe Qualified Names").
85 * @traddr: The transport-specific TRADDR field for a port on the
86 * subsystem which is adding a controller.
87 * @trsvcid: The transport-specific TRSVCID field for a port on the
88 * subsystem which is adding a controller.
89 * @host_traddr: A transport-specific field identifying the NVME host port
90 * to use for the connection to the controller.
91 * @host_iface: A transport-specific field identifying the NVME host
92 * interface to use for the connection to the controller.
93 * @queue_size: Number of IO queue elements.
94 * @nr_io_queues: Number of controller IO queues that will be established.
95 * @reconnect_delay: Time between two consecutive reconnect attempts.
96 * @discovery_nqn: indicates if the subsysnqn is the well-known discovery NQN.
97 * @kato: Keep-alive timeout.
98 * @host: Virtual NVMe host, contains the NQN and Host ID.
99 * @dhchap_secret: DH-HMAC-CHAP secret
100 * @dhchap_ctrl_secret: DH-HMAC-CHAP controller secret for bi-directional
101 * authentication
102 * @keyring: Keyring to use for key lookups
103 * @tls_key: TLS key for encrypted connections (TCP)
104 * @tls: Start TLS encrypted connections (TCP)
105 * @concat: Enabled Secure channel concatenation (TCP)
106 * @disable_sqflow: disable controller sq flow control
107 * @hdr_digest: generate/verify header digest (TCP)
108 * @data_digest: generate/verify data digest (TCP)
109 * @nr_write_queues: number of queues for write I/O
110 * @nr_poll_queues: number of queues for polling I/O
111 * @tos: type of service
112 * @fast_io_fail_tmo: Fast I/O fail timeout in seconds
113 */
114 struct nvmf_ctrl_options {
115 unsigned mask;
116 int max_reconnects;
117 char *transport;
118 char *subsysnqn;
119 char *traddr;
120 char *trsvcid;
121 char *host_traddr;
122 char *host_iface;
123 size_t queue_size;
124 unsigned int nr_io_queues;
125 unsigned int reconnect_delay;
126 bool discovery_nqn;
127 bool duplicate_connect;
128 unsigned int kato;
129 struct nvmf_host *host;
130 char *dhchap_secret;
131 char *dhchap_ctrl_secret;
> 132 key_ref_t keyring;
133 key_ref_t tls_key;
134 bool tls;
135 bool concat;
136 bool disable_sqflow;
137 bool hdr_digest;
138 bool data_digest;
139 unsigned int nr_write_queues;
140 unsigned int nr_poll_queues;
141 int tos;
142 int fast_io_fail_tmo;
143 };
144
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-08 22:52 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=202605090634.DZTgizp2-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@suse.de \
--cc=llvm@lists.linux.dev \
--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