From: Stephen Hemminger <stephen@networkplumber.org>
To: lee.daly@intel.com
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH] compress/isal: fix use after free
Date: Tue, 21 May 2019 07:47:13 -0700 [thread overview]
Message-ID: <20190521144713.12046-1-stephen@networkplumber.org> (raw)
The release function was using qp->stream after already
releasing it and the null pointer checking was missing.
Also since rte_free(NULL) is a no-op, remove unnecessary
checks for NULL.
Coverity issure: 340860
Fixes: dc49e6aa4879 ("compress/isal: add ISA-L compression functionality")
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
drivers/compress/isal/isal_compress_pmd_ops.c | 14 ++++----------
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/drivers/compress/isal/isal_compress_pmd_ops.c b/drivers/compress/isal/isal_compress_pmd_ops.c
index fe9995992304..77ac6fcf21fc 100644
--- a/drivers/compress/isal/isal_compress_pmd_ops.c
+++ b/drivers/compress/isal/isal_compress_pmd_ops.c
@@ -171,18 +171,12 @@ isal_comp_pmd_qp_release(struct rte_compressdev *dev, uint16_t qp_id)
if (qp == NULL)
return -EINVAL;
- if (qp->stream != NULL)
- rte_free(qp->stream);
-
- if (qp->stream->level_buf != NULL)
+ if (qp->stream)
rte_free(qp->stream->level_buf);
- if (qp->state != NULL)
- rte_free(qp->state);
-
- if (qp->processed_pkts != NULL)
- rte_ring_free(qp->processed_pkts);
-
+ rte_free(qp->state);
+ rte_ring_free(qp->processed_pkts);
+ rte_free(qp->stream);
rte_free(qp);
dev->data->queue_pairs[qp_id] = NULL;
--
2.20.1
next reply other threads:[~2019-05-21 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 14:47 Stephen Hemminger [this message]
2019-05-21 15:07 ` Daly, Lee
2019-05-27 16:00 ` Trahe, Fiona
2019-06-19 14:54 ` 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=20190521144713.12046-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=lee.daly@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).