From: Laine Stump <laine@redhat.com>
To: passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>,
Stefano Brivio <sbrivio@redhat.com>
Subject: Re: [PATCH] conf, tap: Silence two false positive invalidFunctionArg from cppcheck
Date: Fri, 17 Feb 2023 09:29:51 -0500 [thread overview]
Message-ID: <71dcfbb0-e317-9e73-fb8d-07955bbcc3c1@redhat.com> (raw)
In-Reply-To: <Y+6z6KTuYUQnIO3m@yekko>
On 2/16/23 5:53 PM, David Gibson wrote:
> On Thu, Feb 16, 2023 at 07:22:10PM +0100, Stefano Brivio wrote:
>> The newly introduced die() calls exit(), but cppcheck doesn't see it
>> and warns about possibly invalid arguments used after the check which
>> triggers die(). Add return statements to silence the warnings.
>>
>> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
>
> Oof, that's super ugly. Any chance that cppcheck will recognize the
> ((noreturn)) attribute if we added it to die()?
Why is this only a problem in these two files?
(and is there a "make check" target that I should have been running and
haven't?)
Requiring an extra "return" after die() kind of removes the advantage of
using it over err(). :-/ If we have to do that, it would be more
straightforward to just use err() followed by exit() directly.
>
>> ---
>> conf.c | 3 +++
>> tap.c | 6 +++++-
>> 2 files changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/conf.c b/conf.c
>> index 675d961..5426c9b 100644
>> --- a/conf.c
>> +++ b/conf.c
>> @@ -1036,6 +1036,9 @@ static void conf_ugid(char *runas, uid_t *uid, gid_t *gid)
>> if ((fd = open("/proc/self/uid_map", O_RDONLY | O_CLOEXEC)) < 0) {
>> die("Can't determine if we're in init namespace: %s",
>> strerror(errno));
>> +
>> + /* Silence cppcheck's invalidFunctionArg for 'fd' in read() */
>> + return;
>> }
>>
>> if (read(fd, buf, BUFSIZ) != sizeof(root_uid_map) ||
>> diff --git a/tap.c b/tap.c
>> index 88eed88..d6f962e 100644
>> --- a/tap.c
>> +++ b/tap.c
>> @@ -1037,9 +1037,13 @@ static void tap_sock_unix_init(struct ctx *c)
>> snprintf(path, UNIX_PATH_MAX - 1, UNIX_SOCK_PATH, i);
>>
>> ex = socket(AF_UNIX, SOCK_STREAM | SOCK_NONBLOCK, 0);
>> - if (ex < 0)
>> + if (ex < 0) {
>> die("UNIX domain socket check: %s", strerror(errno));
>>
>> + /* Silence cppcheck's invalidFunctionArg for 'ex' */
>> + return;
>> + }
>> +
>> ret = connect(ex, (const struct sockaddr *)&addr, sizeof(addr));
>> if (!ret || (errno != ENOENT && errno != ECONNREFUSED &&
>> errno != EACCES)) {
>
next prev parent reply other threads:[~2023-02-17 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 18:22 [PATCH] conf, tap: Silence two false positive invalidFunctionArg from cppcheck Stefano Brivio
2023-02-16 22:53 ` David Gibson
2023-02-17 8:04 ` Stefano Brivio
2023-02-17 9:10 ` David Gibson
2023-02-17 14:29 ` Laine Stump [this message]
2023-02-17 14:37 ` 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=71dcfbb0-e317-9e73-fb8d-07955bbcc3c1@redhat.com \
--to=laine@redhat.com \
--cc=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).