All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+cid87965fa0bcd0f6e@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: scsi/block: NUMA-local scan allocations, shared-tag path cleanup, and SCSI I/O counters
Date: Tue, 09 Jun 2026 15:00:57 -0700	[thread overview]
Message-ID: <6a288d19.39669fcc.33b062.00a6.GAE@google.com> (raw)

syzbot ci has tested the following series

[v3] scsi/block: NUMA-local scan allocations, shared-tag path cleanup, and SCSI I/O counters
https://lore.kernel.org/all/20260609121806.2121755-1-sumit.saxena@broadcom.com
* [PATCH v3 1/4] scsi: scan: allocate sdev and starget on the NUMA node of the host adapter
* [PATCH v3 2/4] scsi: host: allocate struct Scsi_Host on the NUMA node of the host adapter
* [PATCH v3 3/4] block: drop shared-tag fairness throttling
* [PATCH v3 4/4] scsi: use percpu counters for iostat counters in struct scsi_device

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/360774d1-fc19-4efa-ad7f-1b57f3911dc1

***

kernel build error

tree:      linux-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base:      a87737435cfa134f9cdcc696ba3080759d04cf72
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/3435ab05-0af5-4da8-9aea-dcf5f7401be7/config

drivers/ata/libata-scsi.c:4637:57: error: too few arguments to function call, expected 3, have 2

***

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.

To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[aacraid@microsemi.com aliakc@web.de anil.gurumurthy@qlogic.com aradford@gmail.com axboe@kernel.dk bcm-kernel-feedback-list@broadcom.com brking@us.ibm.com bvanassche@acm.org chandrakanth.patil@broadcom.com chleroy@kernel.org cleech@redhat.com daniel@thingy.jp decui@microsoft.com don.brace@microchip.com eperezma@redhat.com fischer@norbit.de fthain@linux-m68k.org geoff@infradead.org gotom@debian.or.jp gr-qlogic-storage-upstream@marvell.com haiyangz@microsoft.com hare@suse.com james.bottomley@hansenpartnership.com james.rizzo@broadcom.com jasowang@redhat.com jgross@suse.com jinpu.wang@cloud.ionos.com john.g.garry@oracle.com justin.tee@broadcom.com kartilak@cisco.com kashyap.desai@broadcom.com khalid@gonehiking.org kys@microsoft.com lduncan@suse.com lenehan@twibble.org linux-arm-kernel@lists.infradead.org linux-block@vger.kernel.org linux-hyperv@vger.kernel.org linux-scsi@vger.kernel.org linux@armlinux.org.uk linux@highpoint-tech.com linuxdrivers@attotech.com linuxppc-dev@lists.ozlabs.org liyihang9@h-partners.com longli@microsoft.com maddy@linux.ibm.com martin.petersen@oracle.com mdr@sgi.com megaraidlinux.pdl@broadcom.com michael.christie@oracle.com mpe@ellerman.id.au mpi3mr-linuxdrv.pdl@broadcom.com]

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-06-09 22:00 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=6a288d19.39669fcc.33b062.00a6.GAE@google.com \
    --to=syzbot+cid87965fa0bcd0f6e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.