From: Jim Meyering <jim@meyering.net>
To: qemu-devel@nongnu.org
Cc: Jim Meyering <meyering@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] memset/sizeof abuse
Date: Thu, 10 May 2012 18:19:46 +0200 [thread overview]
Message-ID: <1336666788-30233-1-git-send-email-jim@meyering.net> (raw)
From: Jim Meyering <meyering@redhat.com>
I ran coverity on all of qemu and have begun going through the results.
A couple problems jumped out as obvious and easy to fix:
Jim Meyering (2):
kvm/apic: correct short memset
cadence_gem: avoid stack-writing buffer-overrun
hw/cadence_gem.c | 2 +-
hw/kvm/apic.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
1.7.10.1.487.ga3935e6
next reply other threads:[~2012-05-10 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 16:19 Jim Meyering [this message]
2012-05-10 16:19 ` [Qemu-devel] [PATCH 1/2] kvm/apic: correct short memset Jim Meyering
2012-05-10 17:28 ` Jan Kiszka
2012-05-22 20:30 ` [Qemu-devel] [PATCH 1.1 " Stefan Weil
2012-05-23 10:33 ` Jan Kiszka
2012-06-10 20:29 ` Stefan Weil
2012-06-11 5:29 ` Jan Kiszka
2012-06-11 9:58 ` [Qemu-devel] [PATCH " Avi Kivity
2012-05-10 16:19 ` [Qemu-devel] [PATCH 2/2] cadence_gem: avoid stack-writing buffer-overrun Jim Meyering
2012-05-14 4:57 ` Peter Crosthwaite
2012-06-10 20:34 ` Stefan Weil
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=1336666788-30233-1-git-send-email-jim@meyering.net \
--to=jim@meyering.net \
--cc=meyering@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).