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: <20260120010512.1951-1-syrus.lssu@ingenic.com>
Date: Tue, 20 Jan 2026 09:05:12 +0800
From: syrus <syrus.lssu@...enic.com>
To: arnd@...db.de
Cc: sanganaka@...dh.me, linux-kernel@...r.kernel.org,
	kernelnewbies@...nelnewbies.org, neil.armstrong@...aro.org,
	"[Syrus]" <"[syrus.lssu@...enic.com]"@web.codeaurora.org>
Subject: Re: Query: Y2038 patch series for 3.18 Kernel

From: [Syrus] <[syrus.lssu@...enic.com]>

Hi Arnd, all,

Thanks for the discussion. While kernel upgrade solves Y2038 for new
projects, our legacy devices on 3.10.14 kernel face upgrade challenges
due to driver compatibility and limited resources (limited manpower, 
communication barriers between different departments and companies, etc.).

Has anyone successfully backported Y2038 fixes to older kernels like
3.10.x? I'm looking for patch summaries or experiences with such
backports, or at least a summary of the commit history that addresses
this issue. Any guidance on key subsystems to focus on would be very
helpful for maintaining our legacy devices.

Best regards,
[Syrus]