From: syzbot ci <syzbot+cie7d10ec38718cb14@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: vfio/pci: Allow MMIO regions to be exported through dma-buf
Date: Sun, 02 Nov 2025 01:46:06 -0700 [thread overview]
Message-ID: <69071a4e.050a0220.29fc44.0019.GAE@google.com> (raw)
syzbot ci has tested the following series
[v6] vfio/pci: Allow MMIO regions to be exported through dma-buf
https://lore.kernel.org/all/20251102-dmabuf-vfio-v6-0-d773cff0db9f@nvidia.com
* [PATCH v6 01/11] PCI/P2PDMA: Separate the mmap() support from the core logic
* [PATCH v6 02/11] PCI/P2PDMA: Simplify bus address mapping API
* [PATCH v6 03/11] PCI/P2PDMA: Refactor to separate core P2P functionality from memory allocation
* [PATCH v6 04/11] PCI/P2PDMA: Provide an access to pci_p2pdma_map_type() function
* [PATCH v6 05/11] PCI/P2PDMA: Document DMABUF model
* [PATCH v6 06/11] dma-buf: provide phys_vec to scatter-gather mapping routine
* [PATCH v6 07/11] vfio: Export vfio device get and put registration helpers
* [PATCH v6 08/11] vfio/pci: Share the core device pointer while invoking feature functions
* [PATCH v6 09/11] vfio/pci: Enable peer-to-peer DMA transactions by default
* [PATCH v6 10/11] vfio/pci: Add dma-buf export support for MMIO regions
* [PATCH v6 11/11] vfio/nvgrace: Support get_dmabuf_phys
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/3957e140-61bf-47f1-a89e-45a4665d3d99
***
kernel build error
tree: kvm-next
URL: https://kernel.googlesource.com/pub/scm/virt/kvm/kvm/
base: 6b36119b94d0b2bb8cea9d512017efafd461d6ac
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/2b2d6598-2cb2-4c0a-8142-f4918eeda555/config
drivers/dma-buf/dma-buf.c:1393:10: error: use of undeclared identifier 'DMA_ATTR_MMIO'
drivers/dma-buf/dma-buf.c:1399:11: error: call to undeclared function 'dma_map_phys'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/dma-buf/dma-buf.c:1401:10: error: use of undeclared identifier 'DMA_ATTR_MMIO'
drivers/dma-buf/dma-buf.c:1441:6: error: use of undeclared identifier 'DMA_ATTR_MMIO'
drivers/dma-buf/dma-buf.c:1444:4: error: call to undeclared function 'dma_unmap_phys'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/dma-buf/dma-buf.c:1445:34: error: use of undeclared identifier 'DMA_ATTR_MMIO'
drivers/dma-buf/dma-buf.c:1476:6: error: use of undeclared identifier 'DMA_ATTR_MMIO'
drivers/dma-buf/dma-buf.c:1481:4: error: call to undeclared function 'dma_unmap_phys'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/dma-buf/dma-buf.c:1482:34: error: use of undeclared identifier 'DMA_ATTR_MMIO'
***
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:
[akpm@linux-foundation.org alex.williamson@redhat.com ankita@nvidia.com axboe@kernel.dk bhelgaas@google.com christian.koenig@amd.com corbet@lwn.net dri-devel@lists.freedesktop.org gustavoars@kernel.org iommu@lists.linux.dev jgg@nvidia.com jgg@ziepe.ca joro@8bytes.org kees@kernel.org kevin.tian@intel.com kjaju@nvidia.com kvm@vger.kernel.org leon@kernel.org linaro-mm-sig@lists.linaro.org linux-block@vger.kernel.org linux-doc@vger.kernel.org linux-hardening@vger.kernel.org linux-kernel@vger.kernel.org linux-media@vger.kernel.org linux-mm@kvack.org linux-pci@vger.kernel.org logang@deltatee.com m.szyprowski@samsung.com mochs@nvidia.com robin.murphy@arm.com skolothumtho@nvidia.com sumit.semwal@linaro.org vivek.kasireddy@intel.com will@kernel.org yishaih@nvidia.com]
If the report looks fine to you, reply with:
#syz upstream
next reply other threads:[~2025-11-02 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 8:46 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-06 15:56 [moderation/CI] Re: vfio/pci: Allow MMIO regions to be exported through dma-buf syzbot ci
2025-11-11 11:07 syzbot ci
2025-11-20 10:18 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=69071a4e.050a0220.29fc44.0019.GAE@google.com \
--to=syzbot+cie7d10ec38718cb14@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