[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202509052153.luapQMZm-lkp@intel.com>
Date: Fri, 5 Sep 2025 22:01:45 +0800
From: kernel test robot <lkp@...el.com>
To: alistair23@...il.com, chuck.lever@...cle.com, hare@...nel.org,
kernel-tls-handshake@...ts.linux.dev, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-nfs@...r.kernel.org
Cc: oe-kbuild-all@...ts.linux.dev, kbusch@...nel.org, axboe@...nel.dk,
hch@....de, sagi@...mberg.me, kch@...dia.com, alistair23@...il.com,
Alistair Francis <alistair.francis@....com>
Subject: Re: [PATCH v2 7/7] nvmet-tcp: Support KeyUpdate
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on trondmy-nfs/linux-next]
[also build test WARNING on net/main net-next/main linus/master v6.17-rc4 next-20250905]
[cannot apply to linux-nvme/for-next horms-ipvs/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/alistair23-gmail-com/net-handshake-Store-the-key-serial-number-on-completion/20250905-105201
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
patch link: https://lore.kernel.org/r/20250905024659.811386-8-alistair.francis%40wdc.com
patch subject: [PATCH v2 7/7] nvmet-tcp: Support KeyUpdate
config: s390-randconfig-001-20250905 (https://download.01.org/0day-ci/archive/20250905/202509052153.luapQMZm-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250905/202509052153.luapQMZm-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202509052153.luapQMZm-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/nvme/target/tcp.c: In function 'nvmet_tcp_tls_record_ok':
>> drivers/nvme/target/tcp.c:1173:12: warning: unused variable 'htype' [-Wunused-variable]
1173 | u8 ctype, htype, level, description;
| ^~~~~
drivers/nvme/target/tcp.c: In function 'nvmet_tcp_io_work':
drivers/nvme/target/tcp.c:1479:5: error: implicit declaration of function 'update_tls_keys'; did you mean 'update_cr_regs'? [-Werror=implicit-function-declaration]
1479 | update_tls_keys(queue);
| ^~~~~~~~~~~~~~~
| update_cr_regs
cc1: some warnings being treated as errors
vim +/htype +1173 drivers/nvme/target/tcp.c
1168
1169 static int nvmet_tcp_tls_record_ok(struct nvmet_tcp_queue *queue,
1170 struct msghdr *msg, char *cbuf)
1171 {
1172 struct cmsghdr *cmsg = (struct cmsghdr *)cbuf;
> 1173 u8 ctype, htype, level, description;
1174 int ret = 0;
1175
1176 ctype = tls_get_record_type(queue->sock->sk, cmsg);
1177 switch (ctype) {
1178 case 0:
1179 break;
1180 case TLS_RECORD_TYPE_DATA:
1181 break;
1182 case TLS_RECORD_TYPE_ALERT:
1183 tls_alert_recv(queue->sock->sk, msg, &level, &description);
1184 if (level == TLS_ALERT_LEVEL_FATAL) {
1185 pr_err("queue %d: TLS Alert desc %u\n",
1186 queue->idx, description);
1187 ret = -ENOTCONN;
1188 } else {
1189 pr_warn("queue %d: TLS Alert desc %u\n",
1190 queue->idx, description);
1191 ret = -EAGAIN;
1192 }
1193 break;
1194 case TLS_RECORD_TYPE_HANDSHAKE:
1195 ret = -EAGAIN;
1196 break;
1197 default:
1198 /* discard this record type */
1199 pr_err("queue %d: TLS record %d unhandled\n",
1200 queue->idx, ctype);
1201 ret = -EAGAIN;
1202 break;
1203 }
1204 return ret;
1205 }
1206
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Powered by blists - more mailing lists