From: Peter Lieven <pl@kamp.de>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, dhannawatpooja1@gmail.com, jasowang@redhat.com
Subject: Re: [Qemu-devel] [PATCH] net: limit allocation in nc_sendv_compat
Date: Fri, 16 Sep 2016 15:27:54 +0200 [thread overview]
Message-ID: <c4343f10-fd3f-0f82-64d9-d3ad32eb7e26@kamp.de> (raw)
In-Reply-To: <20160630133914.GB13793@stefanha-x1.localdomain>
Am 30.06.2016 um 15:39 schrieb Stefan Hajnoczi:
> On Thu, Jun 30, 2016 at 11:49:40AM +0200, Peter Lieven wrote:
>> we only need to allocate enough memory to hold the packet. This might be
>> less than NET_BUFSIZE. Additionally fail early if the packet is larger
>> than NET_BUFSIZE.
>>
>> Signed-off-by: Peter Lieven <pl@kamp.de>
>> ---
>> net/net.c | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Can somebody pick this up please?
Thanks,
Peter
next prev parent reply other threads:[~2016-09-16 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 9:49 [Qemu-devel] [PATCH] net: limit allocation in nc_sendv_compat Peter Lieven
2016-06-30 13:39 ` Stefan Hajnoczi
2016-09-16 13:27 ` Peter Lieven [this message]
2016-09-22 7:34 ` Jason Wang
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=c4343f10-fd3f-0f82-64d9-d3ad32eb7e26@kamp.de \
--to=pl@kamp.de \
--cc=dhannawatpooja1@gmail.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).