From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <musl-return-20632-ml=inbox.vuxu.org@lists.openwall.com>
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.9 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,
	RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,T_SCC_BODY_TEXT_LINE autolearn=ham
	autolearn_force=no version=3.4.4
Received: from second.openwall.net (second.openwall.net [193.110.157.125])
	by inbox.vuxu.org (Postfix) with SMTP id 5300125338
	for <ml@inbox.vuxu.org>; Wed, 13 Mar 2024 09:28:29 +0100 (CET)
Received: (qmail 1531 invoked by uid 550); 13 Mar 2024 08:24:15 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 1507 invoked from network); 13 Mar 2024 08:24:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1710318496;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=9u8r0uX+gyFaM/bRkYm84ly82XOzt22z7EiPv8k8Al0=;
	b=a31pLSjTYZIIDvECMZAReI9bHsy3bvQS2dHqQPueiqbSkdhQMIm/ERHfLQXKf73FYaiKxX
	OXWoQ+qdNmTlzU7KOMaauiq2O/rA3lHu8H2kBG3DimXkoKGHBN1jqub7wH96tx2mPEx4/a
	mrLKja2ccD4vtOA99Ls4P53Q1LS8hdM=
X-MC-Unique: z09r1BzsMZaS46OpTNYWfA-1
From: Florian Weimer <fweimer@redhat.com>
To: "Zack Weinberg" <zack@owlfolio.org>
Cc: "Rich Felker" <dalias@libc.org>,  "Gabriel Ravier"
 <gabravier@gmail.com>,  "Skyler Ferrante (RIT Student)" <sjf5462@rit.edu>,
  musl@lists.openwall.com,  "Andreas Schwab" <schwab@suse.de>,  "Alejandro
 Colomar" <alx@kernel.org>,  "Thorsten Glaser" <tg@mirbsd.de>,  NRK
 <nrk@disroot.org>,  "Guillem Jover" <guillem@hadrons.org>,  "GNU libc
 development" <libc-alpha@sourceware.org>,  libbsd@lists.freedesktop.org,
  "Serge E. Hallyn" <serge@hallyn.com>,  "Iker Pedrosa"
 <ipedrosa@redhat.com>,  "Christian Brauner" <christian@brauner.io>
References: <Pine.BSM.4.64L.2403110017360.18628@herc.mirbsd.org>
	<Ze5UdYsZ6H9i6lMd@debian>
	<CAEOG19qSWnH6WVuTCVZLfTr1HhZnu_W86r7B-64CJrRvhyh_zQ@mail.gmail.com>
	<mvmmsr4ole0.fsf@suse.de>
	<CAEOG19pPhJzJo+3aKV_jUt3GDbH61y44DQNzKEjYxkf=nR-9aQ@mail.gmail.com>
	<20240311194756.GY4163@brightrain.aerifal.cx>
	<40962405-c5b4-4925-9ca5-7a1c723ebbfd@gmail.com>
	<875xxrv9mm.fsf@oldenburg.str.redhat.com>
	<84bf19d7-c2ba-46e7-a77d-ecc6497f08a1@app.fastmail.com>
	<87o7bjttcn.fsf@oldenburg.str.redhat.com>
	<20240312144225.GC4163@brightrain.aerifal.cx>
	<180c5e67-5e97-4ac8-ab7c-696d2aa865ed@app.fastmail.com>
Date: Wed, 13 Mar 2024 09:28:07 +0100
In-Reply-To: <180c5e67-5e97-4ac8-ab7c-696d2aa865ed@app.fastmail.com> (Zack
	Weinberg's message of "Tue, 12 Mar 2024 15:25:31 -0400")
Message-ID: <87il1qsfhk.fsf@oldenburg.str.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.3 (gnu/linux)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.8
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain
Subject: Re: [musl] Re: Tweaking the program name for <err.h> functions

* Zack Weinberg:

> I do fully agree that this is a design error in NFS and in close(2)
> more generally [like all destructors, it should be _impossible_ for
> close to fail], but there is no realistic prospect of changing it, and
> I've been burned a few times by programs that didn't notice delayed
> write errors.

There is fsync to avoid delayed write errors.  Historically, it's been
very bad for performance.  What coreutils et al. aim to do is to deal
with non-catastrophic failures (mainly out of space errors) without
incurring the fsync overhead.

Thanks,
Florian