From: Brian Gerst <bgerst@didntduck.org>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: jmorris@redhat.com, davem@davemloft.net,
linux-kernel@vger.kernel.org, Oleg Makarenko <mole@quadra.ru>
Subject: Re: using crypto_digest() on non-kmalloc'd memory failures
Date: Mon, 18 Oct 2004 16:30:12 -0400 [thread overview]
Message-ID: <417427D4.6080704@didntduck.org> (raw)
In-Reply-To: <20041018192952.GB8607@lists.us.dell.com>
Matt Domsch wrote:
> James, David,
>
> Oleg noted that when we call crypto_digest() on memory allocated as a
> static array in a module, rather than kmalloc(GFP_KERNEL), it returns
> incorrect data, and with other functions, a kernel panic.
>
> Thoughts as to why this may be? Oleg's test patch appended.
>
On some arches modules reside in vmalloc space.
--
Brian Gerst
next prev parent reply other threads:[~2004-10-18 20:33 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
2004-10-18 23:04 ` James Morris
2004-10-19 5:41 ` Oleg Makarenko
2004-10-18 20:30 ` Brian Gerst [this message]
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=417427D4.6080704@didntduck.org \
--to=bgerst@didntduck.org \
--cc=Matt_Domsch@dell.com \
--cc=davem@davemloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.