From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: jmaloy@redhat.com
Subject: Re: [PATCH v6] tcp: Make pointer const in tcp_revert_seq
Date: Thu, 6 Jun 2024 12:41:06 +1000 [thread overview]
Message-ID: <ZmEhwtCpxk2X2irz@zatzit> (raw)
In-Reply-To: <20240606020305.4125785-1-david@gibson.dropbear.id.au>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
On Thu, Jun 06, 2024 at 12:03:05PM +1000, David Gibson wrote:
> The th pointer could be const, which causes a cppcheck warning on at least
> some cppcheck versions (e.g. Cppcheck 2.13.0 in Fedora 40).
>
> Fixes: e84a01e94 "tcp: move seq_to_tap update to when frame is queued"
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Heh, then I updated and the new cppcheck found some more errors. I'll
repost this along with the remaining fixes.
> ---
> tcp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tcp.c b/tcp.c
> index 89a5b19a..ff1198dd 100644
> --- a/tcp.c
> +++ b/tcp.c
> @@ -1261,8 +1261,8 @@ static void tcp_revert_seq(struct tcp_tap_conn **conns, struct iovec (*frames)[T
> int i;
>
> for (i = 0; i < num_frames; i++) {
> + const struct tcphdr *th = frames[i][TCP_IOV_PAYLOAD].iov_base;
> struct tcp_tap_conn *conn = conns[i];
> - struct tcphdr *th = frames[i][TCP_IOV_PAYLOAD].iov_base;
> uint32_t seq = ntohl(th->seq);
>
> if (SEQ_LE(conn->seq_to_tap, seq))
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-06-06 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 2:03 [PATCH v6] tcp: Make pointer const in tcp_revert_seq David Gibson
2024-06-06 2:41 ` David Gibson [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=ZmEhwtCpxk2X2irz@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=jmaloy@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).