From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 01/15] treewide: Spell ASSERT() as assert()
Date: Fri, 20 Mar 2026 21:58:41 +0100 (CET) [thread overview]
Message-ID: <20260320215840.155c9f87@elisabeth> (raw)
In-Reply-To: <20260319061157.1983818-2-david@gibson.dropbear.id.au>
On Thu, 19 Mar 2026 17:11:43 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> The standard library assert(3), at least with glibc, hits our seccomp
> filter and dies with SIGSYS before it's able to print a message, making it
> near useless. Therefore, since 7a8ed9459dfe ("Make assertions actually
> useful") we've instead used our own implementation, named ASSERT().
>
> This makes our code look slightly odd though - ASSERT() has the same
> overall effect as assert(), it's just a different implementation. More
> importantly this makes it awkward to share code between passt/pasta proper
> and things that compile in a more typical environment. We're going to want
> that for our upcoming dynamic configuration tool.
>
> Address this by overriding the standard library's assert() implementation
> with our own, instead of giving ours its own name.
>
> The standard assert() is supposed to be omitted if NDEBUG is defined,
> which ours doesn't do. Implement that as well, so ours doesn't
> unexpectedly differ. For the -DNDEBUG case we do this by *not* overriding
> assert(), since it will be a no-op anyway. This requires a few places to
> add a #include <assert.h> to let us compile (albeit with warnings) when
> -DNDEBUG.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Applied (just this patch).
I fixed up some (expected) trivial conflicts in tcp_vu.c and udp_vu.c
with "vu_common: Move iovec management into vu_collect()".
--
Stefano
next prev parent reply other threads:[~2026-03-20 20:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 6:11 [PATCH v2 00/15] RFC: Read-only dynamic update implementation David Gibson
2026-03-19 6:11 ` [PATCH v2 01/15] treewide: Spell ASSERT() as assert() David Gibson
2026-03-20 20:58 ` Stefano Brivio [this message]
2026-03-19 6:11 ` [PATCH v2 02/15] serialise: Split functions user for serialisation from util.c David Gibson
2026-03-20 20:58 ` Stefano Brivio
2026-03-19 6:11 ` [PATCH v2 03/15] serialise: Add helpers for serialising unsigned integers David Gibson
2026-03-19 6:11 ` [PATCH v2 04/15] fwd: Move selecting correct scan bitmap into fwd_sync_one() David Gibson
2026-03-19 6:11 ` [PATCH v2 05/15] fwd: Look up rule index in fwd_sync_one() David Gibson
2026-03-19 6:11 ` [PATCH v2 06/15] fwd: Store forwarding tables indexed by (origin) pif David Gibson
2026-03-20 20:58 ` Stefano Brivio
2026-03-19 6:11 ` [PATCH v2 07/15] pesto: Introduce stub configuration interface and tool David Gibson
2026-03-19 6:11 ` [PATCH v2 08/15] pesto: Add command line option parsing and debug messages David Gibson
2026-03-19 6:11 ` [PATCH v2 09/15] pesto: Expose list of pifs to pesto David Gibson
2026-03-19 6:11 ` [PATCH v2 10/15] ip: Prepare ip.[ch] for sharing with pesto tool David Gibson
2026-03-19 6:11 ` [PATCH v2 11/15] inany: Prepare inany.[ch] " David Gibson
2026-03-19 6:11 ` [PATCH v2 12/15] fwd: Split forwading rule specification from its implementation state David Gibson
2026-03-19 6:11 ` [PATCH v2 13/15] ip: Define a bound for the string returned by ipproto_name() David Gibson
2026-03-19 6:11 ` [PATCH v2 14/15] fwd_rule: Move forwarding rule text formatting to common code David Gibson
2026-03-19 6:11 ` [PATCH v2 15/15] pesto: Read current ruleset from passt/pasta and display it David Gibson
2026-03-22 14:18 ` [PATCH 16/18] conf: Move port parsing functions to own file, ports.c Stefano Brivio
2026-03-22 14:18 ` [PATCH 17/18] conf, fwd, ports, util: Move things around for pesto Stefano Brivio
2026-03-22 14:18 ` [PATCH 18/18] [DO NOT USE] pesto, conf: Parse, send and receive rules, try to sync forwards 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=20260320215840.155c9f87@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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).