DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Ankur Dwivedi <adwivedi@marvell.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: alialnu@nvidia.com, jerinj@marvell.com, dev@dpdk.org,
	David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH v1] ethdev: remove bitfields from trace
Date: Tue, 28 Feb 2023 16:29:20 +0000	[thread overview]
Message-ID: <bb4e583b-402b-f701-f2cd-a8d27600146d@amd.com> (raw)
In-Reply-To: <20230228155516.2403535-1-adwivedi@marvell.com>

On 2/28/2023 3:55 PM, Ankur Dwivedi wrote:
> 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>

Reviewed-by: Ferruh Yigit <ferruh.yigit@amd.com>


@Thomas, do you want to get this fix to main repo, since it cause crash
and getting from next-net can increase merge time.

  reply	other threads:[~2023-02-28 16:29 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 [this message]
2023-03-01 15:59   ` Thomas Monjalon
2023-02-28 17:37 ` Ali Alnubani

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=bb4e583b-402b-f701-f2cd-a8d27600146d@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=adwivedi@marvell.com \
    --cc=alialnu@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=thomas@monjalon.net \
    /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).