[moderation/CI] Re: scsi/block: NUMA-local scan allocations, shared-tag path cleanup, and SCSI I/O counters

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/[email protected]
* [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: [email protected]

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at [email protected].

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:
[[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid