Re: [PATCH] [SECURITY, 2.4] Avoid 'names_cache' memory leak with CONFIG_AUDITSYSCALL

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.....


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] [SECURITY, 2.4] Avoid 'names_cache' memory leak with CONFIG_AUDITSYSCALL
    • From: Horms <[email protected]>

• References:
  • [PATCH] [SECURITY, 2.4] Avoid 'names_cache' memory leak with CONFIG_AUDITSYSCALL
    • From: Horms <[email protected]>

• Prev by Date: Re: Call for PIIX4 chipset testers
• Next by Date: Re: [PATCH] DRIVER MODEL: Get rid of the obsolete tri-level suspend/resume callbacks
• Previous by thread: [PATCH] [SECURITY, 2.4] Avoid 'names_cache' memory leak with CONFIG_AUDITSYSCALL
• Next by thread: Re: [PATCH] [SECURITY, 2.4] Avoid 'names_cache' memory leak with CONFIG_AUDITSYSCALL
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]