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: Fri, 16 May 2025 17:25:21 +1000 [thread overview]
Message-ID: <aCboYaNInbWICwOR@zatzit> (raw)
In-Reply-To: <20250515160501.2636220-1-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
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.
> ---
> tap.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tap.c b/tap.c
> index d630f6d..6db5d88 100644
> --- a/tap.c
> +++ b/tap.c
> @@ -118,6 +118,8 @@ unsigned long tap_l2_max_len(const struct ctx *c)
> }
> /* NOLINTEND(bugprone-branch-clone) */
> ASSERT(0);
> +
> + return 0; /* Unreachable, for cppcheck's sake */
> }
>
> /**
--
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-16 9: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 [this message]
2025-05-16 16:26 ` Stefano Brivio
2025-05-17 10:29 ` David Gibson
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=aCboYaNInbWICwOR@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).