From: Thomas Monjalon <thomas@monjalon.net>
To: David Hunt <david.hunt@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] examples/vm_power_manager: fix buffer overrun
Date: Fri, 03 May 2019 01:38:21 +0200 [thread overview]
Message-ID: <2453136.0L2uUJhSfQ@xps> (raw)
Message-ID: <20190502233821.i0hVP_kZqOQ1Pc2xDO5t2Ac9mfRqOEqXNUCGDDZTwns@z> (raw)
In-Reply-To: <20190426084209.3853-1-david.hunt@intel.com>
26/04/2019 10:42, David Hunt:
> The freqs array in freq_info struct has RTE_MAX_LCORE_FREQS elements,
> yet the code can attempt to look at the index at RTE_MAX_LCORE,
> 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
> CC: stable@dpdk.org
> Signed-off-by: David Hunt <david.hunt@intel.com>
> Acked-by: Reshma Pattan <reshma.pattan@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-05-02 23:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 12:49 [dpdk-dev] [PATCH v1] " David Hunt
2019-04-10 12:49 ` David Hunt
2019-04-18 15:14 ` Pattan, Reshma
2019-04-18 15:14 ` Pattan, Reshma
2019-04-23 10:26 ` Kevin Traynor
2019-04-23 10:26 ` Kevin Traynor
2019-04-23 10:31 ` Hunt, David
2019-04-23 10:31 ` Hunt, David
2019-04-23 10:42 ` Kevin Traynor
2019-04-23 10:42 ` Kevin Traynor
2019-04-22 21:54 ` Thomas Monjalon
2019-04-22 21:54 ` Thomas Monjalon
2019-04-23 8:21 ` Hunt, David
2019-04-23 8:21 ` Hunt, David
2019-04-23 8:33 ` Thomas Monjalon
2019-04-23 8:33 ` Thomas Monjalon
2019-04-23 8:35 ` Hunt, David
2019-04-23 8:35 ` Hunt, David
2019-04-23 8:53 ` [dpdk-dev] [PATCH v2] " David Hunt
2019-04-23 8:53 ` David Hunt
2019-04-26 8:42 ` [dpdk-dev] [PATCH v3] " David Hunt
2019-04-26 8:42 ` David Hunt
2019-05-02 23:38 ` Thomas Monjalon [this message]
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=2453136.0L2uUJhSfQ@xps \
--to=thomas@monjalon.net \
--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 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).