From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Late time64 changes on the way
Date: Thu, 19 Dec 2019 13:39:51 -0500 [thread overview]
Message-ID: <20191219183951.GA1236@brightrain.aerifal.cx> (raw)
Based on recent findings, I'm working on some late (in the sense of
late in the release cycle) time64 changes I didn't expect to be
making. In particular it was found that, without significant
time64-aware hacks on the application/other-libraries side, the
following would stop working when built for time64:
- socket timestamping (SO_TIMESTAMP[NS])
- sound (ALSA)
- video capture (V4L2)
- ppp (timeouts)
- legacy parallel ports (¯\_(ツ)_/¯)
The first 3, and possibly the first 4, are a pretty big deal -- "Sound
isn't going to work anymore unless you upgrade your kernel" is a big
blocker to adoption and would almost certainly leave us with a
situation where distros/users are trying to stick back with pre-time64
versions or use tricks to keep building new binaries as time32.
I already have a fix for the first queued (fallback to old options
that produce 32-bit timestamps with translation of the cmsg payload in
recvmsg) and an in-progress fix for the rest.
For sound, there are still pending patches to the kernel headers that
will be needed for it to work right:
https://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git/log/?h=y2038-endgame
The needed ones will be backported/merged in musl-cross-make soon.
Once I push these changes, I'd love some assistance testing that they
actually work from users who have appropriate setups (32-bit userspace
with pre-time64 kernel, sound or video capture hardware, software for
using it). Please reply (or mention it on #musl) if you can help.
Rich
next reply other threads:[~2019-12-19 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 18:39 Rich Felker [this message]
2019-12-21 20:01 ` 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=20191219183951.GA1236@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).