From: Jason Wang <jasowang@redhat.com>
To: P J P <ppandit@redhat.com>, Markus Armbruster <armbru@redhat.com>
Cc: Oleksandr Bazhaniuk <oleksandr.bazhaniuk@intel.com>,
Qemu Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] net: mipsnet: check packet length against buffer
Date: Mon, 11 Apr 2016 16:27:52 +0800 [thread overview]
Message-ID: <570B6008.6050609@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1604111301070.12194@wniryva>
On 04/11/2016 03:37 PM, P J P wrote:
> +-- On Thu, 7 Apr 2016, Markus Armbruster wrote --+
> | P J P <ppandit@redhat.com> writes:
> |
> | > --- a/hw/net/mipsnet.c
> | > +++ b/hw/net/mipsnet.c
> | > @@ -82,6 +82,9 @@ static ssize_t mipsnet_receive(NetClientState *nc, const uint8_t *buf, size_t si
> | > if (!mipsnet_can_receive(nc))
> | > return 0;
> | >
> | > + if (size >= sizeof(s->rx_buffer)) {
> | > + return 0;
> | > + }
> | > s->busy = 1;
> |
> | Prompted by Peter Maydell's review of the buddy patch to stellaris_enet:
> | What does the physical device do when it receives such a packet?
>
> I tried to find a device specification, but couldn't find any reference
> MIPSnet.
>
> Jason, wdyt?
Can't find either. Looking at kernel driver git logs, the driver was
even removed since 2012 because it was not longer supported by MIPS.
Consider it indeed fixes a memory corruption, I tend to apply this first
for 2.6.
> --
> Prasad J Pandit / Red Hat Product Security Team
> 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
>
next prev parent reply other threads:[~2016-04-11 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 10:26 [Qemu-devel] [PATCH] net: mipsnet: check packet length against buffer P J P
2016-04-07 15:44 ` Markus Armbruster
2016-04-11 7:37 ` P J P
2016-04-11 8:27 ` Jason Wang [this message]
2016-04-11 8:51 ` P J P
2016-04-26 7:16 ` 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=570B6008.6050609@redhat.com \
--to=jasowang@redhat.com \
--cc=armbru@redhat.com \
--cc=oleksandr.bazhaniuk@intel.com \
--cc=ppandit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.