CephFS(vfs): modern_write_time_update-{1,2} torture tests fails with "bad time" on non-proxy shares

[anoopcs9]

test: samba3.smb2.timestamps.modern_write_time_update-1
time: 2025-06-10 04:26:32.790215Z
time: 2025-06-10 04:26:33.149958Z
failure: samba3.smb2.timestamps.modern_write_time_update-1 [
Exception: ../../source4/torture/smb2/timestamps.c:1395: currenttime1 was Wed Jun 11 04:26:32 2025 UTC, expected Wed Jun 11 04:26:32 2025 UTC: bad time

]
test: samba3.smb2.timestamps.modern_write_time_update-2
time: 2025-06-10 04:26:33.150016Z
time: 2025-06-10 04:26:33.498704Z
failure: samba3.smb2.timestamps.modern_write_time_update-2 [
Exception: ../../source4/torture/smb2/timestamps.c:1687: ctime1 was Tue Jun 10 04:26:33 2025 UTC, expected Tue Jun 10 04:26:33 2025 UTC: bad time

]

[anoopcs9]

tracker #71622 created upstream for smb2.timestamps.modern_write_time_update-1 failure.

[anoopcs9]

Another tracker #71639 for smb2.timestamps.modern_write_time_update-2 failure.

[anoopcs9]

Another tracker #71639 for smb2.timestamps.modern_write_time_update-2 failure.

This failure will most probably vanish with !4084.

Edit: As anticipated smb2.timestamps.modern_write_time_update-2 failure is no longer seen after !4084 is merged.

[anoopcs9]

tracker #71622 created upstream for smb2.timestamps.modern_write_time_update-1 failure.

Given the time taken to address the issue from CephFS side, we add it to the flapping list for now.