| 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
| ||
|
Message-ID: <Pine.LNX.4.64.0704061314400.23939@schroedinger.engr.sgi.com> Date: Fri, 6 Apr 2007 13:28:13 -0700 (PDT) From: Christoph Lameter <clameter@....com> To: Andrew Morton <akpm@...ux-foundation.org> cc: Hugh Dickins <hugh@...itas.com>, Nick Piggin <npiggin@...e.de>, dgc@....com, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/2] Make page->private usable in compound pages V1 On Fri, 6 Apr 2007, Andrew Morton wrote: > > Both SLAB and SLUB use compound pages. > > Not really. slab sets the page->lru.prev of each constituent page to point > at the controlling slab. Uhh.. More slab inconsistencies. page[1]->lru is used for compound pages in the !MMU case. >From page_alloc.c: /* * Higher-order pages are called "compound pages". They are structured thusly: * * The first tail page's ->lru.next holds the address of the compound page's * put_page() function. Its ->lru.prev holds the order of allocation. * This usage means that zero-order pages may not be compound. */ > Will slub handle NOMMU anonymous pages appropriately? I am not sure how anonymous pages relate to the slab allocators. SLUB consistently uses compound pages for all higher order allocations. And those are usually fine for mmu and no mmu even without this series of patches unless someone pokes around page->private. - 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/
Powered by blists - more mailing lists