From: Akhil Goyal <akhil.goyal@nxp.com>
To: Gagandeep Singh <G.Singh@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/caam_jr: fix memory leak and illegal memory access
Date: Tue, 16 Apr 2019 13:47:29 +0000 [thread overview]
Message-ID: <VI1PR04MB4893EEA1F37E18F273192030E6240@VI1PR04MB4893.eurprd04.prod.outlook.com> (raw)
Message-ID: <20190416134729.UmRHvp928oWp_bHh8pE_QjdjZ8eWQXFfPuhXb1uP-KA@z> (raw)
In-Reply-To: <1554813675-13955-1-git-send-email-g.singh@nxp.com>
> Opendir() returns allocated storage which must be freed at the
> end of function or in case any return on error. so freeing the
> allocation using closedir in an error case.
>
> Coverity issue: 323507
> Coverity issue: 325880
> Fixes: e7a45f3cc245 ("crypto/caam_jr: add UIO specific operations")
> Cc: g.singh@nxp.com
>
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
> ---
> drivers/crypto/caam_jr/caam_jr_uio.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
next prev parent reply other threads:[~2019-04-16 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 6:18 Gagandeep Singh
2019-04-09 6:18 ` Gagandeep Singh
2019-04-16 13:47 ` Akhil Goyal [this message]
2019-04-16 13:47 ` Akhil Goyal
2019-04-16 14:51 ` Akhil Goyal
2019-04-16 14:51 ` 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=VI1PR04MB4893EEA1F37E18F273192030E6240@VI1PR04MB4893.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=G.Singh@nxp.com \
--cc=dev@dpdk.org \
/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).