From: Stefan Hajnoczi <stefanha@gmail.com>
To: P J P <ppandit@redhat.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
jasowang@redhat.com, qemu-devel@nongnu.org,
Qinghao Tang <luodalongde@gmail.com>,
Scott Feldman <sfeldma@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] net: rocker: fix an incorrect array bounds check
Date: Wed, 23 Dec 2015 12:50:12 +0800 [thread overview]
Message-ID: <20151223045012.GD5149@stefanha-x1.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.20.1512230043500.9878@wniryva>
[-- Attachment #1: Type: text/plain, Size: 2111 bytes --]
On Wed, Dec 23, 2015 at 12:54:18AM +0530, P J P wrote:
> Hello Paolo, all
>
> Please see an updated patch below, as per suggestion in
> -> https://lists.gnu.org/archive/html/qemu-devel/2015-12/msg04057.html
Adding Jason Wang (net maintainer) on CC.
> ===
> >From 344a487d637be20b3fb110bec36cb703e7f6ecaa Mon Sep 17 00:00:00 2001
> From: Prasad J Pandit <pjp@fedoraproject.org>
> Date: Wed, 23 Dec 2015 00:40:13 +0530
> Subject: [PATCH v2] net: rocker: fix an incorrect array bounds check
>
> While processing transmit(tx) descriptors in 'tx_consume' routine
> the switch emulator suffers from an off-by-one error, if a
> descriptor was to have more than allowed(ROCKER_TX_FRAGS_MAX=16)
> fragments. Fix an incorrect bounds check to avoid it.
>
> Reported-by: Qinghao Tang <luodalongde@gmail.com>
> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
> ---
> hw/net/rocker/rocker.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> 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) {
> --
> 2.4.3
> ===
>
>
> Thank you.
> --
> Prasad J Pandit / Red Hat Product Security Team
> 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-23 4:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 19:24 [Qemu-devel] [PATCH v2] net: rocker: fix an incorrect array bounds check P J P
2015-12-23 4:50 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-22 21:41 Peter Maydell
2015-12-23 5:14 ` P J P
2015-12-28 4:22 ` Jason Wang
2015-12-28 11:34 ` P J P
2015-12-28 10:54 P J P
2015-12-29 2:24 ` 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=20151223045012.GD5149@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=jasowang@redhat.com \
--cc=jiri@resnulli.us \
--cc=luodalongde@gmail.com \
--cc=pbonzini@redhat.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 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).