mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Stirling <root@mauve.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: loop device corruption in 2.4.6
Date: Thu, 5 Jul 2001 12:39:36 +0100 (BST)	[thread overview]
Message-ID: <200107051139.MAA15813@mauve.demon.co.uk> (raw)
In-Reply-To: <3B443F11.307A5F61@pp.inet.fi> from "Jari Ruusu" at Jul 05, 2001 01:18:57 PM

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


  reply	other threads:[~2001-07-05 11:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-04 21:14 Mark Swanson
2001-07-05  5:29 ` Stefan Traby
2001-07-05 10:18 ` Jari Ruusu
2001-07-05 11:39   ` Ian Stirling [this message]
2001-07-05 14:17   ` Mark Swanson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200107051139.MAA15813@mauve.demon.co.uk \
    --to=root@mauve.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®