From: Stefan Hajnoczi <stefanha@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tests/virtio-9p: explicitely handle potential integer overflows
Date: Tue, 30 Jan 2018 12:03:42 +0000 [thread overview]
Message-ID: <20180130120342.GC15551@stefanha-x1.localdomain> (raw)
In-Reply-To: <151730107324.755.12264321256439401751.stgit@bahia.lan>
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
On Tue, Jan 30, 2018 at 09:32:48AM +0100, Greg Kurz wrote:
> Signed-off-by: Greg Kurz <groug@kaod.org>
> ---
> tests/virtio-9p-test.c | 31 +++++++++++++++++++++----------
> 1 file changed, 21 insertions(+), 10 deletions(-)
>
> This is based on SHA1 2eab02aa260ac5405e1e51c9cc1b4c3aa23fc45a from my
> 9p-next branch:
>
> https://github.com/gkurz/qemu/commits/9p-next
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-01-30 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 8:32 [Qemu-devel] [PATCH] tests/virtio-9p: explicitely handle potential integer overflows Greg Kurz
2018-01-30 12:03 ` Stefan Hajnoczi [this message]
2018-01-30 13:56 ` Eric Blake
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=20180130120342.GC15551@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=groug@kaod.org \
--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).