Date: Fri, 6 Aug 2010 16:39:00 +0800
From: Herbert Xu <herbert@gondor.hengli.com.au>
To: Olivier Galibert <galibert@pobox.com>
Cc: kyle@moffetthome.net, torvalds@linux-foundation.org,
        herbert@gondor.hengli.com.au, dhowells@redhat.com, gregkh@suse.de,
        linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: Initcall ordering problem (TTY vs modprobe vs MD5) and
	cryptomgr problem
Message-ID: <20100806083900.GA25385@gondor.apana.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100806080642.GA4642@dspnet.fr>
Organization: Core
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1036
Lines: 25

Olivier Galibert <galibert@pobox.com> wrote:
>
> Of course in practice without the tests your boot would probably just
> have failed.  Badly-decrypted root partitions tend to be noticed as
> such long before trying to write to them.  Then you would have bitched
> on the list and the driver would have been fixed or removed faster
> than having to wait for you (or other people with the hardware issue)
> to notice the spew in dmesg.

So you'd rather have a box that doesn't boot rather than one
that automatically falls back to software crypto allowing you
to diagnose and report the problem.

Yes that makes a lot of sense.

Thanks,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/