From: Thiago Rondon <thiago@ananke.com.br>
To: Peter Lieverdink <cafuego@cafuego.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cryptoloop hard lockup 2.6.0-test5-mm4
Date: Tue, 23 Sep 2003 10:36:24 -0300 [thread overview]
Message-ID: <20030923133624.GA2479@ananke.com.br> (raw)
In-Reply-To: <5.1.0.14.2.20030923151949.01d37568@caffeine.cc.com.au>
Hi Peter,
Can you please test that?
--- mm/swapfile.c.orig 2003-09-23 09:34:16.000000000 -0400
+++ mm/swapfile.c 2003-09-23 09:34:39.000000000 -0400
@@ -1223,7 +1223,7 @@
unsigned int type;
int i, prev;
int error;
- static int least_priority;
+ static int least_priority = 0;
union swap_header *swap_header = 0;
int swap_header_version;
int nr_good_pages = 0;
On Tue, Sep 23, 2003 at 03:25:47PM +1000, Peter Lieverdink wrote:
> I just had a play with an article from an old LinuxJournal, to see if I
> could set up a cryptoloop homedir on my Debian unstable box. Found making
> an fs on the loop device locks the kernel hard. (need reset button) When
> using loopback without crypto it all works fine.
>
> Ayone else have the same experience?
>
> Using util-linux 2.12, aes (same prob with twofish, blowfish).
>
> Crash dump is attached, as is kernel config. When not running uml-switch,
> the crash still occurs but doesn't print the VM: messages. (I don't have a
> swap partition anyway, so what's that all about?)
>
> - Peter.
> kahlua:~# modprobe cryptoloop
> loop: loaded (max 8 devices)
> kahlua:~# modprobe aes
> kahlua:~# losetup -e aes -k 128 /dev/loop0 /home/cafuego.img
> kahlua:~# mkfs -t ext2 /dev/loop0
> mke2fs 1.35-WIP (21-Aug-2003)
> Filesystem label=
> OS type: Linux
> Block size=1024 (log=0)
> Fragment size=1024 (log=0)
> 131072 inodes, 524288 blocks
> 26214 blocks (5.00%) reserved for the super user
> First data block=1
> 64 block groups
> 8192 blocks per group, 8192 fragments per group
> 2048 inodes per group
> Superblock backups stored on blocks:
> 8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409
>
> Writing inode tables: done
> Writing superblocks and filesystem accounting information: do_wp_page: bogus page at address 0804d056
> VM: killing process uml_switch
> swap_dup: Bad swap file entry 90885fdb
> VM: killing process uml_switch
> swap_dup: Bad swap file entry 286be58f
> VM: killing process uml_switch
> Debug: sleeping fucntion called from invalid context at include/linux/rwsem.h:43
> in_atomic():0, irqs_disabled():1
> Call Trace:
--
-Thiago Rondon,
MAKETRADEFAIR.ORG
next prev parent reply other threads:[~2003-09-23 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 5:25 cryptoloop hard lockup 2.6.0-test5-mm4 Peter Lieverdink
2003-09-23 13:36 ` Thiago Rondon [this message]
2003-11-08 22:14 ` Florian Weimer
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=20030923133624.GA2479@ananke.com.br \
--to=thiago@ananke.com.br \
--cc=cafuego@cafuego.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