From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] tap: Avoid bogus missingReturn cppcheck warning in tap_l2_max_len()
Date: Sat, 17 May 2025 20:29:20 +1000 [thread overview]
Message-ID: <aChlAFK8kJ8OqUxV@zatzit> (raw)
In-Reply-To: <20250516182623.69e49c29@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]
On Fri, May 16, 2025 at 06:26:23PM +0200, Stefano Brivio wrote:
> On Fri, 16 May 2025 17:25:21 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > On Thu, May 15, 2025 at 06:05:01PM +0200, Stefano Brivio wrote:
> > > Cppcheck 2.14.2 on Alpine Linux (musl) says that:
> > >
> > > tap.c:111:19: error: Found an exit path from function with non-void return type that has missing return statement [missingReturn]
> > > switch (c->mode) {
> > > ^
> > >
> > > This exit path is not reachable because we ASSERT(0) after the switch,
> > > but for some reason cppcheck doesn't see this with musl headers. Hide
> > > the warning with a redundant return statement.
> > >
> > > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> >
> > Hm. Alternatively you could change this to call abort_with_msg()
> > directly. That's marked as ((noreturn)) so with any luck cppcheck
> > will then be able to figure out what's going on. Although, I'm
> > slightly surprised it can't do so already: I thought I put the
> > ((noreturn)) in there to avoid warnings exactly like this.
>
> So, I checked, and abort_with_msg(""); works. ASSERT() ultimately
> expands to abort_with_msg(), but for some reason cppcheck together with
> Clang can't "follow" that, I suppose it's something related to the
> pre-processor.
>
> But in any case, abort_with_msg("") doesn't look as descriptive and
> as obviously redundant as a return statement with a comment, so I don't
> quite see the benefit changing it (also considering that I need to test
> other versions, which takes time).
Well, kind of the whole point of abort_with_msg() is that you can give
it a meaningful message, which might change the picture. It would
also be trivial to write an unreachable() wrapper around that.
--
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 --]
next prev parent reply other threads:[~2025-05-17 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 16:05 [PATCH] tap: Avoid bogus missingReturn cppcheck warning in tap_l2_max_len() Stefano Brivio
2025-05-16 7:25 ` David Gibson
2025-05-16 16:26 ` Stefano Brivio
2025-05-17 10:29 ` David Gibson [this message]
2025-05-19 7:27 ` 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=aChlAFK8kJ8OqUxV@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).