mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Anthony G. Basile" <basile@opensource.dyc.edu>
To: musl@lists.openwall.com
Subject: Re: musl 1.1.13 released
Date: Fri, 19 Feb 2016 05:22:46 -0500	[thread overview]
Message-ID: <56C6ECF6.2070400@opensource.dyc.edu> (raw)
In-Reply-To: <20160217031623.GC9349@brightrain.aerifal.cx>

On 2/16/16 10:16 PM, Rich Felker wrote:
> 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
> 

Thanks I was in the middle of debugging this.  I hit it with coreutils
`yes ""` on arm.

We've had these sorts of bugs in the past.  Wouldn't it be wise to push
out a new release?  Something like musl-1.1.13.1?  I can deal with
applying the patch but pushing out a another release signals to the
community that there is an update.  Just thought.

-- 
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197


  reply	other threads:[~2016-02-19 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16  4:35 Rich Felker
2016-02-17  3:16 ` Rich Felker
2016-02-19 10:22   ` Anthony G. Basile [this message]
2016-02-19 17:24     ` Shiz
2016-02-19 17:57       ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56C6ECF6.2070400@opensource.dyc.edu \
    --to=basile@opensource.dyc.edu \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).