qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] input-linux: fix Coverity warning
Date: Wed, 16 Mar 2016 13:35:49 +0100	[thread overview]
Message-ID: <1458131749.30910.13.camel@redhat.com> (raw)
In-Reply-To: <56E94BA9.5050309@weilnetz.de>

On Mi, 2016-03-16 at 13:03 +0100, Stefan Weil wrote:
> Am 16.03.2016 um 12:50 schrieb Gerd Hoffmann:
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> --- 
> > ui/input-linux.c | 7 +++++++ 1 file changed, 7 insertions(+)
> > 
> > diff --git a/ui/input-linux.c b/ui/input-linux.c index
> > 76a2abb..f884c00 100644 --- a/ui/input-linux.c +++
> > b/ui/input-linux.c @@ -257,6 +257,13 @@ static void
> > input_linux_event_keyboard(void *opaque) */ continue; } +
> > if (event.code >= KEY_CNT) { +                /* +
> > * Should not happen.  But better safe than sorry, +
> > * and we make Coverity happy too. +                 */ +
> > continue; +            } /* keep track of key state */ if
> > (!il->keydown[event.code] && event.value) { il->keydown[event.code]
> > = true;
> > 
> 
> As it should not happen, I'd prefer this variant:
> 
> g_assert(event.code < KEY_CNT);

Well, it is highly unlikely but not impossible.  KEY_CNT changed from
0x200 to 0x300 in kernel 2.6.28.  If (a) this happens again and (b) a
new key > 0x300 is pressed and (c) we didn't sync the linux headers yet
so qemu still has the old KEY_CNT value we could hit this.

cheers,
  Gerd

      reply	other threads:[~2016-03-16 12:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 11:50 [Qemu-devel] [PATCH] input-linux: fix Coverity warning Gerd Hoffmann
2016-03-16 12:03 ` Stefan Weil
2016-03-16 12:35   ` Gerd Hoffmann [this message]

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=1458131749.30910.13.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).