From: "Jan H. Schönherr" <jschoenh@amazon.de>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: mpe <mpe@ellerman.id>,
linux-kernel <linux-kernel@vger.kernel.org>,
sachinp <sachinp@linux.vnet.ibm.com>
Subject: Re: [mainline][bisected 36ae3c0] Build fail at virt/kvm/eventfd.c:568
Date: Sat, 16 Sep 2017 19:46:59 +0200 [thread overview]
Message-ID: <04cde7c8-d41f-96e2-2b4b-2287b8f04bfc@amazon.de> (raw)
In-Reply-To: <1505579069.9665.22.camel@abdul.in.ibm.com>
On 09/16/2017 06:24 PM, Abdul Haleem wrote:
> Hi,
>
> Today's mainline kernel failed to build on powerpc with below error
>
> arch/powerpc/kvm/../../../virt/kvm/eventfd.c: In function ‘kvm_irqfd’:
> arch/powerpc/kvm/../../../virt/kvm/eventfd.c:568:19: error:
> ‘KVM_MAX_IRQ_ROUTES’ undeclared (first use in this function)
> if (args->gsi >= KVM_MAX_IRQ_ROUTES)
Hmm... the header file for that constant is included...
... but it's only defined when CONFIG_HAVE_KVM_IRQ_ROUTING, which is not the case here.
We can either make that "if" conditional on that, or we revert the commit.
The commit was meant the give user space an early indication that something is wrong.
I was only aware of the IRQ routing use case. This indicates that there are other
use cases. To err on the side of caution, I'd favor a revert as the patch is not strictly
needed -- unless someone else can provide more insight on valid values for GSI.
Paolo, do you want me to prepare a revert for the commit below?
Regards
Jan
> Possible bad commit is :
>
> commit 36ae3c0a36b7456432fedce38ae2f7bd3e01a563
> Author: Jan H. Schönherr <jschoenh@amazon.de>
> Date: Thu Sep 7 19:02:48 2017 +0100
>
> KVM: Don't accept obviously wrong gsi values via KVM_IRQFD
>
> We cannot add routes for gsi values >= KVM_MAX_IRQ_ROUTES -- see
> kvm_set_irq_routing(). Hence, there is no sense in accepting them
> via KVM_IRQFD. Prevent them from entering the system in the first
> place.
>
> Signed-off-by: Jan H. Schönherr <jschoenh@amazon.de>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>
> diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c
> index f2ac53a..c608ab4 100644
> --- a/virt/kvm/eventfd.c
> +++ b/virt/kvm/eventfd.c
> @@ -565,6 +565,8 @@ kvm_irqfd(struct kvm *kvm, struct kvm_irqfd *args)
> {
> if (args->flags & ~(KVM_IRQFD_FLAG_DEASSIGN |
> KVM_IRQFD_FLAG_RESAMPLE))
> return -EINVAL;
> + if (args->gsi >= KVM_MAX_IRQ_ROUTES)
> + return -EINVAL;
>
> if (args->flags & KVM_IRQFD_FLAG_DEASSIGN)
> return kvm_irqfd_deassign(kvm, args);
>
>
next prev parent reply other threads:[~2017-09-16 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 16:24 [mainline][bisected 36ae3c0] Build fail at virt/kvm/eventfd.c:568 Abdul Haleem
2017-09-16 17:46 ` Jan H. Schönherr [this message]
2017-09-16 20:12 ` [PATCH] Revert "KVM: Don't accept obviously wrong gsi values via KVM_IRQFD" Jan H. Schönherr
2017-09-18 6:44 ` Michael Ellerman
2017-09-18 8:11 ` Paolo Bonzini
2017-09-18 12:21 ` David Hildenbrand
2017-09-20 1:31 ` [PATCH] KVM: KVM_MAX_IRQ_ROUTES only defined with CONFIG_HAVE_KVM_IRQ_ROUTING Daniel Black
2017-09-20 5:05 ` Daniel Black
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=04cde7c8-d41f-96e2-2b4b-2287b8f04bfc@amazon.de \
--to=jschoenh@amazon.de \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id \
--cc=pbonzini@redhat.com \
--cc=sachinp@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).