qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: P J P <ppandit@redhat.com>, Qemu Developers <qemu-devel@nongnu.org>
Cc: Yang Hongke <yanghongke@huawei.com>,
	Prasad J Pandit <pjp@fedoraproject.org>
Subject: Re: [Qemu-devel] [PATCH v2] net: ne2000: check ring buffer control registers
Date: Wed, 24 Feb 2016 16:13:08 +0800	[thread overview]
Message-ID: <56CD6614.1000106@redhat.com> (raw)
In-Reply-To: <1456294293-26027-1-git-send-email-ppandit@redhat.com>



On 02/24/2016 02:11 PM, P J P wrote:
> From: Prasad J Pandit <pjp@fedoraproject.org>
>
> Ne2000 NIC uses ring buffer of NE2000_MEM_SIZE(49152)
> bytes to process network packets. Registers PSTART & PSTOP
> define ring buffer size & location. Setting these registers
> to invalid values could lead to infinite loop or OOB r/w
> access issues. Add check to avoid it.
>
> Reported-by: Yang Hongke <yanghongke@huawei.com>
> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
> ---
>  hw/net/ne2000.c | 4 ++++
>  1 file changed, 4 insertions(+)
>
> Update per review:
>   -> https://lists.gnu.org/archive/html/qemu-devel/2016-02/msg05522.html
>
> diff --git a/hw/net/ne2000.c b/hw/net/ne2000.c
> index b032212..ced4666 100644
> --- a/hw/net/ne2000.c
> +++ b/hw/net/ne2000.c
> @@ -154,6 +154,10 @@ static int ne2000_buffer_full(NE2000State *s)
>  {
>      int avail, index, boundary;
>  
> +    if (s->stop <= s->start) {
> +        return 1;
> +    }
> +
>      index = s->curpag << 8;
>      boundary = s->boundary << 8;
>      if (index < boundary)

Hongke, would you mind to test this patch to see if it fixes your issue
and add a "Tested-by" tag?

Thanks

  reply	other threads:[~2016-02-24  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  6:11 [Qemu-devel] [PATCH v2] net: ne2000: check ring buffer control registers P J P
2016-02-24  8:13 ` Jason Wang [this message]
2016-02-24  9:25   ` [Qemu-devel] 答复: " yanghongke
2016-02-26  6:13     ` Jason Wang
2016-02-26  6:39   ` yanghongke

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=56CD6614.1000106@redhat.com \
    --to=jasowang@redhat.com \
    --cc=pjp@fedoraproject.org \
    --cc=ppandit@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yanghongke@huawei.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).