Year 2038 time set problem

[techi eth]

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 at 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.
> >
> > https://en.wikipedia.org/wiki/Year_2038_problem
>
> 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?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180224/f5ac7e25/attachment.html>