[dpdk-dev] net/ixgbe: Put correct id values in ixgbevf_dev_xstats_get
Checks
Commit Message
Without setting the id, calling xstats_get twice with same array causes memory corruption.
Also, if IXGBEVF_NB_XSTATS will be different than 1 in the future, this will cause issues.
Signed-off-by: Ido Barnea <ibarnea@cisco.com>
---
drivers/net/ixgbe/ixgbe_ethdev.c | 1 +
1 file changed, 1 insertion(+)
Comments
On 3/7/2017 2:28 PM, Ido Barnea (ibarnea) wrote:
> Without setting the id, calling xstats_get twice with same array causes memory corruption.
> Also, if IXGBEVF_NB_XSTATS will be different than 1 in the future, this will cause issues.
>
> Signed-off-by: Ido Barnea <ibarnea@cisco.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
On 3/9/2017 4:46 PM, Ferruh Yigit wrote:
> On 3/7/2017 2:28 PM, Ido Barnea (ibarnea) wrote:
>> Without setting the id, calling xstats_get twice with same array causes memory corruption.
>> Also, if IXGBEVF_NB_XSTATS will be different than 1 in the future, this will cause issues.
>>
>> Signed-off-by: Ido Barnea <ibarnea@cisco.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
@@ -3249,6 +3249,7 @@ ixgbevf_dev_xstats_get(struct rte_eth_dev *dev, struct rte_eth_xstat *xstats,
/* Extended stats */
for (i = 0; i < IXGBEVF_NB_XSTATS; i++) {
+ xstats[i].id = i;
xstats[i].value = *(uint64_t *)(((char *)hw_stats) +
rte_ixgbevf_stats_strings[i].offset);
}
--
2.8.3