lkml.org 
[lkml]   [2001]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: loop device corruption in 2.4.6
Date
> 
> Mark Swanson wrote:
> > I get repeatable errors with 2.4.6 patched with the international encryption
> > patch patch-int-2.4.3.1.bz2 when building loop device filesystems on top of
> > Reiserfs.
>
<snip>
> And the block size thing is not the only thing wrong with international
> crypto patch. The whole cryptoapi thing is just bloat that does not belong
> in kernel. Cipher name string to number code mappings should be done in user
> space instead of kernel. And the ice on the cake is that cryptoapi ciphers

Why is this any more evil than protocol names in kernel, or filesystem names
in kernel. The consequences of getting the cipher wrong are often worse
than that of getting the filesystem wrong.
<snip>
> Loop-AES is a superior replacement for international crypto patch, for more
> information about loop-AES, see this announcement:

That has a fraction of the features.

And no, I'm not completely happy with crypto-API, I managed to get it to
corrupt a test FS with a few weeks stress-test a while back.

-
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/

\
 
 \ /
  Last update: 2005-03-22 12:56    [W:0.035 / U:0.496 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site