From: Peter Lieverdink <peter@cc.com.au>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: loopback device + crypto = crash on 2.6.0-test7 ?
Date: Tue, 06 Jan 2004 21:36:31 +1100 [thread overview]
Message-ID: <1073385390.1110.2.camel@kahlua> (raw)
In-Reply-To: <6.0.0.22.2.20031111101721.01bde418@caffeine.cc.com.au>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On Tue, 2003-11-11 at 10:27, Peter Lieverdink wrote:
> At 09:41 11/11/2003, you wrote:
> >In article <20031109131018.GA18342@deneb.enyo.de>,
> >Florian Weimer <fw@deneb.enyo.de> wrote:
> >| Soeren Sonnenburg wrote:
> >|
> >| > losetup -e blowfish /dev/loop0 /file
> >| > Password:
> >| > mkfs -t ext3 /dev/loop0
> >| > mount /dev/loop0 /mnt
> >| > <error unknown fs type>
> >| > <from here something was seriously broken... could not reboot anymore>
> >|
> >| I'm seeing something similar, but in my case, mke2fs already crashes.
> >|
> >| > system is:
> >| > Linux no 2.6.0-test7 #8 Sun Oct 26 17:00:49 CET 2003 ppc GNU/Linux
> >|
> >| Mine ist -test9 on x86.
> >|
> >| Have you found a solution in the meantime?
> >
> >I have been using aes and not seeing this. I suppose it's unlikely that
> >there could be an error in the kernel crypto, but I think I'll wait and
> >try blowfish on a non-critical machine.
>
> My solution has been to not use cryptofs, it crashes with whatever
> algorithm I choose :-(
I've been using 'highmem=off' until now, which provided a workaround.
Just built 2.6.1-rc1-mm2 and cryptloop+highmem works as it should now.
- peter.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-06 10:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 7:09 loopback device + crypto = crash on 2.6.0-test7 ? Soeren Sonnenburg
2003-11-07 14:01 ` Bill Davidsen
2003-11-09 13:10 ` Florian Weimer
2003-11-09 12:23 ` Soeren Sonnenburg
2003-11-10 22:41 ` bill davidsen
2003-11-10 23:27 ` Peter Lieverdink
2003-11-10 23:46 ` bill davidsen
2003-11-11 0:15 ` Linus Torvalds
2003-11-11 8:54 ` Florian Weimer
2003-11-11 2:50 ` Valdis.Kletnieks
2003-11-11 9:43 ` Peter Lieverdink
2003-11-11 16:49 ` Linus Torvalds
2003-11-16 8:46 ` Peter Lieverdink
2004-01-06 10:36 ` Peter Lieverdink [this message]
2004-01-06 10:53 ` Matthias Hentges
-- strict thread matches above, loose matches on Subject: below --
2003-11-15 13:13 Jindrich Makovicka
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=1073385390.1110.2.camel@kahlua \
--to=peter@cc.com.au \
--cc=akpm@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.