From: syzbot ci <syzbot+ci787d5046e238b4e5@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Error recovery for vfio-pci devices on s390x
Date: Mon, 25 Aug 2025 12:08:06 -0700 [thread overview]
Message-ID: <68acb496.a00a0220.33401d.045d.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] Error recovery for vfio-pci devices on s390x
https://lore.kernel.org/all/20250825171226.1602-1-alifm@linux.ibm.com
* [PATCH v2 1/9] PCI: Avoid restoring error values in config space
* [PATCH v2 2/9] PCI: Add additional checks for flr and pm reset
* [PATCH v2 3/9] PCI: Allow per function PCI slots for hypervisor isolated functions
* [PATCH v2 4/9] s390/pci: Restore airq unconditionally for the zPCI device
* [PATCH v2 5/9] s390/pci: Update the logic for detecting passthrough device
* [PATCH v2 6/9] s390/pci: Store PCI error information for passthrough devices
* [PATCH v2 7/9] vfio-pci/zdev: Add a device feature for error information
* [PATCH v2 8/9] vfio: Add a reset_done callback for vfio-pci driver
* [PATCH v2 9/9] vfio: Remove the pcie check for VFIO_PCI_ERR_IRQ_INDEX
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/8d8daca2-df04-4084-80a1-8dea50b26078
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 068a56e56fa81e42fc5f08dff34fab149bb60a09
arch: amd64
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
config: https://ci.syzbot.org/builds/eadaff37-3f5e-4ae0-972f-5bbff4ce9baf/config
drivers/vfio/pci/vfio_pci_priv.h:108:1: error: expected identifier or '('
***
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:
[alex.williamson@redhat.com alifm@linux.ibm.com helgaas@kernel.org kvm@vger.kernel.org linux-kernel@vger.kernel.org linux-s390@vger.kernel.org mjrosato@linux.ibm.com schnelle@linux.ibm.com]
If the report looks fine to you, reply with:
#syz upstream
next reply other threads:[~2025-08-25 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 19:08 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-11 19:15 [moderation/CI] Re: Error recovery for vfio-pci devices on s390x syzbot ci
2025-08-14 23:22 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=68acb496.a00a0220.33401d.045d.GAE@google.com \
--to=syzbot+ci787d5046e238b4e5@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.