linux-kernel - Re: The ext3 way of journalling

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080108213225.GC5050@ucw.cz>
Date:	Tue, 8 Jan 2008 21:32:26 +0000
From:	Pavel Machek <pavel@....cz>
To:	Tuomo Valkonen <tuomov@....fi>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: The ext3 way of journalling

On Tue 2008-01-08 16:07:27, Tuomo Valkonen wrote:
> 
> The ext3 journalling code can be summarised as:
> 
>     superblock->last_checked = random();
>     sync(superblock)
> 
> I hate it: every time Linux crashes, e.g. due to power failure, it takes
> almost an hour to boot, because the kernel has decided to corrupt the 
> superblock to indicate that it's been years since last file system 
> check. And obviously the crappy init system provides no simple way to 
> stop the checking, to put it in the background, or whatever. The FOSS 

rm /sbin/fsck?

And no, ext3 here does not corrupt last_checked here.
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/