DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>,
	david.marchand@6wind.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] eal: out-of-bounds write
Date: Tue, 14 Jun 2016 10:26:40 +0100	[thread overview]
Message-ID: <632ca0d5-86a2-6c7f-f9b1-14ca95633bdc@intel.com> (raw)
In-Reply-To: <1465894956-14016-1-git-send-email-slawomirx.mrozowicz@intel.com>

On 14/06/2016 10:02, Slawomir Mrozowicz wrote:
> Overrunning array mcfg->memseg of 256 44-byte elements
> at element index 257 using index j.
> Fixed by add condition with message information.
>
> Fixes: af75078fece3 ("first public release")
> Coverity ID 13282
>
> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> ---
>   lib/librte_eal/linuxapp/eal/eal_memory.c | 19 +++++++++++++++++--
>   1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal_memory.c b/lib/librte_eal/linuxapp/eal/eal_memory.c
> index 5b9132c..6a2daf5 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_memory.c
> +++ b/lib/librte_eal/linuxapp/eal/eal_memory.c
> @@ -1301,6 +1301,15 @@ rte_eal_hugepage_init(void)
>   			break;
>   		}
>   
> +	if (j >= RTE_MAX_MEMSEG) {
> +		RTE_LOG(ERR, EAL,
> +			"Failed: all memsegs used by ivshmem.\n"
> +			"Current %d is not enough.\n"
> +			"Please either increase the RTE_MAX_MEMSEG\n",
> +			RTE_MAX_MEMSEG);
> +		return -ENOMEM;
> +	}
> +
>   	for (i = 0; i < nr_hugefiles; i++) {
>   		new_memseg = 0;
>   
> @@ -1333,8 +1342,14 @@ rte_eal_hugepage_init(void)
>   
>   		if (new_memseg) {
>   			j += 1;
> -			if (j == RTE_MAX_MEMSEG)
> -				break;
> +			if (j >= RTE_MAX_MEMSEG) {
> +				RTE_LOG(ERR, EAL,
> +					"Failed: all memsegs used by ivshmem.\n"
> +					"Current %d is not enough.\n"
> +					"Please either increase the RTE_MAX_MEMSEG\n",
> +					RTE_MAX_MEMSEG);
> +				return -ENOMEM;
> +			}
>   

I don't think you need to change anything inside the for loop.
As it is in the patch, the error message is not accurate.
What I tried to say in my previous review was to not touch the loop and 
just do the check before the loop.
There is an error message after the loop which is correct for all cases 
except the case this patch is
addressing by checking before the loop.

Sergio

>   			mcfg->memseg[j].phys_addr = hugepage[i].physaddr;
>   			mcfg->memseg[j].addr = hugepage[i].final_va;

      reply	other threads:[~2016-06-14  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14  9:02 Slawomir Mrozowicz
2016-06-14  9:26 ` Sergio Gonzalez Monroy [this message]

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=632ca0d5-86a2-6c7f-f9b1-14ca95633bdc@intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=slawomirx.mrozowicz@intel.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).