From: Thomas Themel <themel@iwoars.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: cryptoloop data corruption (was Re: Device-backed loop broken in 2.6.0-test2?)
Date: Sat, 9 Aug 2003 22:48:54 +0200 [thread overview]
Message-ID: <20030809204854.GA16573@iwoars.net> (raw)
In-Reply-To: <20030806174043.27fd674a.akpm@osdl.org>
Andrew Morton (akpm@osdl.org) wrote on 2003-08-07:
> Thomas Themel <themel@iwoars.net> wrote:
> > it seems that device backed loopback is broken in the 2.6.0-test2 series.
>
> doh.
Hm, it seems that this patch doesn't apply to 2.6.0-test3, so I assume
that the 'other fix' from -mm5 is included?
I still get data corruption on cryptoloop, but now it is a bit more
subtle... One bit of every byte at multiples of 0x200 is flipped,
starting with the one at 0x1000.
See this for a short example (xxd output of file before and after copy
to cryptoloop):
--- good.xxd 2003-08-09 22:33:21.000000000 +0200
+++ b0rk.xxd 2003-08-09 22:32:59.000000000 +0200
@@ -256,3 +256,3 @@
0000ff0: ffff ffff ffff ffff ffff ffff ffff ffff ................
-0001000: ffff ffff ffff ffff ffff ffff ffff ffff ................
+0001000: f7ff ffff ffff ffff ffff ffff ffff ffff ................
0001010: ffff ffff ffff ffff ffff ffff ffff ffff ................
@@ -288,3 +288,3 @@
00011f0: 0ae0 004b 0000 0000 0000 0960 0000 0000 ...K.......`....
-0001200: 0001 2c00 0000 0000 0025 8000 0000 ffff ..,......%......
+0001200: 0801 2c00 0000 0000 0025 8000 0000 ffff ..,......%......
0001210: ffff ffff ffff ffff ffff ffff ffff ffff ................
@@ -320,3 +320,3 @@
00013f0: ffff ffff ffff ffff ffff ffff ffff ffff ................
-0001400: ffff ffff ffff ffff ffff ffff ffff ffff ................
+0001400: f7ff ffff ffff ffff ffff ffff ffff ffff ................
0001410: ffff ffff ffff ffff ffff ffff ffff ffff ................
@@ -352,3 +352,3 @@
00015f0: ffff ffff ffff ffff ffff ffff ffff ffff ................
-0001600: ffff ffff ffff ffff ffff ffff ffff ffff ................
Any ideas what's causing this? The files are ext3 on an AES cryptoloop
backed by an IDE partition.
ciao,
--
[*Thomas Themel*] US law prohibits boycotting Israel
[extended contact]
[info provided in] <http://news.bbc.co.uk/2/hi/business/2403303.stm>
[*message header*] <http://www.bxa.doc.gov/AntiboycottCompliance/Default.htm>
prev parent reply other threads:[~2003-08-09 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 22:40 Device-backed loop broken in 2.6.0-test2? Thomas Themel
2003-08-07 0:40 ` Andrew Morton
2003-08-07 7:23 ` Thomas Themel
2003-08-07 16:07 ` Valdis.Kletnieks
2003-08-07 16:24 ` Valdis.Kletnieks
2003-08-07 16:29 ` Andrew Morton
2003-08-09 20:48 ` Thomas Themel [this message]
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=20030809204854.GA16573@iwoars.net \
--to=themel@iwoars.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox