The filesystem timestamps were improved in ext4. The addition of two high-order bits in the timestamp field defers the Year 2038 problem until 2446—for EXT4 filesystems, at least.
However this means that the test fails with:
[779(5526)/2647 at 42m57s] samba3.smb2.timestamps(nt4_dc)
Using seed 1603364661
Got: create: Thu May 10 22:38:55 2446 UTC, write: Thu May 10 22:38:55 2446 UTC, change: Thu May 10 22:38:55 2446 UTC
Got: create: Thu May 10 22:38:55 2446 UTC, write: Tue Jan 19 03:14:07 2038 UTC, change: Tue Jan 19 03:14:07 2038 UTC
REASON: Exception: Exception: ../../source4/torture/smb2/timestamps.c:184: nttime was 266768591350000000 (0x3B3C09ED4A5E980), expected 137919572470000000 (0x1E9FD1ED4A5E980): Wrong write time
The failing tests are:
(In reply to Andreas Schneider from comment #1)
Wonder why these fails when the fs is *expanding* the value range as the tests just test time_t value that are *within* INT32_MAX (or UINT32_MAX, not sure which one :) ).