From: Jerin Jacob <jerinjacobk@gmail.com>
To: Abdullah Sevincer <abdullah.sevincer@intel.com>
Cc: dev@dpdk.org, jerinj@marvell.com, pbhagavatula@marvell.com,
stable@dpdk.org
Subject: Re: [PATCH v1] eventdev: fix invalid memory free operation
Date: Fri, 3 Mar 2023 21:25:00 +0530 [thread overview]
Message-ID: <CALBAE1Pz_M2UxnK3SYvF2mRu0+onzAe-axxXT-5VT=NJtOONxw@mail.gmail.com> (raw)
In-Reply-To: <20230228213123.371897-1-abdullah.sevincer@intel.com>
On Wed, Mar 1, 2023 at 3:01 AM Abdullah Sevincer
<abdullah.sevincer@intel.com> wrote:
>
> This commit fixes invalid memory free operation
> caused by extending xstats ID width from 32 to 64 bits.
>
> Telemetry application crashed when freeing memory,
> hence, the telemetry app could not display xstats.
>
> Fixes: 1bdfe4d76e98 ("eventdev: increase xstats ID width to 64 bits")
> Cc: stable@dpdk.org
>
> Signed-off-by: Abdullah Sevincer <abdullah.sevincer@intel.com>
Looks good to me.
Acked-by: Jerin Jacob <jerinj@marvell.com>
Updated the git commit as follows and applied to
dpdk-next-net-eventdev/for-main. Thanks
eventdev: fix invalid memory free operation
Fixe the invalid memory free operation caused by extending
xstats ID width from 32 to 64 bits.
Telemetry application crashed when freeing memory,
hence, the telemetry app could not display xstats.
Fixes: 1bdfe4d76e98 ("eventdev: increase xstats ID width to 64 bits")
Cc: stable@dpdk.org
Signed-off-by: Abdullah Sevincer <abdullah.sevincer@intel.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
> ---
> lib/eventdev/rte_eventdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/eventdev/rte_eventdev.c b/lib/eventdev/rte_eventdev.c
> index 71a29f3506..6ab4524332 100644
> --- a/lib/eventdev/rte_eventdev.c
> +++ b/lib/eventdev/rte_eventdev.c
> @@ -1725,7 +1725,7 @@ eventdev_build_telemetry_data(int dev_id,
> if (xstat_names == NULL)
> return -1;
>
> - ids = malloc((sizeof(unsigned int)) * num_xstats);
> + ids = malloc((sizeof(uint64_t)) * num_xstats);
> if (ids == NULL) {
> free(xstat_names);
> return -1;
> --
> 2.25.1
>
prev parent reply other threads:[~2023-03-03 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 21:31 Abdullah Sevincer
2023-03-03 15:55 ` Jerin Jacob [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='CALBAE1Pz_M2UxnK3SYvF2mRu0+onzAe-axxXT-5VT=NJtOONxw@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=abdullah.sevincer@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.com \
--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).