From: Oleg Makarenko <mole@quadra.ru>
To: linux-ppp@vger.kernel.org
Subject: Re: [pptp-devel] Re: [2/2]: ppp_mppe inclusion
Date: Sun, 05 Sep 2004 18:23:15 +0000 [thread overview]
Message-ID: <413B5993.604@quadra.ru> (raw)
In-Reply-To: <20040720204723.GC27576@lists.us.dell.com>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hi Matt
Matt Domsch wrote:
>On Mon, Aug 30, 2004 at 05:42:05PM -0500, Matt Domsch wrote:
>
>
>>On Fri, Jul 30, 2004 at 11:33:09PM +0400, Oleg Makarenko wrote:
>>
>>
>>>2. For some reason you can not use non GFP_KERNEL memory and scatter
>>>lists or at least mix them in crypto_digest(). That is why sha_pad is
>>>now in struct state {}.
>>>
>>>
>
>Can you describe what happens when you do?
>
>
please try the attached patch for tcrypt.c to see what is going on
yourself. modrpobe the resulting module with mode=2 parameter to test
sha1 and see how it fails the tests.
For mode=0 (or without any parameter) you should get kernel panic.
=oleg
[-- Attachment #2: tcrypt.diff --]
[-- Type: text/x-patch, Size: 610 bytes --]
--- tcrypt.c.orig 2004-08-14 09:37:38.000000000 +0400
+++ tcrypt.c 2004-09-05 21:11:19.000000000 +0400
@@ -58,6 +58,8 @@
static char *xbuf;
static char *tvmem;
+static char tvmem_buf[TVMEMSIZE];
+
static char *check[] = {
"des", "md5", "des3_ede", "rot13", "sha1", "sha256", "blowfish",
"twofish", "serpent", "sha384", "sha512", "md4", "aes", "cast6",
@@ -820,7 +822,8 @@
static int __init
init(void)
{
- tvmem = kmalloc(TVMEMSIZE, GFP_KERNEL);
+ tvmem = &tvmem_buf[0];
+
if (tvmem == NULL)
return -ENOMEM;
@@ -833,7 +836,6 @@
do_test();
kfree(xbuf);
- kfree(tvmem);
return 0;
}
next prev parent reply other threads:[~2004-09-05 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 20:47 [2/2]: ppp_mppe inclusion Matt Domsch
2004-07-30 19:33 ` Oleg Makarenko
2004-07-31 18:34 ` Matt Domsch
2004-08-30 22:42 ` [pptp-devel] " Matt Domsch
2004-08-30 22:48 ` Matt Domsch
2004-08-31 22:23 ` Oleg Makarenko
2004-09-05 18:23 ` Oleg Makarenko [this message]
2004-10-12 17:14 ` 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=413B5993.604@quadra.ru \
--to=mole@quadra.ru \
--cc=linux-ppp@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 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.