From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: cryptoloop support broken in 2.6.3-ben2
Date: Sun, 07 Mar 2004 12:22:45 +0100 [thread overview]
Message-ID: <1078658565.3047.4.camel@localhost> (raw)
Hi..
copying something to a cryptoloop file crashes the machine (random
crashes), this is similiar to the report I send for 2.6.0-test11... it
was working with the 2.6.0-test10-mm1 loop-* patches and IIRC with
2.6.1.
Now it is broken again, not sure whether this is due to the big
endianness of this machine.
To crash do:
dd if=/dev/zero of=/file bs=1M count=100
losetup -e blowfish /dev/loop0 /file
Password:
mkfs -t ext3 /dev/loop0
mount /dev/loop0 /mnt
cd /mnt
dd if=/dev/zero of=bla
Soeren.
reply other threads:[~2004-03-07 11:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1078658565.3047.4.camel@localhost \
--to=kernel@nn7.de \
--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.