From: Jerin Jacob <jerinjacobk@gmail.com>
To: 835703180@qq.com
Cc: harry.van.haaren@intel.com, dev@dpdk.org
Subject: Re: [PATCH] examples/eventdev: Check for the NULL pointer after calling rte_zmalloc
Date: Tue, 13 Sep 2022 17:47:50 +0530 [thread overview]
Message-ID: <CALBAE1MKdZ9gxz54Mhvxb7QtJtws-KMTCgwVcKKwv4n3ObA5oA@mail.gmail.com> (raw)
In-Reply-To: <tencent_E049786768575AD04105555B3D3730A17B0A@qq.com>
On Wed, Jul 6, 2022 at 12:54 PM <835703180@qq.com> wrote:
>
> From: Shiqi Liu <835703180@qq.com>
>
> As the possible failure of the rte_zmalloc(), the not_checked and
> checked could be NULL pointer.
> Therefore, it should be better to check it in order to avoid
> the dereference of the NULL pointer.
>
> Fixes: fa8054c8c88 ("examples/eventdev: add thread safe Tx worker pipeline")
> Signed-off-by: Shiqi Liu <835703180@qq.com>
> ---
> examples/eventdev_pipeline/pipeline_worker_tx.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/examples/eventdev_pipeline/pipeline_worker_tx.c b/examples/eventdev_pipeline/pipeline_worker_tx.c
> index a82e064c1c..6ea676c516 100644
> --- a/examples/eventdev_pipeline/pipeline_worker_tx.c
> +++ b/examples/eventdev_pipeline/pipeline_worker_tx.c
> @@ -764,7 +764,9 @@ init_adapters(uint16_t nb_ports)
>
> ret = rte_event_dev_info_get(evdev_id, &dev_info);
> adptr_services = rte_zmalloc(NULL, sizeof(struct rx_adptr_services), 0);
> -
> + if (adptr_services == NULL) {
> + return -ENOMEM;
> + }
it does not look like you have tried to compile this patch. It is a
void return function.
CI: http://mails.dpdk.org/archives/test-report/2022-July/294780.html
Also, Please update the subject. Some suggestion to consider.
examples/eventdev: validate memory allocation
> struct rte_event_port_conf adptr_p_conf = {
> .dequeue_depth = cdata.worker_cq_depth,
> .enqueue_depth = 64,
> --
> 2.35.1.windows.2
>
prev parent reply other threads:[~2022-09-13 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 7:23 835703180
2022-09-13 12:17 ` 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=CALBAE1MKdZ9gxz54Mhvxb7QtJtws-KMTCgwVcKKwv4n3ObA5oA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=835703180@qq.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.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).