From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/15049 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Late time64 changes on the way Date: Thu, 19 Dec 2019 13:39:51 -0500 Message-ID: <20191219183951.GA1236@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="29022"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-15065-gllmg-musl=m.gmane.org@lists.openwall.com Thu Dec 19 19:40:11 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1ii0iX-0007Iw-82 for gllmg-musl@m.gmane.org; Thu, 19 Dec 2019 19:40:09 +0100 Original-Received: (qmail 7693 invoked by uid 550); 19 Dec 2019 18:40:06 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 7655 invoked from network); 19 Dec 2019 18:40:05 -0000 Content-Disposition: inline Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:15049 Archived-At: 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