From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13287 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Open conformance issues & plans Date: Tue, 18 Sep 2018 01:05:05 -0400 Message-ID: <20180918050505.GU17995@brightrain.aerifal.cx> References: <20180823204124.GM1878@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1537246995 19897 195.159.176.226 (18 Sep 2018 05:03:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 18 Sep 2018 05:03:15 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-13303-gllmg-musl=m.gmane.org@lists.openwall.com Tue Sep 18 07:03:10 2018 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.84_2) (envelope-from ) id 1g28AH-00054D-8Y for gllmg-musl@m.gmane.org; Tue, 18 Sep 2018 07:03:09 +0200 Original-Received: (qmail 1695 invoked by uid 550); 18 Sep 2018 05:05:18 -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 1677 invoked from network); 18 Sep 2018 05:05:17 -0000 Content-Disposition: inline In-Reply-To: <20180823204124.GM1878@brightrain.aerifal.cx> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:13287 Archived-At: Some updates on this: On Thu, Aug 23, 2018 at 04:41:24PM -0400, Rich Felker wrote: > 10. getdelim > > The text of the standard seems to allow malloc/realloc only when the > buffer passed in is not already sufficiently large to hold the result. > The current loop logic we use will force resizing one byte early in > most cases, but can't be trivially changed not to do this without > creating overflows in certain cases (depending on buffering). I will > revisit this after the next release and refactor the loop, but it will > need careful attention to ensure we don't introduce new > bugs/overflows. Fixed in commit 1f6cbdb434114139081fe65a9bafe775e9ab6c41. > 14. abort > > The abort function needs to cause process termination as if by SIGABRT > in the case where a SIGABRT handler was installed but returns. Linux > provides no easy mechanism to do this, and we probably need to > emulate it in userspace by preventing reinstallation of a SIGABRT > handler after the first raise(SIGABRT) in abort() returns. I have an > idea for a design but it's a fair bit of work, and I'll probably > return to it after release. Fixed in commit 9b14ad541068d4f7d0be9bcd1ff4c70090d868d3, included in 1.1.20. Rich