From: kernel test robot <lkp@intel.com>
To: Yang Xiuwei <yangxiuwei@kylinos.cn>,
fujita.tomonori@lab.ntt.co.jp, axboe@kernel.dk,
James.Bottomley@hansenpartnership.com,
martin.petersen@oracle.com
Cc: oe-kbuild-all@lists.linux.dev, bvanassche@acm.org,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
Yang Xiuwei <yangxiuwei@kylinos.cn>
Subject: Re: [PATCH v5 3/3] scsi: bsg: add io_uring passthrough handler
Date: Wed, 4 Mar 2026 14:50:07 +0100 [thread overview]
Message-ID: <202603041450.tuj48h9Q-lkp@intel.com> (raw)
In-Reply-To: <20260304080313.675768-4-yangxiuwei@kylinos.cn>
Hi Yang,
kernel test robot noticed the following build errors:
[auto build test ERROR on axboe/for-next]
[also build test ERROR on jejb-scsi/for-next mkp-scsi/for-next linus/master v7.0-rc2 next-20260303]
[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/Yang-Xiuwei/bsg-add-bsg_uring_cmd-uapi-structure/20260304-160717
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git for-next
patch link: https://lore.kernel.org/r/20260304080313.675768-4-yangxiuwei%40kylinos.cn
patch subject: [PATCH v5 3/3] scsi: bsg: add io_uring passthrough handler
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260304/202603041450.tuj48h9Q-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260304/202603041450.tuj48h9Q-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/202603041450.tuj48h9Q-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/scsi/scsi_bsg.c: In function 'scsi_bsg_map_user_buffer':
>> drivers/scsi/scsi_bsg.c:111:71: error: macro "io_uring_sqe_cmd" requires 2 arguments, but only 1 given
111 | const struct bsg_uring_cmd *cmd = io_uring_sqe_cmd(ioucmd->sqe);
| ^
In file included from drivers/scsi/scsi_bsg.c:3:
include/linux/io_uring/cmd.h:29:9: note: macro "io_uring_sqe_cmd" defined here
29 | #define io_uring_sqe_cmd(sqe, type) ({ \
| ^~~~~~~~~~~~~~~~
>> drivers/scsi/scsi_bsg.c:111:43: error: 'io_uring_sqe_cmd' undeclared (first use in this function); did you mean 'io_uring_sqe'?
111 | const struct bsg_uring_cmd *cmd = io_uring_sqe_cmd(ioucmd->sqe);
| ^~~~~~~~~~~~~~~~
| io_uring_sqe
drivers/scsi/scsi_bsg.c:111:43: note: each undeclared identifier is reported only once for each function it appears in
drivers/scsi/scsi_bsg.c: In function 'scsi_bsg_uring_cmd':
drivers/scsi/scsi_bsg.c:137:71: error: macro "io_uring_sqe_cmd" requires 2 arguments, but only 1 given
137 | const struct bsg_uring_cmd *cmd = io_uring_sqe_cmd(ioucmd->sqe);
| ^
include/linux/io_uring/cmd.h:29:9: note: macro "io_uring_sqe_cmd" defined here
29 | #define io_uring_sqe_cmd(sqe, type) ({ \
| ^~~~~~~~~~~~~~~~
drivers/scsi/scsi_bsg.c:137:43: error: 'io_uring_sqe_cmd' undeclared (first use in this function); did you mean 'io_uring_sqe'?
137 | const struct bsg_uring_cmd *cmd = io_uring_sqe_cmd(ioucmd->sqe);
| ^~~~~~~~~~~~~~~~
| io_uring_sqe
drivers/scsi/scsi_bsg.c:203:21: error: assignment to 'enum rq_end_io_ret (*)(struct request *, blk_status_t, const struct io_comp_batch *)' {aka 'enum rq_end_io_ret (*)(struct request *, unsigned char, const struct io_comp_batch *)'} from incompatible pointer type 'enum rq_end_io_ret (*)(struct request *, blk_status_t)' {aka 'enum rq_end_io_ret (*)(struct request *, unsigned char)'} [-Wincompatible-pointer-types]
203 | req->end_io = scsi_bsg_uring_cmd_done;
| ^
vim +/io_uring_sqe_cmd +111 drivers/scsi/scsi_bsg.c
106
107 static int scsi_bsg_map_user_buffer(struct request *req,
108 struct io_uring_cmd *ioucmd,
109 unsigned int issue_flags, gfp_t gfp_mask)
110 {
> 111 const struct bsg_uring_cmd *cmd = io_uring_sqe_cmd(ioucmd->sqe);
112 struct iov_iter iter;
113 bool is_write = cmd->dout_xfer_len > 0;
114 u64 buf_addr = is_write ? cmd->dout_xferp : cmd->din_xferp;
115 unsigned long buf_len = is_write ? cmd->dout_xfer_len : cmd->din_xfer_len;
116 int ret;
117
118 if (ioucmd->flags & IORING_URING_CMD_FIXED) {
119 ret = io_uring_cmd_import_fixed(buf_addr, buf_len,
120 is_write ? WRITE : READ,
121 &iter, ioucmd, issue_flags);
122 if (ret < 0)
123 return ret;
124 ret = blk_rq_map_user_iov(req->q, req, NULL, &iter, gfp_mask);
125 } else {
126 ret = blk_rq_map_user(req->q, req, NULL, uptr64(buf_addr),
127 buf_len, gfp_mask);
128 }
129
130 return ret;
131 }
132
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-04 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 8:03 [PATCH v5 0/3] bsg: add io_uring command support for SCSI passthrough Yang Xiuwei
2026-03-04 8:03 ` [PATCH v5 1/3] bsg: add bsg_uring_cmd uapi structure Yang Xiuwei
2026-03-04 8:03 ` [PATCH v5 2/3] bsg: add io_uring command support to generic layer Yang Xiuwei
2026-03-04 8:03 ` [PATCH v5 3/3] scsi: bsg: add io_uring passthrough handler Yang Xiuwei
2026-03-04 13:50 ` kernel test robot [this message]
2026-03-05 1:28 ` [PATCH v6 0/3] bsg: add io_uring command support for SCSI passthrough Yang Xiuwei
2026-03-05 1:28 ` [PATCH v6 1/3] bsg: add bsg_uring_cmd uapi structure Yang Xiuwei
2026-03-05 15:14 ` Bart Van Assche
2026-03-06 2:54 ` Yang Xiuwei
2026-03-05 1:28 ` [PATCH v6 2/3] bsg: add io_uring command support to generic layer Yang Xiuwei
2026-03-05 15:17 ` Bart Van Assche
2026-03-06 3:03 ` Yang Xiuwei
2026-03-05 1:28 ` [PATCH v6 3/3] scsi: bsg: add io_uring passthrough handler Yang Xiuwei
2026-03-05 15:39 ` Bart Van Assche
2026-03-06 3:04 ` Yang Xiuwei
2026-03-05 15:12 ` [PATCH v6 0/3] bsg: add io_uring command support for SCSI passthrough Bart Van Assche
2026-03-06 2:46 ` Yang Xiuwei
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=202603041450.tuj48h9Q-lkp@intel.com \
--to=lkp@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=io-uring@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yangxiuwei@kylinos.cn \
/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