From: Jean-Luc Cooke <jlcooke@certainkey.com>
To: Christophe Saout <christophe@saout.de>
Cc: Andrew Morton <akpm@osdl.org>,
jmorris@intercode.com.au, linux-kernel@vger.kernel.org
Subject: Re: cryptoapi highmem bug
Date: Wed, 25 Feb 2004 15:12:16 -0500 [thread overview]
Message-ID: <20040225201216.GA6799@certainkey.com> (raw)
In-Reply-To: <20040225181540.GB8983@leto.cs.pocnet.net>
On Wed, Feb 25, 2004 at 07:15:40PM +0100, Christophe Saout wrote:
> Ok, here it is. Still working (when not using omac or hmac) after
> fixing the compile problems (see other mail).
>
> If this is ok someone should split out the scatterwalk_* move from
> your patch and submit it and this one to Andrew so that dm-crypt
> doesn't go boom on highmem machines.
Great thanks a bunch.
Here is the scatterlist+"Le Patch de Christophe":
http://jlcooke.ca/lkml/cryptowalk_christophe_25feb2004.patch
Reguarding dm-crypt:
I didn't get a response back when suggesting we store IV and MAC info for
each block. Can we do this? Can I do this? Where's the source, in
2.3.6-main? I'd like to implement this IV and optional OMAC stuff for
encrypted filesyetems (I assume that's that dm-crypt is replacing)
JLC
--
http://www.certainkey.com
Suite 4560 CTTC
1125 Colonel By Dr.
Ottawa ON, K1S 5B6
next prev parent reply other threads:[~2004-02-25 20:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 20:49 cryptoapi highmem bug Christophe Saout
2004-02-24 22:34 ` Jean-Luc Cooke
2004-02-24 23:01 ` Christophe Saout
2004-02-25 4:32 ` Jean-Luc Cooke
2004-02-25 6:00 ` Andrew Morton
2004-02-25 13:27 ` James Morris
2004-02-25 15:17 ` Jean-Luc Cooke
2004-02-25 19:50 ` Andrew Morton
2004-02-25 21:27 ` Christophe Saout
2004-02-25 21:41 ` Jean-Luc Cooke
2004-02-25 22:55 ` [PATCH 1/2] move scatterwalk functions to own file Christophe Saout
2004-02-25 22:55 ` [PATCH 2/2] fix in-place de/encryption bug with highmem Christophe Saout
2004-02-26 4:13 ` James Morris
2004-02-26 11:03 ` Christophe Saout
2004-02-25 15:31 ` cryptoapi highmem bug Christophe Saout
2004-02-25 15:51 ` Christophe Saout
2004-02-25 15:44 ` Jean-Luc Cooke
2004-02-25 16:13 ` Christophe Saout
2004-02-25 16:09 ` Jean-Luc Cooke
2004-02-25 18:11 ` cryptoapi OMAC (was: cryptoapi highmem bug) Christophe Saout
2004-02-25 20:59 ` Jean-Luc Cooke
2004-02-25 21:44 ` Christophe Saout
2004-02-25 18:15 ` cryptoapi highmem bug Christophe Saout
2004-02-25 20:12 ` Jean-Luc Cooke [this message]
2004-02-25 20:39 ` Christophe Saout
2004-02-25 20:46 ` Jean-Luc Cooke
2004-02-25 21:36 ` Christophe Saout
2004-02-25 21:52 ` Jean-Luc Cooke
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=20040225201216.GA6799@certainkey.com \
--to=jlcooke@certainkey.com \
--cc=akpm@osdl.org \
--cc=christophe@saout.de \
--cc=jmorris@intercode.com.au \
--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