From: "David S. Miller" <davem@davemloft.net>
To: Oleg Makarenko <mole@quadra.ru>
Cc: jmorris@redhat.com, Matt_Domsch@dell.com, linux-kernel@vger.kernel.org
Subject: Re: using crypto_digest() on non-kmalloc'd memory failures
Date: Mon, 18 Oct 2004 13:16:53 -0700 [thread overview]
Message-ID: <20041018131653.5ac00165.davem@davemloft.net> (raw)
In-Reply-To: <41742215.8020005@quadra.ru>
On Tue, 19 Oct 2004 00:05:41 +0400
Oleg Makarenko <mole@quadra.ru> wrote:
> So to calculate digest on some static data I need to copy them to
> kmalloc'ed memory first, right?
>
> Can this copying be somehow avoided?
It is necessary to be able to kmap() the data item
passed into the crypto layer, so dynamically allocated
memory obtained via kmalloc() or similar must be used.
next prev parent reply other threads:[~2004-10-18 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 19:29 using crypto_digest() on non-kmalloc'd memory failures Matt Domsch
2004-10-18 19:35 ` James Morris
2004-10-18 20:05 ` Oleg Makarenko
2004-10-18 20:16 ` David S. Miller [this message]
2004-10-18 23:04 ` James Morris
2004-10-19 5:41 ` Oleg Makarenko
2004-10-18 20:30 ` Brian Gerst
2004-10-18 22:10 ` Gene Heskett
2004-10-18 22:29 ` dupes (was Re: using crypto_digest() on non-kmalloc'd memory failures) Matt Domsch
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=20041018131653.5ac00165.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Matt_Domsch@dell.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mole@quadra.ru \
/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