All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Hunt, David" <david.hunt@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Hunt, David" <david.hunt@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] examples/vm_power_manager: fix buffer overrun
Date: Thu, 18 Apr 2019 15:14:07 +0000	[thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A449608@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <20190410124910.24537-1-david.hunt@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of David Hunt
> Sent: Wednesday, April 10, 2019 1:49 PM
> To: dev@dpdk.org
> Cc: Hunt, David <david.hunt@intel.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH v1] examples/vm_power_manager: fix buffer
> overrun
> 
> The freqs array in freq_info struct has RTE_MAX_LCORE_FREQS elements, yet
> the code can attemtp to look at the index at POWER_MANAGER_MAX_CPUS,

Couple of nit-picks,

:%s/ attempt/ attempt

> which may be greater than RTE_MAX_LCORE_FREQS. Fix to limit index to
> RTE_MAX_LCORE_FREQS.
> 
> Fixes: d26c18c93260 ("examples/vm_power: cpu frequency in host")
>      Coverity issue: 337660

Candidate for stable@dpdk.org?

Acked-by: Reshma Pattan <reshma.pattan@intel.com>

Thanks,
Reshma

  reply	other threads:[~2019-04-18 15:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 12:49 [dpdk-dev] [PATCH v1] examples/vm_power_manager: fix buffer overrun David Hunt
2019-04-18 15:14 ` Pattan, Reshma [this message]
2019-04-23 10:26   ` Kevin Traynor
2019-04-23 10:31     ` Hunt, David
2019-04-23 10:42       ` Kevin Traynor
2019-04-22 21:54 ` Thomas Monjalon
2019-04-23  8:21   ` Hunt, David
2019-04-23  8:33     ` Thomas Monjalon
2019-04-23  8:35       ` Hunt, David
2019-04-23  8:53 ` [dpdk-dev] [PATCH v2] " David Hunt
2019-04-26  8:42   ` [dpdk-dev] [PATCH v3] " David Hunt
2019-05-02 23:38     ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon

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=3AEA2BF9852C6F48A459DA490692831F2A449608@irsmsx110.ger.corp.intel.com \
    --to=reshma.pattan@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.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.