public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dvyukov at google dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/15142] Missing locking in _IO_cleanup Date: Wed, 13 Mar 2024 10:28:47 +0000 [thread overview] Message-ID: <bug-15142-131-DaukBI6e0y@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15142-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15142 --- Comment #8 from Dmitry Vyukov <dvyukov at google dot com> --- > For streams which are blocked in writing, POSIX does not really give us a way to make forward progress because we have to flush the unwritten data before exiting. Is it really the case for this program? If a write does not happen before exit (which is the case in any such blocking), then program cannot potentially know the write has even started before fflush/exit, so it cannot possibly expect the write side-effects to be flushed. What am I missing? > We could perhaps add another flag to fopen/fdopen that indicates that the stream should not participate in fflush (NULL) or exit flushing. Should we worry about all of the existing programs that will start hanging? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-13 10:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-13 13:12 [Bug stdio/15142] New: " schwab@linux-m68k.org 2013-02-14 20:13 ` [Bug stdio/15142] " bugdal at aerifal dot cx 2014-03-25 9:24 ` schwab@linux-m68k.org 2014-06-13 18:49 ` fweimer at redhat dot com 2023-06-04 22:16 ` ppluzhnikov at google dot com 2023-07-03 9:08 ` fweimer at redhat dot com 2024-03-13 10:13 ` dvyukov at google dot com 2024-03-13 10:23 ` fweimer at redhat dot com 2024-03-13 10:28 ` dvyukov at google dot com [this message] 2024-03-13 10:43 ` fweimer at redhat dot com
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=bug-15142-131-DaukBI6e0y@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).