From: P J P <ppandit@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Gerben van der Lubbe <spoofedexistence@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Limit memory r/w length to buffer size
Date: Wed, 14 Oct 2015 11:57:51 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.20.1510141148070.9023@wniryva> (raw)
In-Reply-To: <874mhuh9ym.fsf@blackfin.pond.sub.org>
+-- On Tue, 13 Oct 2015, Markus Armbruster wrote --+
| How is this related to Kevin's
| [PATCH] gdbstub: Fix buffer overflows in gdb_handle_packet()
| Message-Id: <1444721930-5121-1-git-send-email-kwolf@redhat.com> ?
Oh, didn't know there was already a patch. Yes it fixes the same issues;
Also the length check is correct. In my patch I did not consider the size
alterations that occur in memtohex() & hextomem().
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
prev parent reply other threads:[~2015-10-14 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 19:31 [Qemu-devel] [PATCH] Limit memory r/w length to buffer size P J P
2015-10-13 18:29 ` P J P
2015-10-13 18:58 ` Markus Armbruster
2015-10-14 6:27 ` P J P [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=alpine.LFD.2.20.1510141148070.9023@wniryva \
--to=ppandit@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spoofedexistence@gmail.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;
as well as URLs for NNTP newsgroup(s).