linux-kernel - Re: [PATCH 0/5] make slab gfp fair

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: <Pine.LNX.4.64.0705141303570.12167@schroedinger.engr.sgi.com>
Date:	Mon, 14 May 2007 13:06:02 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
cc:	Matt Mackall <mpm@...enic.com>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, Thomas Graf <tgraf@...g.ch>,
	David Miller <davem@...emloft.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Daniel Phillips <phillips@...gle.com>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [PATCH 0/5] make slab gfp fair

On Mon, 14 May 2007, Peter Zijlstra wrote:

> > Hmmm.. Maybe we could do that.... But what I had in mind was simply to 
> > set a page flag (DebugSlab()) if you know in alloc_slab that the slab 
> > should be only used for emergency allocation. If DebugSlab is set then the
> > fastpath will not be called. You can trap all allocation attempts and 
> > insert whatever fancy logic you want in the debug path since its not 
> > performance critical.
> 
> I might have missed some detail when I looked at SLUB, but I did not see
> how setting SlabDebug would trap subsequent allocations to that slab.

Ok its not evident in slab_alloc. But if SlabDebug is set then 
page->lockless_list is always NULL and we always fall back to 
__slab_alloc. There we check for SlabDebug and go to the debug: label. 
There you can insert any fancy processing you want.

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