From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: Chris Wright <chrisw@osdl.org>
Cc: Steve G <linux_4ever@yahoo.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Trusted Path Execution LSM 0.2 (20050108)
Date: Tue, 11 Jan 2005 22:11:36 +0100 [thread overview]
Message-ID: <1105477896.24610.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20050111123320.S469@build.pdx.osdl.net>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
Hi,
El mar, 11-01-2005 a las 12:33 -0800, Chris Wright escribió:
> * Steve G (linux_4ever@yahoo.com) wrote:
> > This patch leaks memory in the error paths. For example:
> >
> > +static ssize_t trustedlistadd_read_file(struct tpe_list *list, char *buf)
> > +{
> > <snip>
> > + char *buffer = kmalloc(400, GFP_KERNEL);
> > +
> > + user = (char *)__get_free_page(GFP_KERNEL);
> > + if (!user)
> > + return -ENOMEM;
>
> Helps to inform the author ;-)
It's fixed now and i will update the patches ASAP.
Next time it would be better to CC me directly, but anyway, thanks for
reporting this, as much as you mess it up, it's as much as i will work
to make it better ;).
Cheers,
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org> [1024D/6F2B2DEC]
[2048g/9AE91A22] Hardened Debian head developer & project manager
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-11 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 19:55 Steve G
2005-01-11 20:33 ` Chris Wright
2005-01-11 21:11 ` Lorenzo Hernández García-Hierro [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-08 18:15 Lorenzo Hernández García-Hierro
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=1105477896.24610.14.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_4ever@yahoo.com \
/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®