| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 28 Jun 2024 00:43:21 +0200 From: Alexandre Belloni <alexandre.belloni@...tlin.com> To: Leonard Anderweit <L.Anderweit@...tec.de> Cc: "arnd@...db.de" <arnd@...db.de>, "linux-rtc@...r.kernel.org" <linux-rtc@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "upstream@...tec.de" <upstream@...tec.de> Subject: Re: Question about [PATCH] [RFC] rtc: y2038: remove broken RTC_HCTOSYS workaround On 24/06/2024 11:41:41+0000, Leonard Anderweit wrote: > Hi, > > I found this patch [1] which is necessary for a project I'm currently > working on. I'm using phyboard-wega [2] with an am335 ARM SoC which I > want to make y2038 proof. > Is there any reason it was never accepted? > The systemd maintainer think the kernel is well placed to take a decision it can't actually take so they won't fix a bug where systemd is crashing when userspace is 32bit. The whole situation is frustrating and honestly, nobody should use the hctosys insanity anyway. Obviously systemd mandates its usage and this is yet another topic on which they think the kernel is better placed to take decisions that are actually userspace policy. I've been arguing for a while and gave up. > [1]https://lore.kernel.org/all/20220908115337.1604277-1-arnd@kernel.org/ > [2]https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm/boot/dts/ti/omap/am335x-wega-rdk.dts > > Regards > Leonard -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Powered by blists - more mailing lists