From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Ankur Dwivedi <adwivedi@marvell.com>, dev@dpdk.org
Cc: jerinj@marvell.com
Subject: Re: [PATCH v1 1/2] ethdev: fix null pointer dereference
Date: Tue, 28 Feb 2023 15:01:05 +0000 [thread overview]
Message-ID: <5b714a8e-1851-d204-18bc-6fe9cd5d5afd@amd.com> (raw)
In-Reply-To: <20230223123029.2117781-2-adwivedi@marvell.com>
On 2/23/2023 12:30 PM, Ankur Dwivedi wrote:
> The speed_fec_capa pointer can be null. So dereferencing the pointer is
> removed and only the pointer is captured in trace function.
> Fixed few more trace functions in which null pointer can be dereferenced.
>
> Coverity issue: 383238
> Bugzilla ID: 1162
> Fixes: 6679cf21d608 ("ethdev: add trace points")
> Fixes: ed04fd4072e9 ("ethdev: add trace points for flow")
>
In below changes, pointers can be NULL at runtime, so agree on to the
change, with minor comments please see below.
But I don't think this is a fix for Bug 1162, which is an ASan reported
error, can you please drop that tag unless it is verified.
<...>
> @@ -2308,8 +2300,7 @@ RTE_TRACE_POINT_FP(
> int ret),
> rte_trace_point_emit_u16(port_id);
> rte_trace_point_emit_ptr(flow);
> - rte_trace_point_emit_int(action->type);
> - rte_trace_point_emit_ptr(action->conf);
> + rte_trace_point_emit_ptr(action);
> rte_trace_point_emit_ptr(data);
> rte_trace_point_emit_int(ret);
I think 'rte_flow_trace_create()' is missed, rest looks OK.
Can you please double check 'rte_flow_trace_create()' too?
> )
> @@ -2349,14 +2340,8 @@ RTE_TRACE_POINT_FP(
> const struct rte_flow_indir_action_conf *conf,
> const struct rte_flow_action *action,
> const struct rte_flow_action_handle *handle),
> - uint8_t ingress = conf->ingress;
> - uint8_t egress = conf->egress;
> - uint8_t transfer = conf->transfer;
> -
> rte_trace_point_emit_u16(port_id);
> - rte_trace_point_emit_u8(ingress);
> - rte_trace_point_emit_u8(egress);
> - rte_trace_point_emit_u8(transfer);
> + rte_trace_point_emit_ptr(conf);
> rte_trace_point_emit_ptr(action);
> rte_trace_point_emit_ptr(handle);
> )
This change is different than others, this is removing bitfield related
local variable assignment.
According to bug 1167 that is causing a crash. So we need a separate
patch to either remove or fix bitfield related issues, for now I am OK
to remove (as done above).
But can you please make another patch for bitfield issue and move above
change to that patch?
Thanks,
ferruh
next prev parent reply other threads:[~2023-02-28 15:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 12:30 [PATCH v1 0/2] bug fix in ethdev trace Ankur Dwivedi
2023-02-23 12:30 ` [PATCH v1 1/2] ethdev: fix null pointer dereference Ankur Dwivedi
2023-02-28 11:04 ` Ferruh Yigit
2023-02-28 11:29 ` David Marchand
2023-02-28 12:46 ` Ferruh Yigit
2023-02-28 13:17 ` Jerin Jacob
2023-02-28 13:39 ` Ferruh Yigit
2023-02-28 15:01 ` Ferruh Yigit [this message]
2023-02-28 15:40 ` [EXT] " Ankur Dwivedi
2023-02-28 16:08 ` Ferruh Yigit
2023-02-28 16:27 ` Ferruh Yigit
2023-03-02 9:58 ` Ferruh Yigit
2023-03-02 16:49 ` Ankur Dwivedi
2023-02-23 12:30 ` [PATCH v1 2/2] ethdev: pass structure pointer Ankur Dwivedi
2023-02-28 15:01 ` Ferruh Yigit
2023-03-03 11:31 ` [PATCH v2 0/2] bug fix in ethdev trace Ankur Dwivedi
2023-03-03 11:31 ` [PATCH v2 1/2] ethdev: fix null pointer dereference Ankur Dwivedi
2023-03-03 13:38 ` Ferruh Yigit
2023-03-03 11:31 ` [PATCH v2 2/2] ethdev: pass structure pointer Ankur Dwivedi
2023-03-03 13:39 ` [PATCH v2 0/2] bug fix in ethdev trace Ferruh Yigit
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=5b714a8e-1851-d204-18bc-6fe9cd5d5afd@amd.com \
--to=ferruh.yigit@amd.com \
--cc=adwivedi@marvell.com \
--cc=dev@dpdk.org \
--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).