From: Kevin Traynor <ktraynor@redhat.com>
To: Shiri Kuzin <shirik@nvidia.com>, stable@dpdk.org
Cc: viacheslavo@nvidia.com,
Ralf Hoffmann <ralf.hoffmann@allegro-packets.com>,
Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-stable] [PATCH] [18.11] net/mlx5: fix xstats reset reinitialization
Date: Tue, 8 Dec 2020 10:37:14 +0000 [thread overview]
Message-ID: <911a1e57-b54a-1727-4901-431936ead2a9@redhat.com> (raw)
In-Reply-To: <20201208075435.24659-1-shirik@nvidia.com>
On 08/12/2020 07:54, Shiri Kuzin wrote:
> [ upstream commit 42dcd453d9b63841a5460a6ca3872eb7648d73bd ]
>
> The mlx5_xstats_reset clears the device extended statistics.
> In this function the driver may reinitialize the structures
> that are used to read device counters.
>
> In case of reinitialization, the number of counters may
> change, which wouldn't be taken into account by the
> reset API callback and can cause a segmentation fault.
>
> This issue is fixed by allocating the counters size after
> the reinitialization.
>
> Fixes: a4193ae3bc4f ("net/mlx5: support extended statistics")
>
> Reported-by: Ralf Hoffmann <ralf.hoffmann@allegro-packets.com>
> Signed-off-by: Shiri Kuzin <shirik@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
Hi, this does not compile
../drivers/net/mlx5/mlx5_stats.c: In function ‘mlx5_xstats_reset’:
../drivers/net/mlx5/mlx5_stats.c:493:10: warning: ‘return’ with a value,
in function returning void [-Wreturn-type]
493 | return -rte_errno;
../drivers/net/mlx5/mlx5_stats.c:470:1: note: declared here
470 | mlx5_xstats_reset(struct rte_eth_dev *dev)
| ^~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_stats.c:500:10: warning: ‘return’ with a value,
in function returning void [-Wreturn-type]
500 | return ret;
| ^~~
../drivers/net/mlx5/mlx5_stats.c:470:1: note: declared here
470 | mlx5_xstats_reset(struct rte_eth_dev *dev)
| ^~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_stats.c:504:14: error: ‘struct
mlx5_xstats_ctrl’ has no member named ‘hw_stats’
504 | xstats_ctrl->hw_stats[i] = 0;
| ^~
../drivers/net/mlx5/mlx5_stats.c:507:9: warning: ‘return’ with a value,
in function returning void [-Wreturn-type]
507 | return 0;
| ^
../drivers/net/mlx5/mlx5_stats.c:470:1: note: declared here
470 | mlx5_xstats_reset(struct rte_eth_dev *dev)
| ^~~~~~~~~~~~~~~~~
[9/623] Compiling C object
drivers/libtmp_rte_pmd_mlx5.a.p/net_mlx5_mlx5_rxtx_vec.c.o
> drivers/net/mlx5/mlx5_stats.c | 20 ++++++++++++++++----
> 1 file changed, 16 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/mlx5/mlx5_stats.c b/drivers/net/mlx5/mlx5_stats.c
> index 6906dc81cc..38a2ffba4a 100644
> --- a/drivers/net/mlx5/mlx5_stats.c
> +++ b/drivers/net/mlx5/mlx5_stats.c
> @@ -473,8 +473,7 @@ mlx5_xstats_reset(struct rte_eth_dev *dev)
> struct mlx5_xstats_ctrl *xstats_ctrl = &priv->xstats_ctrl;
> int stats_n;
> unsigned int i;
> - unsigned int n = xstats_ctrl->mlx5_stats_n;
> - uint64_t counters[n];
> + uint64_t *counters;
> int ret;
>
> stats_n = mlx5_ethtool_get_stats_n(dev);
> @@ -485,14 +484,27 @@ mlx5_xstats_reset(struct rte_eth_dev *dev)
> }
> if (xstats_ctrl->stats_n != stats_n)
> mlx5_stats_init(dev);
> + counters = malloc(sizeof(*counters) * xstats_ctrl->mlx5_stats_n);
> + if (!counters) {
> + DRV_LOG(WARNING, "port %u unable to allocate memory for xstats "
> + "counters",
> + dev->data->port_id);
> + rte_errno = ENOMEM;
> + return -rte_errno;
> + }
> ret = mlx5_read_dev_counters(dev, counters);
> if (ret) {
> DRV_LOG(ERR, "port %u cannot read device counters: %s",
> dev->data->port_id, strerror(rte_errno));
> - return;
> + free(counters);
> + return ret;
> }
> - for (i = 0; i != n; ++i)
> + for (i = 0; i != xstats_ctrl->mlx5_stats_n; ++i) {
> xstats_ctrl->base[i] = counters[i];
> + xstats_ctrl->hw_stats[i] = 0;
> + }
> + free(counters);
> + return 0;
> }
>
> /**
>
next prev parent reply other threads:[~2020-12-08 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 7:54 Shiri Kuzin
2020-12-08 10:37 ` Kevin Traynor [this message]
2020-12-08 12:28 Viacheslav Ovsiienko
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=911a1e57-b54a-1727-4901-431936ead2a9@redhat.com \
--to=ktraynor@redhat.com \
--cc=matan@nvidia.com \
--cc=ralf.hoffmann@allegro-packets.com \
--cc=shirik@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).