Bug#351393: [Pkg-cryptsetup-devel] Bug#351393: Might as well close this

[Jonas Meurer]

On 04/03/2006 Sam Morris wrote:
> A few days after running into this bug I upgraded my system, and I now 
> use swap partitions instead of files.
> 
> For the sake of anyone else who runs into this problem, I had 512 MB of 
> RAM and a 1 GB swap file, /swap.

do you mean, that you cannot reproduce this bug any more?

or did you simply change your system setup, and therefore not any longer
suffer from the bug?

if this bug still applies for you when using an encrypted swap file, how
exactly does the crash look like? do you get any messages, is the screen
frozen, or are you still able to press enter, but the system simply
doesn't respond.

i tried to reproduce this bug, used a 1 GB encrypted swap file at /swap,
and ran
$ perl -e '@foo = (); push(@foo, "x"x1000) for (1..10**5); fork for (1..10**5); sleep 60'

i've 512 MB RAM too, and my system crashed too in some way. it simply
didn't respond, but still printed the keyboard keys i pressed. only it
didn't recognize them.
with a normal 1GB swap partition (not encrypted), and even with an
unencrypted 1GB swap file, the same command doesn't "crash" my system.
i'll try with an unencrypted 1GB swap file now, and we'll see.

i don't use darcs, so i cannot really simulate the same environment as
yours, but it seems like i was able to reproduce your bug.

it would be great, if you could try to reproduce the bug (best with
cryptsetup 1.0.2+1.0.3-rc2-1) by running the perl command above.

also, could you provide more information about your system? i.e. which
kernel version did you use, which architecture are you running, etc.

...
 jonas