From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
dev@dpdk.org, Chenbo Xia <chenbox@nvidia.com>,
Akhil Goyal <gakhil@marvell.com>
Cc: anoobj@marvell.com
Subject: Re: [PATCH] vhost/crypto: fix uninitialized variable
Date: Fri, 16 May 2025 15:43:20 +0200 [thread overview]
Message-ID: <84657ae7-d811-4019-a8f9-e781c87710e7@redhat.com> (raw)
In-Reply-To: <20250515081004.1742-1-gmuthukrishn@marvell.com>
On 5/15/25 10:10 AM, Gowrishankar Muthukrishnan wrote:
> Fix uninitialized variable as reported in coverity scan.
>
> Coverity-issue: 457449
> Fixes: d1b484bf187 ("vhost/crypto: support asymmetric RSA")
>
> Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> ---
> lib/vhost/vhost_crypto.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/vhost/vhost_crypto.c b/lib/vhost/vhost_crypto.c
> index f78daf98d1..66ba5342e2 100644
> --- a/lib/vhost/vhost_crypto.c
> +++ b/lib/vhost/vhost_crypto.c
> @@ -1493,10 +1493,10 @@ vhost_crypto_process_one_req(struct vhost_crypto *vcrypto,
> struct vhost_crypto_data_req *vc_req, *vc_req_out;
> struct rte_cryptodev_asym_session *asym_session;
> struct rte_cryptodev_sym_session *sym_session;
> + struct vhost_crypto_data_req data_req = {0};
> struct vhost_crypto_session *vhost_session;
> struct vhost_crypto_desc *desc = descs;
> uint32_t nb_descs = 0, max_n_descs, i;
> - struct vhost_crypto_data_req data_req;
> struct virtio_crypto_op_data_req req;
> struct virtio_crypto_inhdr *inhdr;
> struct vring_desc *src_desc;
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2025-05-16 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 8:10 Gowrishankar Muthukrishnan
2025-05-16 13:43 ` Maxime Coquelin [this message]
2025-05-16 14:12 ` Maxime Coquelin
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=84657ae7-d811-4019-a8f9-e781c87710e7@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=anoobj@marvell.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=gmuthukrishn@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).