From nobody Tue Jan 10 18:55:15 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ns0Pb0VyKz2sRXd for ; Tue, 10 Jan 2023 18:55:31 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ns0PZ5x8hz4FTZ; Tue, 10 Jan 2023 18:55:30 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-f180.google.com with SMTP id n5so12992851ljc.9; Tue, 10 Jan 2023 10:55:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QU3yXC5bdehYb6KG09CCJYq480EfnpPuTepGqyiXkuk=; b=AdnTdSusPYUilltlkLdIGyEKhtdXz8hYlACSyWKlYyJRpKXXKq4V3iVp+66x4803Co h/2617bsoRGF7zTETqA4aEsUNxVh4PtIeQZ8BOaVotwGANeL2mJyC4yyFw7sMhV06D8k XofQSlFDY7FeBxkuc8an92VoT8quVcY35T0LDJGdpG4w8bX/LkOJG3t1CwymIWCXILpM BESOWlkvtIp8JLj2o0NHZXQpjmKaxshvsyOr1hYX0jdHJoASJkmG4EGueeiwa+q1KZd5 aIaboi3UiXW41WuzYdnAprEQr75sy0WFoXXgMB5CQivWwe3319ilVOa2CJOd5IUpcpoA b/KA== X-Gm-Message-State: AFqh2kr8onIylIfflrRgLrMpHcd4aNgxR2WI8hkL2wJNjSzQp+hrEskp 04dkkx87hvIGfTX7ihCFALZxQHiAHW5XP4+u2p90p27k X-Google-Smtp-Source: AMrXdXt6oXN0ddo/WUL+mBmOPsrQD2wWElfsr2KwZy1A3S13Yxj/2g/PxbZUIpjNVISzAfmTGt9AWk5SV0DE8XrzpaU= X-Received: by 2002:a2e:b88b:0:b0:288:2375:e931 with SMTP id r11-20020a2eb88b000000b002882375e931mr35145ljp.381.1673376928044; Tue, 10 Jan 2023 10:55:28 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Ed Maste Date: Tue, 10 Jan 2023 13:55:15 -0500 Message-ID: Subject: Re: libcasper and async-signal-safety To: Alan Somers Cc: FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Ns0PZ5x8hz4FTZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, 10 Jan 2023 at 13:45, Alan Somers wrote: > > I assume that this is just an oversight. After all, all of the > existing programs in the base system that use casper are > single-threaded. But it's a limitation that ought to be documented in > the cap_init(3) man page, right? Or am I missing something? I don't think you're missing anything, and this just needs to be explicitly documented. The forking behaviour of Casper services is perhaps an internal implementation detail, but the limitations it imposes on the consumer should be clear.