We are getting closer and closer to the year 2038 where the 32 bit
time_t overflow will happen. While products (= embedded systems) with an
expected life time of 15 years are still save the situation may change
if your system has to survive the next 20 years.
ext2 and ext3 filesystems are always a
From: Florian Bezdeka
We are getting closer and closer to the year 2038 where the 32 bit
time_t overflow will happen. While products (= embedded systems) with an
expected life time of 15 years are still save the situation may change
if your system has to survive the next 20 years.
ext2 and ext3
On Mon, 2021-02-22 at 15:59 +, Richard Purdie wrote:
> On Mon, 2021-02-22 at 11:42 +0000, florian.bezd...@siemens.com wrote:
> > From: Florian Bezdeka
> >
> > We are getting closer and closer to the year 2038 where the 32 bit
> > time_t overflow will happen.
From: Florian Bezdeka
We are getting closer and closer to the year 2038 where the 32 bit
time_t overflow will happen. While products (= embedded systems) with an
expected life time of 15 years are still save the situation may change
if your system has to survive the next 20 years.
ext2 and ext3
Hi Richard,
On Fri, 2021-02-19 at 10:55 +, Richard Purdie wrote:
> On Thu, 2021-02-18 at 13:06 +0000, florian.bezd...@siemens.com wrote:
> > From: Florian Bezdeka
> >
> > The following patch is the summary of a nice journey through the file
> > system jungle rega
From: Florian Bezdeka
We are getting closer and closer to the year 2038 where the 32 bit
time_t overflow will happen. While products (= embedded systems) with an
expected life time of 15 years are still save the situation may change
if your system has to survive the next 20 years.
ext2 and ext3
From: Florian Bezdeka
The following patch is the summary of a nice journey through the file
system jungle regarding Y2038 problem. It all began with a warning which
is reported by kernels >= 5.4:
ext4 filesystem being mounted at (mountpoint) supports timestamps until
2038 (0x7fff)
When re
