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: <23767.1199866868@turing-police.cc.vt.edu>
Date:	Wed, 09 Jan 2008 03:21:08 -0500
From:	Valdis.Kletnieks@...edu
To:	BuraphaLinux Server <buraphalinuxserver@...il.com>
Cc:	Kyle Moffett <mrmacman_g4@....com>,
	LKML Kernel <linux-kernel@...r.kernel.org>
Subject: Re: The ext3 way of journalling

On Wed, 09 Jan 2008 15:00:46 +0700, BuraphaLinux Server said:
> The help for CONFIG_DM_SNAPSHOT says it is EXPERIMENTAL (in
> 2.6.23.12).  So this would mean that there is very high risk of
> software failure using snapshots.  Would you want to do that for your
> fsck?

The overall current state of EXPERIMENTAL in the tree is, quite frankly,
somewhere between a complete crock and a wheelbarrow full of bovine fertilizer.
There's a lot of things labeled EXPERIMENTAL that shouldn't be, and a lot of
bleeding edge things that may eat your disks and cause your dog to turn green
that aren't labelled EXPERIMENTAL.

Having said that, I have *no* idea what state the snapshot code is in, but I
have approximately zero confidence that the EXPERIMENTAL tag tells me anything
actually useful about the snapshot code.

Content of type "application/pgp-signature" skipped