Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Ricardo Koller <ricarkol@google.com>
To: Oliver Upton <oupton@google.com>
Cc: kvm@vger.kernel.org, maz@kernel.org, rananta@google.com,
	pshier@google.com, catalin.marinas@arm.com,
	kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] KVM: arm64: vgic: drop WARN from vgic_get_irq
Date: Wed, 18 Aug 2021 14:45:04 -0700	[thread overview]
Message-ID: <YR1/YEY8DX+r05nt@google.com> (raw)
In-Reply-To: <CAOQ_QshVenuri8WdZdEis4szCv03U0KRNt4CqDNtvUBsqBqUoA@mail.gmail.com>

On Wed, Aug 18, 2021 at 02:34:03PM -0700, Oliver Upton wrote:
> Hi Ricardo,
> 
> On Wed, Aug 18, 2021 at 2:32 PM Ricardo Koller <ricarkol@google.com> wrote:
> >
> > vgic_get_irq(intid) is used all over the vgic code in order to get a
> > reference to a struct irq. It warns whenever intid is not a valid number
> > (like when it's a reserved IRQ number). The issue is that this warning
> > can be triggered from userspace (e.g., KVM_IRQ_LINE for intid 1020).
> >
> > Drop the WARN call from vgic_get_irq.
> >
> > Signed-off-by: Ricardo Koller <ricarkol@google.com>
> > ---
> >  arch/arm64/kvm/vgic/vgic.c | 1 -
> >  1 file changed, 1 deletion(-)
> >
> > diff --git a/arch/arm64/kvm/vgic/vgic.c b/arch/arm64/kvm/vgic/vgic.c
> > index 111bff47e471..81cec508d413 100644
> > --- a/arch/arm64/kvm/vgic/vgic.c
> > +++ b/arch/arm64/kvm/vgic/vgic.c
> > @@ -106,7 +106,6 @@ struct vgic_irq *vgic_get_irq(struct kvm *kvm, struct kvm_vcpu *vcpu,
> >         if (intid >= VGIC_MIN_LPI)
> >                 return vgic_get_lpi(kvm, intid);
> >
> > -       WARN(1, "Looking up struct vgic_irq for reserved INTID");
> 
> Could we maybe downgrade the message to WARN_ONCE() (to get a stack)
> or pr_warn_ratelimited()? I agree it is problematic that userspace can
> cause this WARN to fire, but it'd be helpful for debugging too.
> 

Was thinking about that, until I found this in bug.h:

	/*
	 * WARN(), WARN_ON(), WARN_ON_ONCE, and so on can be used to report
	 * significant kernel issues that need prompt attention if they should ever
	 * appear at runtime.
	 *
	 * Do not use these macros when checking for invalid external inputs
	 * (e.g. invalid system call arguments, or invalid data coming from
	 * network/devices),

Just in case, KVM_IRQ_LINE returns -EINVAL for an invalid intid (like
1020). I think it's more appropriate for the vmm to log it. What do you
think?

Thanks,
Ricardo

> --
> Thanks,
> Oliver
> 
> >         return NULL;
> >  }
> >
> > --
> > 2.33.0.rc2.250.ged5fa647cd-goog
> >
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2021-08-18 21:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 21:32 [PATCH] KVM: arm64: vgic: drop WARN from vgic_get_irq Ricardo Koller
2021-08-18 21:34 ` Oliver Upton
2021-08-18 21:45   ` Ricardo Koller [this message]
2021-08-19  7:41     ` Oliver Upton
2021-08-19  8:04       ` Marc Zyngier
2021-08-19  8:16         ` Oliver Upton
2021-08-19 10:47 ` Marc Zyngier

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=YR1/YEY8DX+r05nt@google.com \
    --to=ricarkol@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=maz@kernel.org \
    --cc=oupton@google.com \
    --cc=pshier@google.com \
    --cc=rananta@google.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