From: Fruhwirth Clemens <clemens-dated-1061346967.29a4@endorphin.org>
To: linux-kernel@vger.kernel.org
Cc: pascal.brisset-ml@wanadoo.fr, mbligh@aracnet.com,
kernel@gozer.org, axboe@suse.de
Subject: [PATCH] loop: fixing cryptoloop troubles.
Date: Sun, 10 Aug 2003 04:36:06 +0200 [thread overview]
Message-ID: <20030810023606.GA15356@ghanima.endorphin.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 442 bytes --]
In loop_transfer_bio the initial vector has been computed only once. For any
situation where more than one bio_vec is present the initial vector will be
wrong. Here is the trivial but important fix.
This will fix the disk corruption problems of cryptoloop for block-backed
loop devices mentioned earlier this month on this list.
This should close http://bugme.osdl.org/show_bug.cgi?id=1000
Please confirm.
Regards, Clemens
[-- Attachment #1.2: loop-2.6t2.diff --]
[-- Type: text/plain, Size: 310 bytes --]
--- linux-2.6.0-test2/drivers/block/loop.c~ Sun Jul 27 19:03:16 2003
+++ linux-2.6.0-test2/drivers/block/loop.c Sun Aug 10 04:22:44 2003
@@ -513,6 +513,7 @@
from_bvec->bv_len, IV);
kunmap(from_bvec->bv_page);
kunmap(to_bvec->bv_page);
+ IV += from_bvec->bv_len >> 9;
}
return ret;
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2003-08-10 2:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 2:36 Fruhwirth Clemens [this message]
2003-08-10 14:10 ` Pascal Brisset
2003-08-10 14:27 ` Christophe Saout
2003-08-10 21:03 ` Fruhwirth Clemens
2003-08-10 22:07 ` Christophe Saout
2003-08-11 13:11 ` Fruhwirth Clemens
2003-08-11 16:16 ` Christophe Saout
2003-08-12 3:30 ` David Wagner
2003-08-10 15:15 ` James Morris
2003-08-10 16:08 ` Pascal Brisset
2003-08-10 16:28 ` James Morris
2003-08-10 18:01 ` Ingo Oeser
2003-08-11 8:38 ` Pascal Brisset
2003-08-11 13:31 ` James Morris
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=20030810023606.GA15356@ghanima.endorphin.org \
--to=clemens-dated-1061346967.29a4@endorphin.org \
--cc=axboe@suse.de \
--cc=kernel@gozer.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=pascal.brisset-ml@wanadoo.fr \
/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
Powered by JetHome