Year 2038 time set problem
Hi, Which Linux kernel version have Year 2038 problem solved for Linux running on 32 Bit system. https://en.wikipedia.org/wiki/Year_2038_problem
On Fri, 23 Feb 2018 15:13:30 +0530, techi eth said:
Which Linux kernel version have Year 2038 problem solved for Linux running on 32 Bit system.
Did you read references 15 through 17 on that page? Also, the answer isn't a strict "Linux v5.91 fixes it" - the problem wasn't fixed in one commit. So for instance, some filesystems had 64 bit timestamps from the very beginning, while there's probably at least one or two that still need work. And if your problem is that you've got some ancient ext2 file system images that you have to keep around for forensic reasons, no kernel version is going to help (And yes, that could happen - as part of my job, I've had to keep disk images around for close to a decade due to ongoing legal action, and I've got users who need to keep research data for 30 years due to grant restrictions). So the *real* question here is - what data/hardware/whatever are you looking at where the 2038 problem is possibly relevant?
I am trying on 32 Bit micro board with ubifs file system with Linux Kernel 4.1. On Fri, Feb 23, 2018 at 6:48 PM, <valdis.kletnieks@vt.edu> wrote:
On Fri, 23 Feb 2018 15:13:30 +0530, techi eth said:
Which Linux kernel version have Year 2038 problem solved for Linux running on 32 Bit system.
Did you read references 15 through 17 on that page?
Also, the answer isn't a strict "Linux v5.91 fixes it" - the problem wasn't fixed in one commit. So for instance, some filesystems had 64 bit timestamps from the very beginning, while there's probably at least one or two that still need work.
And if your problem is that you've got some ancient ext2 file system images that you have to keep around for forensic reasons, no kernel version is going to help (And yes, that could happen - as part of my job, I've had to keep disk images around for close to a decade due to ongoing legal action, and I've got users who need to keep research data for 30 years due to grant restrictions).
So the *real* question here is - what data/hardware/whatever are you looking at where the 2038 problem is possibly relevant?
On Sat, Feb 24, 2018 at 07:29:35PM +0530, techi eth wrote:
I am trying on 32 Bit micro board with ubifs file system with Linux Kernel 4.1.
And in your testing, did you find any problems? Also note that the 4.1 kernel is very old and obsolete and insecure, and should NOT be used for any devices in the year 2038. best of luck! greg k-h
Hi, 2018-02-24 16:50 GMT+01:00 Greg KH <greg@kroah.com>:
Also note that the 4.1 kernel is very old and obsolete and insecure, and should NOT be used for any devices in the year 2038.
According to kernel.org website 4.1 has projected EOL in May 2018. Is the information about kernel releases on kernel.org irrelevant/ shouldn't be trusted? Or my understanding of longterm kernel trees is incorrect? Which trees do get security updates? Best regards, Piotr.
I am just trying to know why 4.1 kernel is insecure ? I have try to look but not able to get right answer. Could you please give me hint or link. I only see it is going to EOL by May 2018. https://www.kernel.org/category/releases.html Thanks On Sat, Feb 24, 2018 at 9:20 PM, Greg KH <greg@kroah.com> wrote:
On Sat, Feb 24, 2018 at 07:29:35PM +0530, techi eth wrote:
I am trying on 32 Bit micro board with ubifs file system with Linux Kernel 4.1.
And in your testing, did you find any problems?
Also note that the 4.1 kernel is very old and obsolete and insecure, and should NOT be used for any devices in the year 2038.
best of luck!
greg k-h
On Thu, Mar 01, 2018 at 02:49:05PM +0530, techi eth wrote:
I am just trying to know why 4.1 kernel is insecure ? I have try to look but not able to get right answer.
Could you please give me hint or link. I only see it is going to EOL by May 2018.
Yes, why would you use a kernel that is going to be end-of-life in a few months, in the year 2038? What is going to keep it "secure" until then? thanks, greg k-h
On Sat, 24 Feb 2018 19:29:35 +0530, techi eth said:
I am trying on 32 Bit micro board with ubifs file system with Linux Kernel 4.1.
Is this board something that has a realistic expectation of still being in use in 2038? What's making you worry about 2038 issues? I'm willing to bet that the mostly likely cause of problems inside the kernel will be ubifs. But there's an even bigger chances that something in your userspace isn't 2038 clean yet.
participants (4)
-
Greg KH -
Piotr Figiel -
techi eth -
valdis.kletnieks＠vt.edu