From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13836 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: fgets() doesn't call fsync() before getting input Date: Thu, 21 Feb 2019 10:22:43 -0500 Message-ID: <20190221152243.GF23599@brightrain.aerifal.cx> References: Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="2155"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-13852-gllmg-musl=m.gmane.org@lists.openwall.com Thu Feb 21 16:23:00 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1gwqBg-0000Sx-5w for gllmg-musl@m.gmane.org; Thu, 21 Feb 2019 16:23:00 +0100 Original-Received: (qmail 5837 invoked by uid 550); 21 Feb 2019 15:22:58 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 5795 invoked from network); 21 Feb 2019 15:22:57 -0000 Content-Disposition: inline In-Reply-To: Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:13836 Archived-At: On Thu, Feb 21, 2019 at 10:09:03AM -0500, James Larrowe wrote: > I'm writing a program that prints a dialogue to the screen and then asks > for input. In musl, the dialogue does not show before fgets() is called, > however in glibc it does. That causes a blank prompt and also some > confusion. Attached is a minimal example and a log. This difference is intentional. The specification allows but does not require that attempting to read from a line-buffered input stream causes all line-buffered output streams to be flushed. This behavior was somewhat convenient for old-style input-prompt idioms, but it doesn't scale with large numbers of files open and deadlocks with some multi-threaded usage. The portable solution here for applications is to fflush (not fsync) the particular stream you want flushed. Rich