From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: arch/x86/kvm/svm/svm.c:5344:2: error: cannot jump from switch statement to this case label
Date: Thu, 10 Sep 2026 06:53:06 +0800 [thread overview]
Message-ID: <202609100607.80b6BJUr-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "bisect to a FBC not belonging to original linux-review patches: branch: linux-review/J-rg-R-del/KVM-SEV-Document-SNP-direct-VMSA-userspace-ABI/20260908-123331, commit: fc1fa4f39837b012424bc998a2cb81055328c0c1"
::::::
BCC: lkp@intel.com
CC: llvm@lists.linux.dev
CC: oe-kbuild-all@lists.linux.dev
TO: Joerg Roedel <joerg.roedel@amd.com>
CC: 0day robot <lkp@intel.com>
tree: https://github.com/intel-lab-lkp/linux/commits/J-rg-R-del/KVM-SEV-Document-SNP-direct-VMSA-userspace-ABI/20260908-123331
head: 416bd4f57e5fc0762ea36db7d45a35e040edab4c
commit: fc1fa4f39837b012424bc998a2cb81055328c0c1 KVM: SEV: Add direct VMSA capability
date: 32 hours ago
:::::: branch date: 32 hours ago
:::::: commit date: 32 hours ago
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260910/202609100607.80b6BJUr-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260910/202609100607.80b6BJUr-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202609100607.80b6BJUr-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/kvm/svm/svm.c:5344:2: error: cannot jump from switch statement to this case label
5344 | default:
| ^
arch/x86/kvm/svm/svm.c:5337:3: note: jump bypasses initialization of variable with __attribute__((cleanup))
5337 | guard(mutex)(&kvm->lock);
| ^
include/linux/cleanup.h:423:2: note: expanded from macro 'guard'
423 | CLASS(_name, __UNIQUE_ID(guard))
| ^
include/linux/cleanup.h:303:3: note: expanded from macro 'CLASS'
303 | class_##_name##_constructor
| ^
<scratch space>:38:1: note: expanded from here
38 | class_mutex_constructor
| ^
note: (skipping 3 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
include/linux/compiler_types.h:16:23: note: expanded from macro '__PASTE'
16 | #define __PASTE(a, b) ___PASTE(a, b)
| ^
include/linux/compiler_types.h:15:24: note: expanded from macro '___PASTE'
15 | #define ___PASTE(a, b) a##b
| ^
<scratch space>:44:1: note: expanded from here
44 | __UNIQUE_ID_unlock_1237
| ^
arch/x86/kvm/svm/svm.c:5337:3: note: jump bypasses initialization of variable with __attribute__((cleanup))
include/linux/cleanup.h:423:15: note: expanded from macro 'guard'
423 | CLASS(_name, __UNIQUE_ID(guard))
| ^
include/linux/compiler.h:165:2: note: expanded from macro '__UNIQUE_ID'
165 | __PASTE(__UNIQUE_ID_, \
| ^
include/linux/compiler_types.h:16:23: note: expanded from macro '__PASTE'
16 | #define __PASTE(a, b) ___PASTE(a, b)
| ^
include/linux/compiler_types.h:15:24: note: expanded from macro '___PASTE'
15 | #define ___PASTE(a, b) a##b
| ^
<scratch space>:32:1: note: expanded from here
32 | __UNIQUE_ID_guard_1236
| ^
1 error generated.
vim +5344 arch/x86/kvm/svm/svm.c
75253db41a467a Brijesh Singh 2024-01-25 5327
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5328 static int svm_enable_vm_cap(struct kvm *kvm, struct kvm_enable_cap *cap)
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5329 {
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5330 switch (cap->cap) {
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5331 #ifdef CONFIG_KVM_AMD_SEV
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5332 case KVM_CAP_SNP_DIRECT_VMSA:
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5333 if (memchr_inv(cap->args, 0, sizeof(cap->args)) ||
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5334 kvm->arch.vm_type != KVM_X86_SNP_VM)
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5335 return -EINVAL;
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5336
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5337 guard(mutex)(&kvm->lock);
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5338 if (kvm->created_vcpus)
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5339 return -EINVAL;
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5340
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5341 to_kvm_sev_info(kvm)->snp_direct_vmsa = true;
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5342 return 0;
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5343 #endif
fc1fa4f39837b0 Joerg Roedel 2026-09-08 @5344 default:
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5345 return -EINVAL;
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5346 }
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5347 }
fc1fa4f39837b0 Joerg Roedel 2026-09-08 5348
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-09 22:53 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=202609100607.80b6BJUr-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.