linux-ext4 - Why does e2fsck stop on system clock differences?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4F4CFF35.2040504@redhat.com>
Date:	Tue, 28 Feb 2012 10:22:13 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Why does e2fsck stop on system clock differences?

I've got Fedora users concerned (again) about clock problems stopping their boot in e2fsck.

I know about the +/- 24h slop, and the broken_system_clock e2fsck.conf setting, which we might just set to do away with this issue.

But I wonder if I can get a little historical perspective from the extN elders on why e2fsck is so clock-obsessed. (I think this has been discussed in other threads, but I'm not finding them now)

What are the actual risks if we just ignore time differences at fsck time, can we get this stated on the record (hopefully in a somewhat google-able $SUBJECT?)

Thanks,
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html