Kernel prepatch 5.7-rc5

[Posted May 10, 2020 by corbet]

The 5.7-rc5 kernel prepatch is out for testing. "We'll see what the next few weeks bring, but at least for now it all feels normal, and like the 5.7 release is tracking well. So please keep testing, and if you haven't dared a 5.7 pre-release kernel yet, we're well into the 'things look calm and safe to test' time."

Kernel prepatch 5.7-rc5

Posted May 11, 2020 1:10 UTC (Mon) by unixbhaskar (guest, #44758) [Link] (3 responses)

Well, it builds.. boots..without fuss... here is a snippet for you to glance :)

[ 2.958511] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.967402] md: Waiting for all devices to be available before autodetect
[ 2.967816] md: If you don't use raid, use raid=noautodetect
[ 2.972796] md: Autodetecting RAID arrays.
[ 2.973169] md: autorun ...
[ 2.973344] md: ... autorun DONE.
[ 3.130783] EXT4-fs (sda): recovery complete
[ 3.137381] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: (null)
[ 3.138736] ext4 filesystem being mounted at /root supports timestamps until 2038 (0x7fffffff)
[ 3.139394] VFS: Mounted root (ext4 filesystem) on device 8:0.
[ 3.150388] devtmpfs: mounted
[ 3.170567] Freeing unused decrypted memory: 2040K
[ 3.230237] Freeing unused kernel image (initmem) memory: 1584K
[ 3.230916] Write protecting the kernel read-only data: 26624k
[ 3.235192] Freeing unused kernel image (text/rodata gap) memory: 2040K
[ 3.236945] Freeing unused kernel image (rodata/data gap) memory: 992K
[ 3.237783] rodata_test: all tests were successful
[ 3.238298] Run /sbin/init as init process
[ 3.278289] process '/bin/busybox' started with executable stack
[ 3.442543] EXT4-fs (sda): re-mounted. Opts: (null)
[ 3.443306] ext4 filesystem being remounted at / supports timestamps until 2038 (0x7fffffff)
[ 3.514639] tsc: Refined TSC clocksource calibration: 2194.918 MHz
[ 3.515429] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1fa37202099, max_idle_ns: 440795206796 ns
[ 3.515988] clocksource: Switched to clocksource tsc
Starting syslogd: OK
Starting klogd: OK
Running sysctl: OK
Initializing random number generator: OK
Saving random seed: [ 4.502876] random: dd: uninitialized urandom read (512 bytes read)
OK
Starting network: [ 4.722763] random: crng init done
OK

Welcome to Buildroot_Linux
Bhaskar_Thinkpad_x250 login: root
# uname -a
Linux Bhaskar_Thinkpad_x250 5.7.0-rc5-Gentoo #1 SMP Mon May 11 04:50:55 IST 2020 x86_64 GNU/Linux
#

ext4 timestamps only until 2038?

Posted May 11, 2020 13:36 UTC (Mon) by pr1268 (guest, #24648) [Link] (2 responses)

ext4 filesystem being remounted at / supports timestamps until 2038 (0x7fffffff)

So does that mean we who still use ext4 are screwed come eighteen years from now?

ext4 timestamps only until 2038?

Posted May 11, 2020 16:12 UTC (Mon) by wsy (subscriber, #121706) [Link] (1 responses)

Only very small patitions use 128byte inode by default. That's why most of us won't get that warning.

ext4 timestamps only until 2038?

Posted May 11, 2020 17:28 UTC (Mon) by cesarb (subscriber, #6266) [Link]

I vaguely recall that, in the past, 128 byte inodes were the default even for large partitions, so it could also be an old filesystem (perhaps even one migrated from ext2 or ext3).