From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Chenbo Xia <chenbox@nvidia.com>,
Akhil Goyal <gakhil@marvell.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [PATCH] vhost/crypto: fix build with asserts
Date: Wed, 05 Mar 2025 12:00:21 +0100 [thread overview]
Message-ID: <3718319.PIDvDuAF1L@thomas> (raw)
In-Reply-To: <1353fc1e-588d-4faf-b5b7-548cf83b98f5@redhat.com>
05/03/2025 10:48, Maxime Coquelin:
>
> On 3/5/25 10:43 AM, David Marchand wrote:
> > ../lib/vhost/vhost_crypto.c: In function ‘virtio_crypto_asym_rsa_der_to_xform’:
> > ../lib/vhost/vhost_crypto.c:538:42: warning: comparison of integer expressions
> > of different signedness: ‘long int’ and ‘size_t’ {aka ‘long unsigned int’}
> > [-Wsign-compare]
> > 538 | RTE_ASSERT((tlv + len - &der[0]) == der_len);
> > | ^~
> > ../lib/eal/include/rte_branch_prediction.h:43:45: note: in definition of macro
> > ‘unlikely’
> > 43 | #define unlikely(x) __builtin_expect(!!(x), 0)
> > | ^
> > ../lib/eal/include/rte_debug.h:47:25: note: in expansion of macro ‘RTE_VERIFY’
> > 47 | #define RTE_ASSERT(exp) RTE_VERIFY(exp)
> > | ^~~~~~~~~~
> > ../lib/vhost/vhost_crypto.c:538:9: note: in expansion of macro ‘RTE_ASSERT’
> > 538 | RTE_ASSERT((tlv + len - &der[0]) == der_len);
> > | ^~~~~~~~~~
> >
> > Fixes: d1b484bf1876 ("vhost/crypto: support asymmetric RSA")
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.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 8dd1806a39..3c6c5dc114 100644
> > --- a/lib/vhost/vhost_crypto.c
> > +++ b/lib/vhost/vhost_crypto.c
> > @@ -535,7 +535,7 @@ virtio_crypto_asym_rsa_der_to_xform(uint8_t *der, size_t der_len,
> > xform->rsa.qt.qInv.data = qinv;
> > xform->rsa.qt.qInv.length = qinvlen;
> >
> > - RTE_ASSERT((tlv + len - &der[0]) == der_len);
> > + RTE_ASSERT(tlv + len == der + der_len);
> > return 0;
> > }
> >
>
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Applied, thanks.
next prev parent reply other threads:[~2025-03-05 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 9:43 [PATCH] vhost/crypto: fix build with asserts David Marchand
2025-03-05 9:48 ` Maxime Coquelin
2025-03-05 11:00 ` Thomas Monjalon [this message]
2025-03-05 9:54 ` [EXTERNAL] " Gowrishankar Muthukrishnan
2025-03-05 10:43 ` Ali Alnubani
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=3718319.PIDvDuAF1L@thomas \
--to=thomas@monjalon.net \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=gmuthukrishn@marvell.com \
--cc=maxime.coquelin@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.