From: Ali Alnubani <alialnu@nvidia.com>
To: Ankur Dwivedi <adwivedi@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "jerinj@marvell.com" <jerinj@marvell.com>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>
Subject: RE: [PATCH v1] ethdev: remove bitfields from trace
Date: Tue, 28 Feb 2023 17:37:10 +0000 [thread overview]
Message-ID: <DM4PR12MB5167D5159BCE67ADFCD41936DAAC9@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230228155516.2403535-1-adwivedi@marvell.com>
> -----Original Message-----
> From: Ankur Dwivedi <adwivedi@marvell.com>
> Sent: Tuesday, February 28, 2023 5:55 PM
> To: dev@dpdk.org
> Cc: Ali Alnubani <alialnu@nvidia.com>; jerinj@marvell.com;
> ferruh.yigit@amd.com; Ankur Dwivedi <adwivedi@marvell.com>
> Subject: [PATCH v1] ethdev: remove bitfields from trace
>
> To capture bitfield variables in trace, the pointer to the structure
> containing the bitfields was referenced. But during trace point
> registration the pointer contains invalid address. Referencing this
> invalid address causes segmentation fault.
>
> This patch removes the capture of bitfield variables in trace.
>
> Bugzilla ID: 1167
> Fixes: 6679cf21d608 ("ethdev: add trace points")
> Fixes: ed04fd4072e9 ("ethdev: add trace points for flow")
>
> Signed-off-by: Ankur Dwivedi <adwivedi@marvell.com>
> ---
Thanks Ankur.
Tested-by: Ali Alnubani <alialnu@nvidia.com>
prev parent reply other threads:[~2023-02-28 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 15:55 Ankur Dwivedi
2023-02-28 16:29 ` Ferruh Yigit
2023-03-01 15:59 ` Thomas Monjalon
2023-02-28 17:37 ` Ali Alnubani [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=DM4PR12MB5167D5159BCE67ADFCD41936DAAC9@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=adwivedi@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jerinj@marvell.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).