linux-kernel - Re: Query: Y2038 patch series for 3.18 Kernel

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <0fe1ce84-b7b2-4c37-a94a-80ddd7339105@app.fastmail.com>
Date: Thu, 06 Nov 2025 09:17:21 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Pintu Kumar Agarwal" <pintu.ping@...il.com>
Cc: "Siddh Raman Pant" <sanganaka@...dh.me>,
 linux-kernel <linux-kernel@...r.kernel.org>,
 kernelnewbies <kernelnewbies@...nelnewbies.org>,
 "Neil Armstrong" <neil.armstrong@...aro.org>
Subject: Re:  Query: Y2038 patch series for 3.18 Kernel

On Wed, Nov 5, 2025, at 10:47, Pintu Kumar Agarwal wrote:
> On Tue, 4 Nov 2025 at 15:18, Arnd Bergmann <arnd@...db.de> wrote:
>
>> Which chip exactly are you using?
> This request is for one of the legacy QC MDM 9K chipset.

Ah, I see. Support for those was never fully merged, so it's
much harder to upgrade than other platforms, especially
if you need the modem driver to work.

We do have some support for the newer sdx55/sdxx65 chips,
and much more rudimentary support for mdm9607 and mdm9615
(without modem) in mainline, but since we've never had a
fully supported board use the older chips I would not expect
them to work without additional bugfixes and a rebase of
the missing drivers.

There is of course a chance that you may get them to work
in a way that does not rely on knowing the time. If you
don't have (or use) and RTC and the system time is always
set to Jan 1 1970 on boot, this would technically work
indefinitely. Running a 3.18 kernel is obviously a bad idea
for a number of other reasons.

     Arnd