linux-kernel - Re: [patch] slub: fix per cpu kmem_cache

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1233134864.16201.3.camel@penberg-laptop>
Date:	Wed, 28 Jan 2009 11:27:44 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Christoph Lameter <cl@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch] slub: fix per cpu kmem_cache_cpu array memory leak

Hi David,

On Wed, 28 Jan 2009, Pekka Enberg wrote:
> > Btw, did you hit this bug during testing or did you just spot it
> > during review? That is, do we need to get this to -stable? 

On Wed, 2009-01-28 at 01:20 -0800, David Rientjes wrote:
> I ran into it while hacking the per cpu arrays, but haven't witnessed it 
> on a vanilla kernel.  Since there are no guarantees that a kmem_cache_cpu 
> will not be allocated on this boundary, I would recommend it for -stable.

Documentation/stable_kernel_rules.txt states that:

 - It must fix a real bug that bothers people (not a, "This could be a
   problem..." type thing).

The bug has been there for a very long time and hasn't generated any bug
reports so I think I'll just push it to mainline and leave it that. 

Thanks!

		Pekka

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