From: syzbot ci <syzbot+ci077b8815f0ecdff2@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: PCI: liveupdate: PCI core support for Live Update
Date: Tue, 12 May 2026 18:28:14 -0700 [thread overview]
Message-ID: <6a03d3ae.050a0220.e7082.0002.GAE@google.com> (raw)
syzbot ci has tested the following series
[v5] PCI: liveupdate: PCI core support for Live Update
https://lore.kernel.org/all/20260512184846.119396-1-dmatlack@google.com
* [PATCH v5 01/11] PCI: liveupdate: Set up FLB handler for the PCI core
* [PATCH v5 02/11] PCI: liveupdate: Track outgoing preserved PCI devices
* [PATCH v5 03/11] PCI: liveupdate: Track incoming preserved PCI devices
* [PATCH v5 04/11] PCI: liveupdate: Document driver binding responsibilities
* [PATCH v5 05/11] PCI: liveupdate: Keep bus numbers constant during Live Update
* [PATCH v5 06/11] PCI: liveupdate: Auto-preserve upstream bridges across Live Update
* [PATCH v5 07/11] PCI: liveupdate: Inherit ACS flags in incoming preserved devices
* [PATCH v5 08/11] PCI: liveupdate: Inherit ARI Forwarding Enable on preserved bridges
* [PATCH v5 09/11] PCI: liveupdate: Freeze preservation status during shutdown
* [PATCH v5 10/11] PCI: liveupdate: Do not disable bus mastering on preserved devices during kexec
* [PATCH v5 11/11] Documentation: PCI: Add documentation for Live Update
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/2bd36b56-6749-4b60-8011-0dc81da9bbbe
***
kernel build error
tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: 34e8f02817e31826e76bb2ded48bf28fe921f20b
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/0fc4ac39-5a07-470f-8057-4c357e165522/config
drivers/pci/liveupdate.h:38: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.
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:
[ajayachandra@nvidia.com alex@shazbot.org bhelgaas@google.com chrisl@kernel.org corbet@lwn.net dmatlack@google.com graf@amazon.com jacob.pan@linux.microsoft.com jgg@nvidia.com jrhilke@google.com kexec@lists.infradead.org leonro@nvidia.com linux-doc@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org linux-pci@vger.kernel.org lukas@wunner.de parav@nvidia.com pasha.tatashin@soleen.com praan@google.com pratyush@kernel.org rientjes@google.com rppt@kernel.org saeedm@nvidia.com skhan@linuxfoundation.org skhawaja@google.com vipinsh@google.com witu@nvidia.com yi.l.liu@intel.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-05-13 1:28 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=6a03d3ae.050a0220.e7082.0002.GAE@google.com \
--to=syzbot+ci077b8815f0ecdff2@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