From: kernel test robot <lkp@intel.com>
To: Wilfred Mallawa <wilfred.opensource@gmail.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
John Fastabend <john.fastabend@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Sabrina Dubroca <sd@queasysnail.net>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Hannes Reinecke <hare@suse.de>,
Wilfred Mallawa <wilfred.mallawa@wdc.com>
Subject: Re: [PATCH] nvme/tcp: handle tls partially sent records in write_space()
Date: Fri, 10 Oct 2025 05:36:31 +0800 [thread overview]
Message-ID: <202510100505.gzOzGPbI-lkp@intel.com> (raw)
In-Reply-To: <20251007004634.38716-2-wilfred.opensource@gmail.com>
Hi Wilfred,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net/main]
[also build test WARNING on net-next/main linus/master linux-nvme/for-next v6.17 next-20251009]
[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/Wilfred-Mallawa/nvme-tcp-handle-tls-partially-sent-records-in-write_space/20251009-193029
base: net/main
patch link: https://lore.kernel.org/r/20251007004634.38716-2-wilfred.opensource%40gmail.com
patch subject: [PATCH] nvme/tcp: handle tls partially sent records in write_space()
config: s390-randconfig-002-20251010 (https://download.01.org/0day-ci/archive/20251010/202510100505.gzOzGPbI-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 39f292ffa13d7ca0d1edff27ac8fd55024bb4d19)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251010/202510100505.gzOzGPbI-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/202510100505.gzOzGPbI-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/nvme/host/tcp.c:1316:22: warning: unused variable 'ctx' [-Wunused-variable]
1316 | struct tls_context *ctx = tls_get_ctx(queue->sock->sk);
| ^~~
1 warning generated.
vim +/ctx +1316 drivers/nvme/host/tcp.c
1312
1313 static int nvme_tcp_try_send(struct nvme_tcp_queue *queue)
1314 {
1315 struct nvme_tcp_request *req;
> 1316 struct tls_context *ctx = tls_get_ctx(queue->sock->sk);
1317 unsigned int noreclaim_flag;
1318 int ret = 1;
1319
1320 if (!queue->request) {
1321 queue->request = nvme_tcp_fetch_request(queue);
1322 if (!queue->request)
1323 return 0;
1324 }
1325 req = queue->request;
1326
1327 noreclaim_flag = memalloc_noreclaim_save();
1328 if (req->state == NVME_TCP_SEND_CMD_PDU) {
1329 ret = nvme_tcp_try_send_cmd_pdu(req);
1330 if (ret <= 0)
1331 goto done;
1332 if (!nvme_tcp_has_inline_data(req))
1333 goto out;
1334 }
1335
1336 if (req->state == NVME_TCP_SEND_H2C_PDU) {
1337 ret = nvme_tcp_try_send_data_pdu(req);
1338 if (ret <= 0)
1339 goto done;
1340 }
1341
1342 if (req->state == NVME_TCP_SEND_DATA) {
1343 ret = nvme_tcp_try_send_data(req);
1344 if (ret <= 0)
1345 goto done;
1346 }
1347
1348 if (req->state == NVME_TCP_SEND_DDGST)
1349 ret = nvme_tcp_try_send_ddgst(req);
1350 done:
1351 if (ret == -EAGAIN) {
1352 ret = 0;
1353 } else if (ret < 0) {
1354 dev_err(queue->ctrl->ctrl.device,
1355 "failed to send request %d\n", ret);
1356 nvme_tcp_fail_request(queue->request);
1357 nvme_tcp_done_send_req(queue);
1358 }
1359 out:
1360 memalloc_noreclaim_restore(noreclaim_flag);
1361 return ret;
1362 }
1363
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-10-09 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 0:46 [PATCH] nvme/tcp: handle tls partially sent records in write_space() Wilfred Mallawa
2025-10-07 5:19 ` Hannes Reinecke
2025-10-07 9:24 ` Wilfred Mallawa
2025-10-07 9:51 ` Hannes Reinecke
2025-10-08 2:11 ` Wilfred Mallawa
2025-10-08 6:28 ` Hannes Reinecke
2025-10-09 21:36 ` kernel test robot [this message]
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=202510100505.gzOzGPbI-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kbusch@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=sagi@grimberg.me \
--cc=sd@queasysnail.net \
--cc=wilfred.mallawa@wdc.com \
--cc=wilfred.opensource@gmail.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).