mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Cc: Matt Domsch <Matt_Domsch@dell.com>,
	jmorris@redhat.com, davem@davemloft.net,
	Oleg Makarenko <mole@quadra.ru>
Subject: Re: using crypto_digest() on non-kmalloc'd memory failures
Date: Mon, 18 Oct 2004 18:10:41 -0400	[thread overview]
Message-ID: <200410181810.41406.gene.heskett@verizon.net> (raw)
In-Reply-To: <20041018192952.GB8607@lists.us.dell.com>

On Monday 18 October 2004 15:29, 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.

Off topic Matt, but why am I getting 4 to 6 copies of the messages you 
send?  All identical time stamps, the whole works.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

  parent reply	other threads:[~2004-10-18 22:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18 19:29 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
2004-10-18 22:10 ` Gene Heskett [this message]
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=200410181810.41406.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®