From: Matt Domsch <Matt_Domsch@dell.com>
To: linux-ppp@vger.kernel.org
Subject: Re: [pptp-devel] ppp_mppe status for 2.6.x kernels
Date: Wed, 13 Oct 2004 02:49:17 +0000 [thread overview]
Message-ID: <20041013024917.GA16659@lists.us.dell.com> (raw)
In-Reply-To: <20041012220528.GA7876@lists.us.dell.com>
On Tue, Oct 12, 2004 at 05:05:28PM -0500, Matt Domsch wrote:
> Quick update on the state of ppp_mppe in kernel 2.6.x. Works for me,
> but more testers are needed, please test and post your results to
> these lists.
>
> BK:
> http://mdomsch.bkbits.net/linux-2.6-mppe
It would help if I actually freed the newly allocated sha_pad
struct... I pushed this into the above BK tree.
Oleg, Frank, I'm going to need to get a "Signed-of-by:" line for each
of you for final patch submission. See
linux/Documentation/SubmittingPatches for the format and what you're
agreeing to.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
ChangeSet@1.2167, 2004-10-12 18:00:10-05:00, Matt_Domsch@dell.com
ppp_mppe: free sha_pad properly
Signed-off-by: Matt Domsch <Matt_Domsch@dell.com>
ppp_mppe.c | 3 +++
1 files changed, 3 insertions
diff -Nru a/drivers/net/ppp_mppe.c b/drivers/net/ppp_mppe.c
--- a/drivers/net/ppp_mppe.c 2004-10-12 21:44:58 -05:00
+++ b/drivers/net/ppp_mppe.c 2004-10-12 21:44:58 -05:00
@@ -708,6 +708,8 @@
if (answer = 0)
printk(KERN_INFO "PPP MPPE Compression module registered\n");
+ else
+ kfree(sha_pad);
return answer;
}
@@ -715,6 +717,7 @@
static void __exit ppp_mppe_cleanup(void)
{
ppp_unregister_compressor(&ppp_mppe);
+ kfree(sha_pad);
}
module_init(ppp_mppe_init);
next prev parent reply other threads:[~2004-10-13 2:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 22:05 ppp_mppe status for 2.6.x kernels Matt Domsch
2004-10-13 2:49 ` Matt Domsch [this message]
2004-10-13 10:47 ` Michael Tokarev
2004-10-13 16:41 ` [pptp-devel] " Matt Domsch
2004-10-14 4:39 ` Paul Mackerras
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=20041013024917.GA16659@lists.us.dell.com \
--to=matt_domsch@dell.com \
--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.