[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160217031623.GC9349@brightrain.aerifal.cx>
Date: Tue, 16 Feb 2016 22:16:23 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: musl 1.1.13 released
On Mon, Feb 15, 2016 at 11:35:28PM -0500, Rich Felker wrote:
> This release adds support for out-of-tree builds, search domains in
> resolv.conf, VDSO-accelerated clock_gettime on MIPS, and building
> SMP-safe/ready SH binaries for the open-hardware J2. Performance of
> atomics and synchronization primitives has been greatly improved on
> most "ll/sc model" RISC archs. Regex BRE now supports the widely-used
> extensions \|, \+, and \? and larger regular expressions are now
> supported. A number of minor application and toolchain compatibility
> improvements have also been made, including changes which reduce the
> risk of assembler and linker bugs leading to malfunctioning binaries.
>
> Two potentially dangerous bugs have been fixed: a single-byte heap
> overflow in getdelim and a pointer indexing error in dynamic TLS
> allocation. Other bugs fixed include various issues in parsing and
> error handling for resolv.conf and related files, incorrect error
> return values for some functions, and failures to accept null pointer
> arguments in some functions for which they have defined behavior. Some
> arch-specific bugs affecting ARM, MIPS, and SH/FDPIC have also been
> fixed.
>
> http://www.musl-libc.org/releases/musl-1.1.13.tar.gz
> http://www.musl-libc.org/releases/musl-1.1.13.tar.gz.asc
It's been found that this release has a fairly significant regression
caused by fixing a bug in fwrite's return value. Users should apply
the attached patch to avoid problems with puts("") and fputs("",f)
malfunctioning.
Rich
View attachment "0001-fix-assumption-in-fputs-that-fwrite-returning-0-impl.patch" of type "text/plain" (1138 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
