From: syzbot ci <syzbot+cif6582a959155eabe@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: bsg: add io_uring command support for SCSI passthrough
Date: Wed, 04 Mar 2026 16:38:22 -0800 [thread overview]
Message-ID: <69a8d07e.a70a0220.135158.0013.GAE@google.com> (raw)
syzbot ci has tested the following series
[v5] bsg: add io_uring command support for SCSI passthrough
https://lore.kernel.org/all/20260304080313.675768-1-yangxiuwei@kylinos.cn
* [PATCH v5 1/3] bsg: add bsg_uring_cmd uapi structure
* [PATCH v5 2/3] bsg: add io_uring command support to generic layer
* [PATCH v5 3/3] scsi: bsg: add io_uring passthrough handler
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/d10fb67c-0756-49f2-a7fd-bfade2305b9a
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: ecc64d2dc9ff9738d2a896beb68e02c2feaf9a02
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/8abf8676-4535-40d8-b35f-6f8ab7e8bbee/config
drivers/scsi/scsi_bsg.c:111:64: error: too few arguments provided to function-like macro invocation
drivers/scsi/scsi_bsg.c:111:36: error: use of undeclared identifier 'io_uring_sqe_cmd'
drivers/scsi/scsi_bsg.c:137:64: error: too few arguments provided to function-like macro invocation
drivers/scsi/scsi_bsg.c:137:36: error: use of undeclared identifier 'io_uring_sqe_cmd'
drivers/scsi/scsi_bsg.c:203:14: error: incompatible function pointer types assigning to 'rq_end_io_fn *' (aka 'enum rq_end_io_ret (*)(struct request *, unsigned char, const struct io_comp_batch *)') from 'enum rq_end_io_ret (struct request *, blk_status_t)' (aka 'enum rq_end_io_ret (struct request *, unsigned char)') [-Wincompatible-function-pointer-types]
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
The email will later be sent to:
[axboe@kernel.dk bvanassche@acm.org fujita.tomonori@lab.ntt.co.jp io-uring@vger.kernel.org james.bottomley@hansenpartnership.com linux-block@vger.kernel.org linux-kernel@vger.kernel.org linux-scsi@vger.kernel.org martin.petersen@oracle.com yangxiuwei@kylinos.cn]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-03-05 0:38 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=69a8d07e.a70a0220.135158.0013.GAE@google.com \
--to=syzbot+cif6582a959155eabe@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.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