Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci6eb4396eec0fdf67@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: KVM: SVM: Support direct setting of VMSA for SEV-SNP guests
Date: Tue, 08 Sep 2026 06:38:49 -0700	[thread overview]
Message-ID: <6aa00fe9.f81106d8.285f0a.0002.GAE@google.com> (raw)

syzbot ci has tested the following series

[v2] KVM: SVM: Support direct setting of VMSA for SEV-SNP guests
https://lore.kernel.org/all/20260908103338.427254-1-joro@8bytes.org
* [PATCH v2 1/8] KVM: SEV: Document SNP direct VMSA userspace ABI
* [PATCH v2 2/8] KVM: SVM: Implement GET_AP_APIC_IDS NAE event
* [PATCH v2 3/8] KVM: SVM: Hold SRCU while reloading guest-owned VMSAs
* [PATCH v2 4/8] KVM: SEV: Add direct VMSA capability
* [PATCH v2 5/8] KVM: SEV: Allow VMSA pages in SNP launch updates
* [PATCH v2 6/8] KVM: SEV: Add SNP vCPU state get and set commands
* [PATCH v2 7/8] KVM: selftests: Test the SNP APIC-ID-list GHCB request
* [PATCH v2 8/8] KVM: selftests: Test SNP vCPU state and direct VMSA launch

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/cec648dd-2a50-4821-b110-268d2ecf091f

***

kernel build error

tree:      axboe
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/axboe/linux.git
base:      df2908090cda368b01ff43709f51890076c56157
arch:      amd64
compiler:  Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config:    https://ci.syzbot.org/builds/0356e5b2-bf16-445c-a2bf-b8eec005744f/config

arch/x86/kvm/svm/svm.c:5344:2: error: cannot jump from switch statement to this case label

***

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 fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.

Notes:
- The patch will be applied on top of the tested series (as an
  incremental fix).
- To test a new version of the whole series, please send it directly
  to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.

The email will later be sent to:
[coconut-svsm@lists.linux.dev james.bottomley@hansenpartnership.com joerg.roedel@amd.com joro@8bytes.org kvm@vger.kernel.org liam.merwick@oracle.com linux-doc@vger.kernel.org linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org michael.roth@amd.com ninadnaik07@gmail.com pbonzini@redhat.com seanjc@google.com thomas.lendacky@amd.com vannapurve@google.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-09-08 13:38 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=6aa00fe9.f81106d8.285f0a.0002.GAE@google.com \
    --to=syzbot+ci6eb4396eec0fdf67@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