All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Qinghao Tang <luodalongde@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>, Scott Feldman <sfeldma@gmail.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] net: rocker: fix an incorrect array bounds check
Date: Tue, 22 Dec 2015 19:13:11 +0100	[thread overview]
Message-ID: <567992B7.1020408@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1512222248450.5574@wniryva>



On 22/12/2015 18:26, P J P wrote:
> +-- On Tue, 22 Dec 2015, Paolo Bonzini wrote --+
> | > -        if (++iovcnt > ROCKER_TX_FRAGS_MAX) {
> | > +        if (++iovcnt >= ROCKER_TX_FRAGS_MAX) {
> | 
> | Doesn't this forbid some valid ROCKER_TX_FRAGS_MAX-element iovecs?
> 
>   forbid..?  Sorry, I did not get the question.
> 
> | The check should be moved before the assignment to iov[iovcnt].iov_len.
> 
>   You mean like below..?
> 
> ===
> diff --git a/hw/net/rocker/rocker.c b/hw/net/rocker/rocker.c
> index c57f1a6..2e77e50 100644
> --- a/hw/net/rocker/rocker.c
> +++ b/hw/net/rocker/rocker.c
> @@ -232,6 +232,9 @@ static int tx_consume(Rocker *r, DescInfo *info)
>          frag_addr = rocker_tlv_get_le64(tlvs[ROCKER_TLV_TX_FRAG_ATTR_ADDR]);
>          frag_len = rocker_tlv_get_le16(tlvs[ROCKER_TLV_TX_FRAG_ATTR_LEN]);
>  
> +        if (iovcnt >= ROCKER_TX_FRAGS_MAX) {
> +            goto err_too_many_frags;
> +        }
>          iov[iovcnt].iov_len = frag_len;
>          iov[iovcnt].iov_base = g_malloc(frag_len);
>          if (!iov[iovcnt].iov_base) {
> @@ -244,10 +247,7 @@ static int tx_consume(Rocker *r, DescInfo *info)
>              err = -ROCKER_ENXIO;
>              goto err_bad_io;
>          }
> -
> -        if (++iovcnt > ROCKER_TX_FRAGS_MAX) {
> -            goto err_too_many_frags;
> -        }
> +        iovcnt++;
>      }
>  
>      if (iovcnt) {
> ===
> 
> Thank you.
> --
> Prasad J Pandit / Red Hat Product Security Team
> 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
> 
> 

Yes, can you submit it as v2?

Paolo

  reply	other threads:[~2015-12-22 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 13:07 [Qemu-devel] [PATCH] net: rocker: fix an incorrect array bounds check P J P
2015-12-22 13:36 ` Jiri Pirko
2015-12-22 14:45   ` P J P
2015-12-22 14:46 ` Paolo Bonzini
2015-12-22 17:26   ` P J P
2015-12-22 18:13     ` Paolo Bonzini [this message]
2015-12-22 19:04       ` P J P

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=567992B7.1020408@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=luodalongde@gmail.com \
    --cc=ppandit@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sfeldma@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 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.