From: Florian Weimer <fw@deneb.enyo.de>
To: musl@lists.openwall.com
Subject: [musl] Linked stream handling
Date: Sat, 18 Jan 2025 10:58:11 +0100 [thread overview]
Message-ID: <87ed10mojw.fsf@mid.deneb.enyo.de> (raw)
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?
next reply other threads:[~2025-01-18 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 9:58 Florian Weimer [this message]
2025-01-18 11:31 ` Rich Felker
2025-01-19 11:20 ` Florian Weimer
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=87ed10mojw.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=musl@lists.openwall.com \
/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://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).