From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <musl-return-21638-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=-3.1 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED 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 E4DE32158A
	for <ml@inbox.vuxu.org>; Sat, 18 Jan 2025 10:58:24 +0100 (CET)
Received: (qmail 14209 invoked by uid 550); 18 Jan 2025 09:58:21 -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
x-ms-reactions: disallow
Received: (qmail 14168 invoked from network); 18 Jan 2025 09:58:20 -0000
From: Florian Weimer <fw@deneb.enyo.de>
To: musl@lists.openwall.com
Date: Sat, 18 Jan 2025 10:58:11 +0100
Message-ID: <87ed10mojw.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain
Subject: [musl] Linked stream handling

Some of us interpret POSIX that it requires or at least encourages a
concept of linked streams: reading on from some streams may implicitly
flush certain other streams.  (The language in the standard around
that is not particularly clear.)  Linked streams may introduce
deadlocks (particularly with explicit locking if flockfile), so POSIX
suggests that implementations provide some form of deadlock detection,
failing certain stream operations.

Do I read the sources correctly, and musl does not implement any of
this?