linux-kernel - Re: [RFC/PATCH 3/3] SLOB: make ksize() more strict for page allocator pass-through

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] [day] [month] [year] [list]

Date:	Wed, 21 May 2008 14:16:40 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Pekka Enberg <penberg@...helsinki.fi>
cc:	Matt Mackall <mpm@...enic.com>, linux-kernel@...r.kernel.org,
	lethal@...ux-sh.org, dhowells@...hat.com
Subject: Re: [RFC/PATCH 3/3] SLOB: make ksize() more strict for page allocator
 pass-through

On Thu, 22 May 2008, Pekka Enberg wrote:

> Christoph Lameter wrote:
> > I also would prefer to keep this out of SLUB. Set/Clear PageSlab dirties the
> > cacheline and it forces the unlining of kmalloc_large.
> 
> Hmm, well, that leaves ksize() open for more abuse. I guess we'll just have to
> live with that then.

SLUB could add a BUG_ON(!PageCompound ) since we added buffering for order 
0 allocs. So only order 1 and higher go through kmalloc large. That should 
catch the general case.


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