From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/12004 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: open issues Date: Fri, 13 Oct 2017 22:59:40 -0400 Message-ID: <20171014025940.GN1627@brightrain.aerifal.cx> References: <20170827043606.GQ15263@port70.net> <20170830020652.GD1627@brightrain.aerifal.cx> <20170907021812.GQ1627@brightrain.aerifal.cx> <20170907023201.GR1627@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 1507950562 623 195.159.176.226 (14 Oct 2017 03:09:22 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 14 Oct 2017 03:09:22 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-12017-gllmg-musl=m.gmane.org@lists.openwall.com Sat Oct 14 05:09:18 2017 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 1e3Cp8-0007eE-Ay for gllmg-musl@m.gmane.org; Sat, 14 Oct 2017 05:09:14 +0200 Original-Received: (qmail 30417 invoked by uid 550); 14 Oct 2017 03:09:17 -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 30389 invoked from network); 14 Oct 2017 03:09:16 -0000 Content-Disposition: inline In-Reply-To: <20170907023201.GR1627@brightrain.aerifal.cx> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:12004 Archived-At: On Wed, Sep 06, 2017 at 10:32:01PM -0400, Rich Felker wrote: > Updated status: > > Pending decision(s) of what do to: > > - fix nftw when called with paths ending in slash > http://www.openwall.com/lists/musl/2017/03/07/1 Planning to just commit my minimal fix for now since further changes are still incomplete/pending discussion. > - use-after-free in __unlock of pthread struct > http://www.openwall.com/lists/musl/2017/06/01/7 I really want to adopt the new lock but the release is way past due without having thoroughly reviewed and tested. I have a trivial patch to just make pthread_detach always call __wake rather than using the waiters count which fixes the bug for now. We can switch back to lock primitives once the new lock is in use. > - missed underflow in fma > http://www.openwall.com/lists/musl/2017/03/19/6 > new fma, depends on a_clz_64 > http://www.openwall.com/lists/musl/2017/04/23/10 > [new patch on top of old one submitted, still not ideal > but no volatile] Applying nsz's latest patch that fixed the volatile hacks. > Pending updated patch: > > - make dlsym and reloc time lookup consistent > http://www.openwall.com/lists/musl/2017/02/16/1 Punting to next release cycle. > Pending analysis of cause: > > - mips64 utime issue? > "tar binary can't fix the modification/access times on any extracted symbolic links," > http://www.openwall.com/lists/musl/2017/07/06/1 Punting to next release cycle. > Additional issue that was left out that I promised for a long time to > review; pending tests to ensure it doesn't break anything in the > standard functionality it touches: > > - strftime extensions > http://www.openwall.com/lists/musl/2016/11/22/1 I'm still waiting for tests to show that this doesn't introduce regressions, so won't be including the patch. But for the purpose of Alpine or any other distros that want to patch it themselves without introducing incompatibility, please consider it "accepted" in that the interface (the extensions) will make it upstream; it's just the implementation that still needs checking (and may need changes if there are problems). I think this mostly concludes what's pending for release. Rich