public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Subject: Re: [PATCH] tcp_vu: Change 'dlen' to ssize_t in tcp_vu_data_from_sock()
Date: Wed, 27 Nov 2024 15:59:48 +0100	[thread overview]
Message-ID: <14f5881a-8431-4b02-8028-f1bf4fb2f77c@redhat.com> (raw)
In-Reply-To: <20241127144327.3778810-1-sbrivio@redhat.com>

On 27/11/2024 15:43, Stefano Brivio wrote:
> ...to quickly suppress a false positive from Coverity, which assumes
> that iov_size is 0 and 'dlen' might overflow as a result (with hdrlen
> being 66). An ASSERT() in tcp_vu_sock_recv() already guarantees that
> iov_size(iov, buf_cnt) here is anyway greater than 'hdrlen'.
> 
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> ---
> This applies on top of "[PATCH] Fix build on 32bit target"
> 
>   tcp_vu.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tcp_vu.c b/tcp_vu.c
> index 05e2d1d..a1510d9 100644
> --- a/tcp_vu.c
> +++ b/tcp_vu.c
> @@ -462,7 +462,7 @@ int tcp_vu_data_from_sock(const struct ctx *c, struct tcp_tap_conn *conn)
>   	for (i = 0, check = NULL; i < head_cnt; i++) {
>   		struct iovec *iov = &elem[head[i]].in_sg[0];
>   		int buf_cnt = head[i + 1] - head[i];
> -		int dlen = iov_size(iov, buf_cnt) - hdrlen;
> +		ssize_t dlen = iov_size(iov, buf_cnt) - hdrlen;
>   
>   		vu_set_vnethdr(vdev, iov->iov_base, buf_cnt);
>   

Reviewed-by: Laurent Vivier <lvivier@redhat.com>


      reply	other threads:[~2024-11-27 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 14:43 [PATCH] tcp_vu: Change 'dlen' to ssize_t in tcp_vu_data_from_sock() Stefano Brivio
2024-11-27 14:59 ` Laurent Vivier [this message]

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=14f5881a-8431-4b02-8028-f1bf4fb2f77c@redhat.com \
    --to=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).