From: syzbot ci <syzbot+ci9cc0b10ebae46e88@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: vfio/pci: Support ZONE_DEVICE-backed P2P Registration
Date: Wed, 10 Jun 2026 23:58:21 -0700 [thread overview]
Message-ID: <6a2a5c8d.3b0a2d4e.8c8d1.0009.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] vfio/pci: Support ZONE_DEVICE-backed P2P Registration
https://lore.kernel.org/all/20260610151853.3608948-1-praan@google.com
* [RFC PATCH 1/5] vfio: Add UAPI for ZONE_DEVICE-backed P2P registration
* [RFC PATCH 2/5] vfio/pci: Implement ZONE_DEVICE-backed P2P registration
* [RFC PATCH 3/5] vfio/pci: Block mmap & dmabuf export for ZONE_DEVICE-registered BARs
* [RFC PATCH 4/5] vfio/pci: Block ZONE_DEVICE registration for BARs with active DMABUFs
* [RFC PATCH 5/5] PCI/P2PDMA: Introduce a helper to release P2P resources
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/1de9f593-0233-404a-961d-39efb4662ff8
***
kernel build error
tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: abe651837cb394f76d738a7a747322fca3bf17ba
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/78f945da-79a3-47fe-802a-04960bafe8b6/config
drivers/vfio/pci/vfio_pci_core.c:1709:3: error: call to undeclared function 'pci_p2pdma_remove_resource'; 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 ankita@nvidia.com bhelgaas@google.com jgg@ziepe.ca kevin.tian@intel.com kvm@vger.kernel.org leon@kernel.org linux-kernel@vger.kernel.org linux-pci@vger.kernel.org logang@deltatee.com mattev@meta.com praan@google.com shivajikant@google.com skhawaja@google.com vivek.kasireddy@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-06-11 6:58 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=6a2a5c8d.3b0a2d4e.8c8d1.0009.GAE@google.com \
--to=syzbot+ci9cc0b10ebae46e88@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