Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: sashiko-reviews@lists.linux.dev
Cc: kvm@vger.kernel.org, Alexander Gordeev <agordeev@linux.ibm.com>,
	linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [GIT PULL 3/6] KVM: x86: Use file_to_kvm_x86() in SEV
Date: Fri, 9 Oct 2026 16:53:01 +0200	[thread overview]
Message-ID: <95c55fab-cd04-497f-9266-6c30353d73e4@linux.ibm.com> (raw)
In-Reply-To: <sashiko-outbox-165722@kernel.org>



Am 09.10.26 um 16:36 schrieb sashiko-bot@kernel.org:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] kvm: build failure due to missing definition of file_to_kvm_x86()
> --
> 
> commit 10a7cd7a1613201c02ffd0500ecb15453fab9d30
> Author: Steffen Eiden <seiden@linux.ibm.com>
> 
> KVM: x86: Use file_to_kvm_x86() in SEV
> 
> This commit replaces the open-coded file check and private_data cast
> with a new arch-namespaced helper file_to_kvm_x86().
> 
>> diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
>> index 944aaea6501f2..2787b832c9e0f 100644
>> --- a/arch/x86/kvm/svm/sev.c
>> +++ b/arch/x86/kvm/svm/sev.c
>> @@ -2121,10 +2121,10 @@ int sev_vm_move_enc_context_from(struct kvm *kvm, unsigned int source_fd)
>>   	if (fd_empty(f))
>>   		return -EBADF;
>>   
>> -	if (!file_is_kvm(fd_file(f)))
>> +	source_kvm = file_to_kvm_x86(fd_file(f));
> 
> [Severity: Low]
> Is file_to_kvm_x86() defined anywhere in the kernel source tree at this
> commit? It appears to be missing, which will cause an implicit
> declaration compiler error here in sev_vm_move_enc_context_from().
> Could it be that the patch introducing this helper was omitted from the
> series or ordered after this patch?

false positive, see patch1.



  reply	other threads:[~2026-10-09 14:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 14:27 [GIT PULL 0/6] KVM/vfio: Use file-based reference counting for KVM Christian Borntraeger
2026-10-09 14:27 ` [GIT PULL 1/6] KVM: Introduce file_to_kvm_<arch>() infrastructure Christian Borntraeger
2026-10-09 14:37   ` sashiko-bot
2026-10-09 14:27 ` [GIT PULL 2/6] KVM: Add file back-pointer to struct kvm Christian Borntraeger
2026-10-09 14:40   ` sashiko-bot
2026-10-09 14:27 ` [GIT PULL 3/6] KVM: x86: Use file_to_kvm_x86() in SEV Christian Borntraeger
2026-10-09 14:36   ` sashiko-bot
2026-10-09 14:53     ` Christian Borntraeger [this message]
2026-10-09 14:27 ` [GIT PULL 4/6] KVM/vfio: Use file-based reference counting for KVM Christian Borntraeger
2026-10-09 14:56   ` sashiko-bot
2026-10-09 16:06     ` Paolo Bonzini
2026-10-09 16:46       ` Christian Borntraeger
2026-10-09 14:27 ` [GIT PULL 5/6] KVM: Restrict kvm_get_kvm/kvm_put_kvm export to internal KVM modules Christian Borntraeger
2026-10-09 14:27 ` [GIT PULL 6/6] KVM: Remove unused file_is_kvm Christian Borntraeger
2026-10-09 16:30 ` [GIT PULL 0/6] KVM/vfio: Use file-based reference counting for KVM Paolo Bonzini

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=95c55fab-cd04-497f-9266-6c30353d73e4@linux.ibm.com \
    --to=borntraeger@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=sashiko-reviews@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox