From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"shally.verma@caviumnetworks.com"
<shally.verma@caviumnetworks.com>,
Sunila Sahu <ssahu@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] compress/zlib: fix coverity warning
Date: Thu, 25 Jul 2019 13:14:40 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435897D0682@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20190724084246.5768-1-adamx.dybkowski@intel.com>
Including Sunila, the zlib PMD maintainer.
> -----Original Message-----
> From: Dybkowski, AdamX
> Sent: Wednesday, July 24, 2019 9:43 AM
> To: dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>; shally.verma@caviumnetworks.com
> Cc: Dybkowski, AdamX <adamx.dybkowski@intel.com>
> Subject: [PATCH] compress/zlib: fix coverity warning
>
> Add missing return after setting the error status in case of
> invalid flush_flag in the operation.
> The issue was found by the coverity scan as the fin_flush variable,
> not initialized in such case, was used later in the flow.
>
> CID 340859: Uninitialized variables (UNINIT)
>
> Fixes: c7b436ec95fd ("compress/zlib: support burst enqueue/dequeue")
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> ---
> drivers/compress/zlib/zlib_pmd.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/compress/zlib/zlib_pmd.c b/drivers/compress/zlib/zlib_pmd.c
> index 5a4d47d4d..19f9200c2 100644
> --- a/drivers/compress/zlib/zlib_pmd.c
> +++ b/drivers/compress/zlib/zlib_pmd.c
> @@ -30,6 +30,7 @@ process_zlib_deflate(struct rte_comp_op *op, z_stream *strm)
> default:
> op->status = RTE_COMP_OP_STATUS_INVALID_ARGS;
> ZLIB_PMD_ERR("Invalid flush value\n");
> + return;
> }
>
> if (unlikely(!strm)) {
> --
> 2.17.1
next prev parent reply other threads:[~2019-07-25 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 8:42 Adam Dybkowski
2019-07-25 13:14 ` Trahe, Fiona [this message]
2019-07-26 13:59 ` Akhil Goyal
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=348A99DA5F5B7549AA880327E580B435897D0682@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=adamx.dybkowski@intel.com \
--cc=dev@dpdk.org \
--cc=shally.verma@caviumnetworks.com \
--cc=ssahu@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).