From: syzbot ci <syzbot+ci36a206614ae21ca5@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: vfio/pci: Add PCIe TPH support
Date: Thu, 04 Jun 2026 07:47:33 -0700 [thread overview]
Message-ID: <6a219005.e4db5ad2.5fee4.0060.GAE@google.com> (raw)
syzbot ci has tested the following series
[v16] vfio/pci: Add PCIe TPH support
https://lore.kernel.org/all/20260604132804.28678-1-fengchengwen@huawei.com
* [PATCH v16 01/12] PCI/TPH: Fix pcie_tph_get_st_table_loc() field extraction
* [PATCH v16 02/12] PCI/TPH: Fix tph_enabled concurrent update race by bitfield packing
* [PATCH v16 03/12] PCI/TPH: Cache TPH requester capability at probe time
* [PATCH v16 04/12] PCI/TPH: Refactor pcie_enable_tph & add explicit requester variant
* [PATCH v16 05/12] PCI/TPH: Refactor pcie_tph_get_cpu_st & add explicit variant
* [PATCH v16 06/12] PCI/TPH: expose the enabled TPH requester type
* [PATCH v16 07/12] PCI/TPH: Add pcie_tph_supported() helper to check TPH capability attributes
* [PATCH v16 08/12] vfio/pci: Hide TPH capability when TPH is unsupported
* [PATCH v16 09/12] vfio/pci: Add TPH_ENABLE feature skeleton and unsafe module parameter
* [PATCH v16 10/12] vfio/pci: Add TPH_CPU_ST to query CPU's TPH steering tag
* [PATCH v16 11/12] vfio/pci: Add TPH_ST_CONFIG for PCIe TPH ST configuration
* [PATCH v16 12/12] vfio/pci: Virtualize PCIe TPH capability registers
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/9b7b69b8-bfdc-4bd3-b1b3-f39969de466d
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: ba3e43a9e601636f5edb54e259a74f96ca3b8fd8
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/ebe0427d-6ae9-43ad-8794-5f7369454756/config
drivers/vfio/pci/vfio_pci_config.c:1166:9: error: call to undeclared function 'FIELD_GET'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
***
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:
[alex@shazbot.org fengchengwen@huawei.com helgaas@kernel.org jgg@ziepe.ca kvm@vger.kernel.org linux-pci@vger.kernel.org liuyonglong@huawei.com wangyushan12@huawei.com wangzhou1@hisilicon.com wathsala.vithanage@arm.com wei.huang2@amd.com zhipingz@meta.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
next reply other threads:[~2026-06-04 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 14:47 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-16 11:53 [moderation/CI] Re: vfio/pci: Add PCIe TPH support syzbot ci
2026-05-26 5:05 syzbot ci
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=6a219005.e4db5ad2.5fee4.0060.GAE@google.com \
--to=syzbot+ci36a206614ae21ca5@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