public inbox for syzbot@lists.linux.dev
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci540f1d67b8cb4cf8@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: PCI/TSM: coco/sev-guest: Implement SEV-TIO PCIe TDISP (phase2)
Date: Wed, 25 Feb 2026 02:21:00 -0800	[thread overview]
Message-ID: <699ecd0c.a00a0220.21906d.0006.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] PCI/TSM: coco/sev-guest: Implement SEV-TIO PCIe TDISP (phase2)
https://lore.kernel.org/all/20260225053806.3311234-1-aik@amd.com
* [PATCH kernel 1/9] pci/tsm: Add TDISP report blob and helpers to parse it
* [PATCH kernel 2/9] pci/tsm: Add tsm_tdi_status
* [PATCH kernel 3/9] coco/sev-guest: Allow multiple source files in the driver
* [PATCH kernel 4/9] dma/swiotlb: Stop forcing SWIOTLB for TDISP devices
* [PATCH kernel 5/9] x86/mm: Stop forcing decrypted page state for TDISP devices
* [PATCH kernel 6/9] x86/dma-direct: Stop changing encrypted page state for TDISP devices
* [PATCH kernel 7/9] coco/sev-guest: Implement the guest support for SEV TIO (phase2)
* [PATCH kernel 8/9] RFC: PCI: Avoid needless touching of Command register
* [PATCH kernel 9/9] pci: Allow encrypted MMIO mapping via sysfs

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/104c65e3-d8a7-4aa7-b1cb-ecc9f89b9842

***

kernel build error

tree:      kvm-next
URL:       https://kernel.googlesource.com/pub/scm/virt/kvm/kvm/
base:      e89f0e9a0a007e8c3afb8ecd739c0b3255422b00
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/4d4a2f11-2662-4b42-8ccb-c1711fdb51c5/config

./include/linux/swiotlb.h:182:6: error: call to undeclared function 'device_cc_accepted'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
./arch/x86/include/asm/dma-direct.h:20:6: error: call to undeclared function 'device_cc_accepted'; 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.

The email will later be sent to:
[aik@amd.com ak@linux.intel.com akpm@linux-foundation.org alex@shazbot.org aneesh.kumar@kernel.org ardb@kernel.org arnd@arndb.de ashish.kalra@amd.com augustus92@kaist.ac.kr bhelgaas@google.com bp@alien8.de catalin.marinas@arm.com dan.j.williams@intel.com dave.hansen@linux.intel.com dwmw@amazon.co.uk efremov@linux.com geliang@kernel.org gregkh@linuxfoundation.org herbert@gondor.apana.org.au hpa@zytor.com huibo.wang@amd.com iommu@lists.linux.dev jacob.jun.pan@linux.intel.com jbarnes@virtuousgeek.org joerg.roedel@amd.com jonathan.cameron@huawei.com kevin.brodsky@arm.com kim.phillips@amd.com konrad.wilk@oracle.com kvm@vger.kernel.org linux-coco@lists.linux.dev linux-kernel@vger.kernel.org linux-pci@vger.kernel.org luto@kernel.org m.szyprowski@samsung.com michael.roth@amd.com mingo@redhat.com mpe@ellerman.id.au mst@redhat.com neeraj.upadhyay@amd.com nikunj@amd.com pbonzini@redhat.com peterz@infradead.org piotrgregor@rsyncme.org robin.murphy@arm.com rppt@kernel.org sathyanarayanan.kuppuswamy@linux.intel.com seanjc@google.com sgarzare@redhat.com sstabellini@kernel.org]

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-02-25 10:21 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=699ecd0c.a00a0220.21906d.0006.GAE@google.com \
    --to=syzbot+ci540f1d67b8cb4cf8@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