From: kernel test robot <lkp@intel.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: kbuild-all@lists.01.org, linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>
Subject: [linux-nvme:nvme-5.17 1/2] drivers/nvme/host/tcp.c:920:25: sparse: sparse: incorrect type in argument 2 (different base types)
Date: Wed, 9 Feb 2022 21:37:01 +0800 [thread overview]
Message-ID: <202202092122.25VLa0rQ-lkp@intel.com> (raw)
tree: git://git.infradead.org/nvme.git nvme-5.17
head: 5c66f610f0be01358a3bb037fce6ae5744e225d2
commit: 52100021775a35eef08e493acabe3deb31847cb8 [1/2] nvme-tcp: fix bogus request completion when failing to send AER
config: x86_64-randconfig-s021 (https://download.01.org/0day-ci/archive/20220209/202202092122.25VLa0rQ-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
git remote add linux-nvme git://git.infradead.org/nvme.git
git fetch --no-tags linux-nvme nvme-5.17
git checkout 52100021775a35eef08e493acabe3deb31847cb8
# save the config file to linux build tree
mkdir build_dir
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/nvme/host/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/nvme/host/tcp.c:920:25: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected restricted __le16 [usertype] status @@ got int @@
drivers/nvme/host/tcp.c:920:25: sparse: expected restricted __le16 [usertype] status
drivers/nvme/host/tcp.c:920:25: sparse: got int
vim +920 drivers/nvme/host/tcp.c
913
914 static void nvme_tcp_fail_request(struct nvme_tcp_request *req)
915 {
916 if (nvme_tcp_async_req(req)) {
917 union nvme_result res = {};
918
919 nvme_complete_async_event(&req->queue->ctrl->ctrl,
> 920 NVME_SC_HOST_PATH_ERROR, &res);
921 } else {
922 nvme_tcp_end_request(blk_mq_rq_from_pdu(req),
923 NVME_SC_HOST_PATH_ERROR);
924 }
925 }
926
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-02-09 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 13:37 kernel test robot [this message]
2022-02-09 13:51 ` [linux-nvme:nvme-5.17 1/2] drivers/nvme/host/tcp.c:920:25: sparse: sparse: incorrect type in argument 2 (different base types) Christoph Hellwig
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=202202092122.25VLa0rQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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