public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/8] Avoid running cppcheck on system headers
Date: Fri, 8 Nov 2024 10:58:05 +1100	[thread overview]
Message-ID: <Zy1UDZfPbH0cD_2d@zatzit> (raw)
In-Reply-To: <20241107155516.37ce6d1f@elisabeth>

[-- Attachment #1: Type: text/plain, Size: 2067 bytes --]

On Thu, Nov 07, 2024 at 03:55:16PM +0100, Stefano Brivio wrote:
> On Wed,  6 Nov 2024 17:54:13 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > It turns out cppcheck has inbuilt knowledge of the C library, and
> > isn't typically given the system headers.  Avoiding doing so reduces
> > the runtime to less than half of what it currently is.
> > 
> > For non-obvious reasons, this change also exposes some new warnings.
> > Some are real, one is a cppcheck bug.  Fix and/or workaround these
> > then make the change to the cppcheck options.
> > 
> > This is based on my earlier series with clangd configuration and
> > fixes.
> > 
> > David Gibson (8):
> >   linux_dep: Generalise tcp_info.h to handling Linux extension
> >     compatibility
> >   log: Only check for FALLOC_FL_COLLAPSE_RANGE availability at runtime
> >   linux_dep: Move close_range() conditional handling to linux_dep.h
> >   linux_dep: Fix CLOSE_RANGE_UNSHARE availability handling
> >   ndp: Use const pointer for ndp_ns packet
> >   udp: Don't dereference uflow before NULL check in
> >     udp_reply_sock_handler()
> >   util: Work around cppcheck bug 6936
> >   cppcheck: Don't check the system headers
> 
> Applied, except for 2/8, 3/8, 4/8, and 8/8.
> 
> I had to skip 8/8 as well for the moment because, contrary to what I
> reported earlier by mistake, it's actually the one leading to the new
> cppcheck warning:
> 
> dhcpv6.c:334:14: style: The comparison 'ia_type == 3' is always true. [knownConditionTrueFalse]
>  if (ia_type == OPT_IA_NA) {
> 
> ...also on x86. The difference is not the architecture, rather the
> cppcheck version: it happens with 2.16.x but not with 2.14.x.
> 
> I'm posting a patch for that soon.

Oh, interesting.  8/8 exposed several new warnings for me too (hence
most of this series), but not that one.

-- 
David Gibson (he or they)	| 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 --]

      reply	other threads:[~2024-11-08  2:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  6:54 [PATCH 0/8] Avoid running cppcheck on system headers David Gibson
2024-11-06  6:54 ` [PATCH 1/8] linux_dep: Generalise tcp_info.h to handling Linux extension compatibility David Gibson
2024-11-06  6:54 ` [PATCH 2/8] log: Only check for FALLOC_FL_COLLAPSE_RANGE availability at runtime David Gibson
2024-11-06 19:10   ` Stefano Brivio
2024-11-06 20:54     ` David Gibson
2024-11-06  6:54 ` [PATCH 3/8] linux_dep: Move close_range() conditional handling to linux_dep.h David Gibson
2024-11-06 19:10   ` Stefano Brivio
2024-11-06 20:56     ` David Gibson
2024-11-06  6:54 ` [PATCH 4/8] linux_dep: Fix CLOSE_RANGE_UNSHARE availability handling David Gibson
2024-11-06 19:12   ` Stefano Brivio
2024-11-06 21:01     ` David Gibson
2024-11-07  7:03       ` Stefano Brivio
2024-11-06  6:54 ` [PATCH 5/8] ndp: Use const pointer for ndp_ns packet David Gibson
2024-11-06  6:54 ` [PATCH 6/8] udp: Don't dereference uflow before NULL check in udp_reply_sock_handler() David Gibson
2024-11-06  6:54 ` [PATCH 7/8] util: Work around cppcheck bug 6936 David Gibson
2024-11-06  6:54 ` [PATCH 8/8] cppcheck: Don't check the system headers David Gibson
2024-11-07 14:55 ` [PATCH 0/8] Avoid running cppcheck on " Stefano Brivio
2024-11-07 23:58   ` 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=Zy1UDZfPbH0cD_2d@zatzit \
    --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).