From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-10.9 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 14982 invoked from network); 14 Mar 2022 20:36:50 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 14 Mar 2022 20:36:50 -0000 Received: (qmail 31846 invoked by uid 550); 14 Mar 2022 20:36:47 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 31803 invoked from network); 14 Mar 2022 20:36:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=NCUa6KdzPdoB9FzLYpo/Ll0mlZ8gij8SOt5k+399N4E=; b=fuy/XfoDHRfWPFMur7FEPZGV0WzIVBdfkLAtL3CTkxdDg7H7Mg82u+7akEbyjK3X95 TT8i3VgF+RgMgwj1Hwvcuj6HNzdhXNO6s/p3TRHoMdDpKR3vqFIOeiMI+uo5Jwp7N8wL NT/k2z6HSiOP75d6Ob5hZyo22wFOb4MwjR7t3drOqhMpYsll9ri1SvqaGU3b6lx1xRph Wlcbt9vxjXtZ8XLHZTF4MToTwG5P7wcY0edBbTiys9wt84rskXiJJufZpIEHrOx6v298 WyEV2WclkNWSTTndUWHsgvSBkeTrb+DaM5w/honkSI/z0B8EqnIWUAGiPN1yYXlSzQNT N4/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=NCUa6KdzPdoB9FzLYpo/Ll0mlZ8gij8SOt5k+399N4E=; b=Y/KUvWRHP1d6DmzGCFi3KJTEynxOAkDGbFYJCBSAzYP9peFZtar9ynq17n+b0vgDlV nYIR90RdsX0+2QND2JbgRUUa3CMiZhAzyyP6Ka1NN9UmITSlsR3olYbuvu2TIR6DxtZM q7bMWp5jxvXJYeJCCVr7edwsmDb8mKru7ZxSMbWJTZL3d+/9igrrfy8BtXxoeyz44P1n ZNe+8Jfb3rYNx/bf8mPrA8WHa0GG5uZ0T2hji2kUas7Y2x/i7yBDziW8ma2ZgfIN0oGT NfiTmzp9EezX0dw04m7GjFkrecDApagTqvDNGmJtvVW99lbLTX2Wep+NYtMjQVdzYNRK ywvQ== X-Gm-Message-State: AOAM533IeDhsGfWHj5Pyf6hAd5ZkO83ACjF9PVSBVUu6HvaLZcpLePHD JvRbXv17t8hMODe9SjHFirAbuGhiFTvZWMUBBhv9YVWebmI4NA== X-Google-Smtp-Source: ABdhPJwOdAs6RoAe0T/1ze9KAggWfzui3Uxwxhkb9u7V13W0+U9se3fQB0eHi0sG9y7A3iUTNV4hMZdv6+xRveuMc7c= X-Received: by 2002:a81:9844:0:b0:2db:db74:f7db with SMTP id p65-20020a819844000000b002dbdb74f7dbmr20907617ywg.359.1647290193922; Mon, 14 Mar 2022 13:36:33 -0700 (PDT) MIME-Version: 1.0 References: <20220308225406.GA10714@brightrain.aerifal.cx> In-Reply-To: <20220308225406.GA10714@brightrain.aerifal.cx> From: enh Date: Mon, 14 Mar 2022 13:36:22 -0700 Message-ID: To: musl@lists.openwall.com Content-Type: multipart/alternative; boundary="000000000000da24bb05da33a23b" Subject: Re: [musl] Summary of open items at 1.2.3 release time --000000000000da24bb05da33a23b Content-Type: text/plain; charset="UTF-8" On Tue, Mar 8, 2022 at 2:54 PM Rich Felker wrote: > I'm trying to wrap up a way-overdue release, and there are some known > things I wanted to get done in this cycle that just need to be put > off: > > - mntent fix: At least as I remember the state of things, there's no > fix patch that's been written and tested that's not making > additional possibly- (likely-) unwanted behavioral changes. > > - pthread_barrier_wait: It seems something is seriously wrong and I > (or someone else, but this is probably best for me to do) need to > sit down and work out the sequencing logic and figure out what's > wrong. The result might entail a redesign and rewrite, so I don't > think we can hold things up with this. I should probably drop use of > it in musl (all uses can be replaced by simpler primitives) but I'd > rather do that after release too. > > - ld-musl....path file location logic: There's a patch for this I > haven't reviewed. It's a low-impact issue so I'll look after > release. > > - ASM source file conversions to inline asm: I'm not sure of the > status on this; it was in progress but not ready for merge before. > > - Some mess in x32 sys/user.h: A bunch of members are 32-bit and some > (maybe all) need to be 64-bit? > > - Some RPATH $ORIGIN failure cases: I need to review this again. > > - Request for preadv2/pwritev2: No follow-up getting info on whether > or how glibc exposes them. > from https://man7.org/linux/man-pages/man2/writev.2.html: preadv2() and pwritev2() first appeared in Linux 4.6. Library support was added in glibc 2.26. (we recently added them to bionic too.) - CMSG_* warning mess: We may want to finally act on this since it > keeps tripping people up, but I don't want to do a hasty change and > risk introducing a bug at release time. Let's look at this later. > > - NFTW_CHDIR support: This is probably ok but I haven't reviewed it. > Hope to merge after release. > > - nscd querying when the daemon is disabled for some query types: IIRC > this had really problematic behavior we don't understand well still > on the nscd side that might mean we're doing things wrong or that > there's no way to do things right. Needs investigation before any > action. > > - Glob altdirfunc stuff and related changes: I don't remember if the > UB was all resolved; if so this may be acceptable to merge. > > - _SC_NPROCESSORS_CONF: Need to review where this is at. > > - Improvements to qsort: These were put off pending qsort_r, which is > done now, so it may be appropriate to fix up and merge these. > > And some things that were open but approved for merge or trivial, that > I'm fixing now: > > - Zeroing canary byte to avoid leaking it via string functions > - Avoid runtime conversions of floating-point constants > - __WORDSIZE inconsistency on x32 > - Linux uapi additions > - nice EACCES/EPERM issue > > All in all, the above list turned out to be a lot more extensive than > I expected, and this really highlights the need for an issue > tracker... > > Please reply to add anything I may have missed. If you have follow-up > on any of the actual items, though, maybe hold off for a few days > until I can actually get a release out and have mental space to deal > with new stuff. :-) > > Rich > --000000000000da24bb05da33a23b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Mar 8, 2022 at 2:54 PM Rich F= elker <dalias@libc.org> wrote:=
I'm trying = to wrap up a way-overdue release, and there are some known
things I wanted to get done in this cycle that just need to be put
off:

- mntent fix: At least as I remember the state of things, there's no =C2=A0 fix patch that's been written and tested that's not making =C2=A0 additional possibly- (likely-) unwanted behavioral changes.

- pthread_barrier_wait: It seems something is seriously wrong and I
=C2=A0 (or someone else, but this is probably best for me to do) need to =C2=A0 sit down and work out the sequencing logic and figure out what's=
=C2=A0 wrong. The result might entail a redesign and rewrite, so I don'= t
=C2=A0 think we can hold things up with this. I should probably drop use of=
=C2=A0 it in musl (all uses can be replaced by simpler primitives) but I= 9;d
=C2=A0 rather do that after release too.

- ld-musl....path file location logic: There's a patch for this I
=C2=A0 haven't reviewed. It's a low-impact issue so I'll look a= fter
=C2=A0 release.

- ASM source file conversions to inline asm: I'm not sure of the
=C2=A0 status on this; it was in progress but not ready for merge before.
- Some mess in x32 sys/user.h: A bunch of members are 32-bit and some
=C2=A0 (maybe all) need to be 64-bit?

- Some RPATH $ORIGIN failure cases: I need to review this again.

- Request for preadv2/pwritev2: No follow-up getting info on whether
=C2=A0 or how glibc exposes them.


=C2=A0 =C2=A0 =C2=A0 =C2=A0preadv2() and pwritev2() first appeared in Lin= ux 4.6.=C2=A0 Library
=C2=A0 =C2=A0 =C2=A0 =C2=A0support was added in gl= ibc 2.26.

(we recently added them to bionic to= o.)

- CMSG_* warning mess: We may want to finally act on this since it
=C2=A0 keeps tripping people up, but I don't want to do a hasty change = and
=C2=A0 risk introducing a bug at release time. Let's look at this later= .

- NFTW_CHDIR support: This is probably ok but I haven't reviewed it. =C2=A0 Hope to merge after release.

- nscd querying when the daemon is disabled for some query types: IIRC
=C2=A0 this had really problematic behavior we don't understand well st= ill
=C2=A0 on the nscd side that might mean we're doing things wrong or tha= t
=C2=A0 there's no way to do things right. Needs investigation before an= y
=C2=A0 action.

- Glob altdirfunc stuff and related changes: I don't remember if the =C2=A0 UB was all resolved; if so this may be acceptable to merge.

- _SC_NPROCESSORS_CONF: Need to review where this is at.

- Improvements to qsort: These were put off pending qsort_r, which is
=C2=A0 done now, so it may be appropriate to fix up and merge these.

And some things that were open but approved for merge or trivial, that
I'm fixing now:

- Zeroing canary byte to avoid leaking it via string functions
- Avoid runtime conversions of floating-point constants
- __WORDSIZE inconsistency on x32
- Linux uapi additions
- nice EACCES/EPERM issue

All in all, the above list turned out to be a lot more extensive than
I expected, and this really highlights the need for an issue
tracker...

Please reply to add anything I may have missed. If you have follow-up
on any of the actual items, though, maybe hold off for a few days
until I can actually get a release out and have mental space to deal
with new stuff. :-)

Rich
--000000000000da24bb05da33a23b--