From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] util: In ASSERT(), use "fprintf(stderr, ...)" rather than err(...)
Date: Tue, 6 Aug 2024 10:27:11 +1000 [thread overview]
Message-ID: <ZrFt36YqPcq3LXL9@zatzit.fritz.box> (raw)
In-Reply-To: <20240805141027.1502569-1-lvivier@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]
On Mon, Aug 05, 2024 at 04:10:27PM +0200, Laurent Vivier wrote:
> We use our own implementation of assert() because the glic implementation
> uses syscalls that aren't in our seccomp filter, see 7a8ed9459dfe
> ("Make assertions actually useful"). And we replaced it by an err(),
> followed by an abort() (that is also catched by seccomp).
I think Stefano's said everything I would on the change itself, but..
> We don't have a coredump or a backtrace but we have at least the
> error message... only if logging is enabled.
Whether we get a coredump shouldn't be affected by our weird ASSERT()
here. If coredumps are enabled (which they're not by default on
current distros, AFAICT), we should still get a coredump with the
SIGSYS here, just as we would for a SIGABRT.
> As this kind of information is needed in any case, replace the "err()"
> function by an "fprintf(stderr, ...)".
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> util.h | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/util.h b/util.h
> index b7541ce24e5a..b44b4bfdccd7 100644
> --- a/util.h
> +++ b/util.h
> @@ -13,6 +13,7 @@
> #include <stdint.h>
> #include <string.h>
> #include <signal.h>
> +#include <stdio.h>
> #include <arpa/inet.h>
>
> #include "log.h"
> @@ -67,8 +68,10 @@
> #define ASSERT(expr) \
> do { \
> if (!(expr)) { \
> - err("ASSERTION FAILED in %s (%s:%d): %s", \
> - __func__, __FILE__, __LINE__, STRINGIFY(expr)); \
> + fprintf(stderr, \
> + "ASSERTION FAILED in %s (%s:%d): %s\n", \
> + __func__, __FILE__, __LINE__, \
> + STRINGIFY(expr)); \
> /* This may actually SIGSYS, due to seccomp, \
> * but that will still get the job done \
> */ \
--
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:[~2024-08-06 0:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 14:10 [PATCH] util: In ASSERT(), use "fprintf(stderr, ...)" rather than err(...) Laurent Vivier
2024-08-05 14:34 ` Stefano Brivio
2024-08-05 15:52 ` Laurent Vivier
2024-08-05 16:12 ` Stefano Brivio
2024-08-06 0:27 ` David Gibson [this message]
2024-08-06 9:27 ` Laurent Vivier
2024-08-06 11:43 ` Stefano Brivio
2024-08-06 12:28 ` David Gibson
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=ZrFt36YqPcq3LXL9@zatzit.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
/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).