From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] Add 'fall through' comments to case statements without break
Date: Tue, 10 Jan 2012 08:35:55 +0000 [thread overview]
Message-ID: <20120110083555.GA13145@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <1326130191-20344-1-git-send-email-sw@weilnetz.de>
On Mon, Jan 09, 2012 at 06:29:51PM +0100, Stefan Weil wrote:
> These comments are used by static code analysis tools and in code reviews
> to avoid false warnings because of missing break statements.
>
> The case statements handled here were reported by coverity.
>
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
> hw/pcnet.c | 1 +
> json-lexer.c | 1 +
> qemu-option.c | 4 ++++
> 3 files changed, 6 insertions(+), 0 deletions(-)
This reminds me of another questionable fall-through:
bt-host.c:bt_host_read():
while (s->len --)
switch (*pkt ++) {
...
case HCI_SCODATA_PKT:
if (s->len < 3)
goto bad_pkt;
pktlen = MIN(pkt[2] + 3, s->len);
s->len -= pktlen;
pkt += pktlen;
<--- fall-through or not?
default:
bad_pkt:
fprintf(stderr, "qemu: bad HCI packet type %02x\n", pkt[-1]);
}
It seems the code will skip HCI_SCODATA_PKT and report a warning (although type
pkt[-1] will be incorrect). Any thoughts?
Stefan
next prev parent reply other threads:[~2012-01-10 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 17:29 [Qemu-devel] [PATCH] Add 'fall through' comments to case statements without break Stefan Weil
2012-01-09 17:34 ` Peter Maydell
2012-01-10 8:35 ` Stefan Hajnoczi [this message]
2012-01-10 21:52 ` [Qemu-devel] [Qemu-trivial] " Stefan Weil
2012-01-12 13:05 ` andrzej zaborowski
2012-01-12 13:16 ` Stefan Hajnoczi
2012-01-12 13:21 ` Stefan Hajnoczi
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=20120110083555.GA13145@stefanha-thinkpad.localdomain \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).