summaryrefslogtreecommitdiffstats
path: root/meta/lib/oeqa/runtime/cases/pam.py
diff options
context:
space:
mode:
authorFlorian Bezdeka <florian.bezdeka@siemens.com>2021-02-25 09:22:02 +0100
committerSteve Sakoman <steve@sakoman.com>2021-03-11 05:00:02 -1000
commit280bf295a12b49a1d5199d86da6641516df0ce6a (patch)
tree50814cbd0d7f9dded70809407cfaf441363bba8f /meta/lib/oeqa/runtime/cases/pam.py
parent8b38cd1b36f3e227a63c0aa3955f3f5ab172c509 (diff)
downloadopenembedded-core-contrib-280bf295a12b49a1d5199d86da6641516df0ce6a.tar.gz
wic: Warn if an ext filesystem affected by the Y2038 problem is used
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 affected by the time overflow, so let's warn the user if these filesystems are still being used. If ext4 is affected depends on the inode size chosen during filesystem creation. At least 256 bytes are necessary to be safe. As ext4 is used very often (and partitions may be created small first and extended later) this might be an issue for many users. Some filesystems created during CI runs were already affected by the Y2038 problem. By using `--mkfs-extraopts "-T default"` we tell mke2fs not to auto-detect the usage type based on the filesystem size. mke2fs will use the default values for tuning parameters instead. The inode size is one of these parameters. Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit eecbe625558406680121d2a7e84917fea45ea9dc) Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'meta/lib/oeqa/runtime/cases/pam.py')
0 files changed, 0 insertions, 0 deletions