mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: [musl] musl 1.2.2 release
Date: Thu, 14 Jan 2021 23:58:24 -0500	[thread overview]
Message-ID: <20210115045821.GI23432@brightrain.aerifal.cx> (raw)

The release adds the _Fork function from the upcoming edition of POSIX
and takes advantage of the interpretation dropping the
async-signal-safety requirement from fork to provide a consistent
execution environment (not restricted to calling only
async-signal-safe functions) after a multithreaded parent forks. This
solves deadlocks which would otherwise be effectively unfixable in
some language runtimes that expose fork as part of their contract with
applications, as well as various library and application software that
could and should be fixed, but hasn't been. A number of related issues
in synchronization between fork, abort, async IO, posix_spawn,
pthread_exit, and other components have been fixed as part of this
change.

The realpath function has been rewritten to do its own path traversal,
rather than depending on procfs magic symlink contents for O_PATH file
descriptors. This makes it work prior to mount of /proc and in
container or chroot environments where /proc contents may not
accurately reflect the pathname as visible to the calling process.

The C versions of the square root functions, used on archs without a
native FPU instruction for square root, have also been rewritten with
significant improvements to performance, especially on archs that lack
FPU entirely. This rewrite also fixes the lack of accurate sqrtl on
archs with quad-precision long double.

New functions added include the aforementioned _Fork, reallocarray
from OpenBSD, gettid along with SIGEV_THREAD_ID timer notification
support, and tcgetwinsize/tcsetwinsize from POSIX-future.

A buffer overflow (CVE-2020-28928) in wcsnrtombs has been fixed with
the function essentially rewritten. This function is not widely used
and the bug is not relevant to software that does not use it directly
(it's not used by other libc components), but it may be serious for
software that does. An assortment of lesser bugs have also been fixed.



https://musl.libc.org/releases/musl-1.2.2.tar.gz
https://musl.libc.org/releases/musl-1.2.2.tar.gz.asc



Special thanks to musl's release sponsors who have supported the
project financially over this release cycle via Patreon and GitHub
Sponsors at the $32/month level or higher:

* Andrew Kelley / ziglang
* David Sonder
* Drew DeVault
* Evan Phoenix
* Hurricane Labs (hurricanelabs.com)
* Jered Sutton
* Jeremiah Gowdy
* Jonathan Barronville
* Jonny
* Julien Voisin
* Justin Cormack
* Laurent Bercot
* Les Aker
* The Midipix Project (midipix.org)
* Michael Forney
* Mirza Prasovic
* Nathan Hoad
* Neal Gompa
* Noel Cower

For information on becoming a sponsor, visit one of:

https://github.com/sponsors/richfelker
https://patreon.com/musl

                 reply	other threads:[~2021-01-15  4:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210115045821.GI23432@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).