public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/4] RFC: Updates for cppcheck-2.12 warnings
Date: Fri, 29 Sep 2023 15:50:18 +1000	[thread overview]
Message-ID: <20230929055022.48624-1-david@gibson.dropbear.id.au> (raw)

cppcheck 2.12 (which Fedora 38 has updated, for one) introduces a
number of new warnings.  Unfortunately, at least one of these is a
clear bug in cppcheck.

This series fixes a number of the new warnings reported in passt
(patches 1..3) and works around the remaining cppcheck bug (patch 4).
I'm pretty confident that patches 1 & 2 are safe and beneficial to
apply regardless of which cppcheck we're using.

Patch 3 is a little more dubious, because it potentially increases the
cppcheck runtime.  On my system it doesn't seem to make a significant
difference, but that might not always stay true.

Patch 4 is a tricky one.  It applies a specific suppression to work
around the cppcheck bug.  That's necessary to get a pass with the
currently available cppcheck.  However, it's ugly and we'd like to
remove it once the bug is fixed, but have no obvious way to remind us
to do that.  What we want to do here kind of depends how long it takes
the bug to be fixed, which isn't clear at the moment.

David Gibson (4):
  cppcheck: Make many pointers const
  conf: Remove overly cryptic selection of forward table
  cppcheck: Use "exhaustive" level checking when available
  cppcheck: Work around bug in cppcheck 2.12.0

 Makefile     |  6 ++++++
 conf.c       | 25 +++++++++++--------------
 isolation.c  |  2 +-
 isolation.h  |  2 +-
 log.c        |  6 +++---
 netlink.c    |  6 +++---
 netlink.h    |  6 +++---
 pasta.c      |  4 ++--
 pasta.h      |  2 +-
 tap.c        | 14 +++++++-------
 tap.h        |  6 +++---
 tcp.c        | 25 ++++++++++++++++---------
 tcp_conn.h   |  2 +-
 tcp_splice.c |  5 +++--
 tcp_splice.h |  3 ++-
 udp.c        |  4 ++--
 udp.h        |  2 +-
 util.c       |  5 +++--
 util.h       |  4 ++--
 19 files changed, 71 insertions(+), 58 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-09-29  5:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29  5:50 David Gibson [this message]
2023-09-29  5:50 ` [PATCH 1/4] cppcheck: Make many pointers const David Gibson
2023-09-29  5:50 ` [PATCH 2/4] conf: Remove overly cryptic selection of forward table David Gibson
2023-09-29  5:50 ` [PATCH 3/4] cppcheck: Use "exhaustive" level checking when available David Gibson
2023-09-29  5:50 ` [PATCH 4/4] cppcheck: Work around bug in cppcheck 2.12.0 David Gibson
2023-09-29  5:52 ` [PATCH 0/4] RFC: Updates for cppcheck-2.12 warnings David Gibson
2023-09-29 15:31 ` Stefano Brivio
2023-10-03  2:36   ` David Gibson
2023-10-05  6:19     ` Stefano Brivio

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=20230929055022.48624-1-david@gibson.dropbear.id.au \
    --to=david@gibson.dropbear.id.au \
    --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).