mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Hentges <mailinglisten@hentges.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: AES cryptoloop corruption under recent -mm kernels
Date: 15 Jan 2004 03:44:28 +0100	[thread overview]
Message-ID: <1074134668.6094.16.camel@mhcln02> (raw)
In-Reply-To: <20040114125210.1dc50593.akpm@osdl.org>

Am Mit, 2004-01-14 um 21.52 schrieb Andrew Morton:
> Jim Faulkner <jfaulkne@ccs.neu.edu> wrote:
> >
> > I am experiencing data corruption on my AES cryptoloop partition under
> > recent -mm kernels (including 2.6.1-mm3).  I am unsure how long this
> > problem has existed, and I am unsure if this problem exists in the
> > mainstream kernel (I can't test it because of an aic7xxx bug in the
> > mainstream kernel).
> 
> It exists in the mainstream kernel.
> 
> I thought we had this whipped in 2.6.0-mm2, but then I removed the loop
> patches and switched to a new set.  I think I'll switch back.
> 
> It would be interesting to find out if 2.6.0-mm2 is working OK for you.

FYI: 2.6.0-mm2 fixed a nasty crypto-loop corruption bug for me.
IIRC it was encrypted w/ AES. I did not try 2.6.1-mm3, yet.

Thanks god the corruption could be fixed by running e2fsck over the
encrypted loop device using a 2.4 kernel.
A stock 2.6.0 would crash the machine when trying that.

HTH
-- 

Matthias Hentges 
Cologne / Germany

[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4   -> No files, no URL's

My OS: Debian Woody. Geek by Nature, Linux by Choice


  parent reply	other threads:[~2004-01-15  2:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14 20:36 Jim Faulkner
2004-01-14 20:41 ` Jim Faulkner
2004-01-14 20:52 ` Andrew Morton
2004-01-14 23:30   ` Jim Faulkner
2004-01-15  2:44   ` Matthias Hentges [this message]
2004-01-15 16:57 ` Jari Ruusu
2004-01-15 17:24   ` Jim Faulkner
2004-01-15 20:33     ` Jari Ruusu
2004-01-15 22:59       ` Hans Reiser
2004-01-16 14:21       ` Mark Borgerding
2004-01-16 15:42         ` James Morris
2004-01-16 17:10           ` Mark Borgerding
2004-01-17  2:47             ` David Wagner
2004-01-17 16:13               ` Mark Borgerding
2004-01-17 20:39             ` Shawn Willden
     [not found]       ` <4007EBDA.2060308@borgerding.net>
     [not found]         ` <4007F79C.80A5DE72@users.sourceforge.net>
     [not found]           ` <400818AA.9080009@borgerding.net>
2004-01-16 21:43             ` Jari Ruusu
2004-01-15 18:16   ` James Morris
2004-02-01 17:19     ` Pasi Kärkkäinen
2004-02-01 19:40       ` markus reichelt

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=1074134668.6094.16.camel@mhcln02 \
    --to=mailinglisten@hentges.net \
    --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

Powered by JetHome