From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4F49A3857C5A; Wed, 13 Mar 2024 10:28:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4F49A3857C5A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1710325727; bh=G6DhGqDPet+TnT0JfI6g2vTuE/KwWVMd7mBWCa//fe0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=pdEmkUXV5O+Ezlr2DAsGjWyiRPPsEiemJZDBx8oUxGhmqzMwQa3j7Qlb2fO0BKtHe kWHJalEzL7GJZiI/tPyVidhfZqI+8lhqN5ieXjkljXaKAFuHW0bOxNkpiXGdakaAJP tmiEJ0N/ky29+5tlLwqbJNGTew/tAhEUi6tkhi7E= From: "dvyukov at google dot com" To: glibc-bugs@sourceware.org Subject: [Bug stdio/15142] Missing locking in _IO_cleanup Date: Wed, 13 Mar 2024 10:28:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: stdio X-Bugzilla-Version: 2.3.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dvyukov at google dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 2.38 X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D15142 --- Comment #8 from Dmitry Vyukov --- > 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 b= efore 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? --=20 You are receiving this mail because: You are on the CC list for the bug.=