All of lore.kernel.org
 help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [SECURITY, 2.4]  Avoid 'names_cache' memory leak with CONFIG_AUDITSYSCALL
Date: Sat, 29 Oct 2005 12:42:58 +0900	[thread overview]
Message-ID: <20051029034258.GM4961@verge.net.au> (raw)
In-Reply-To: <1130493647.2800.17.camel@laptopd505.fenrus.org>

On Fri, Oct 28, 2005 at 12:00:46PM +0200, Arjan van de Ven wrote:
> On Fri, 2005-10-28 at 18:27 +0900, Horms wrote:
> > This is CAN-2005-3181, and a backport of
> > 829841146878e082613a49581ae252c071057c23 from Linus's 2.6 tree to 2.4.
> > 
> > Original Description and Sign-Off:
> > 
> > Avoid 'names_cache' memory leak with CONFIG_AUDITSYSCALL
> > 
> > The nameidata "last.name" is always allocated with "__getname()", and
> > should always be free'd with "__putname()".
> > 
> > Using "putname()" without the underscores will leak memory, because the
> > allocation will have been hidden from the AUDITSYSCALL code.
> 
> > My sign off, indicating I think it applies to 2.4:
> 
> 
> since there is no such thing as CONFIG_AUDITSYSCALL in any 2.4 kernel, I
> really think this is entirely NOT relevant to 2.4.....

Thanks, I withdraw the patch.

-- 
Horms

      reply	other threads:[~2005-10-29  4:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28  9:27 [PATCH] [SECURITY, 2.4] Avoid 'names_cache' memory leak with CONFIG_AUDITSYSCALL Horms
2005-10-28 10:00 ` Arjan van de Ven
2005-10-29  3:42   ` Horms [this message]

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=20051029034258.GM4961@verge.net.au \
    --to=horms@verge.net.au \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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 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.