From: Andrew Morton <akpm@osdl.org>
To: James Morris <jmorris@redhat.com>
Cc: jlcooke@certainkey.com, christophe@saout.de,
linux-kernel@vger.kernel.org, adam@yggdrasil.com
Subject: Re: cryptoapi highmem bug
Date: Wed, 25 Feb 2004 11:50:27 -0800 [thread overview]
Message-ID: <20040225115027.580cc2ed.akpm@osdl.org> (raw)
In-Reply-To: <Xine.LNX.4.44.0402250825110.28907-100000@thoron.boston.redhat.com>
James Morris <jmorris@redhat.com> wrote:
>
> On Tue, 24 Feb 2004, Andrew Morton wrote:
>
> > Jean-Luc Cooke <jlcooke@certainkey.com> wrote:
> > >
> > > How do I check for equal real addresses from two virtual ones?
> >
> > I don't think there is a practical way of doing this. It would involve
> > comparing the virtual address with the kmap and atomic kmap regions,
> > performing a pagetable walk, extracting the pageframe. If the page is not
> > in a kmap area generate the pageframe directly. Make that work on all
> > architectures. Very yuk.
> >
> > If practical this API should have been defined in terms of
> > (page/offset/len) and it should have kmapped the pages itself. I guess
> > it's too late for that.
>
> Do you mean that the crypt() function should do kmapping?
Passing the page* down one more level would permit cbc_process() to get at
the pageframes themselves, so it can sanely determine if src and dest
overlap. (I assume this is for encryption-in-place).
Or maybe it's sufficient for crypt() to pass a simple boolean down to the
prfn() callout which says "this is in-place encryption".
next prev parent reply other threads:[~2004-02-25 19:53 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 [this message]
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
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=20040225115027.580cc2ed.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adam@yggdrasil.com \
--cc=christophe@saout.de \
--cc=jlcooke@certainkey.com \
--cc=jmorris@redhat.com \
--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