linux-kernel - Re: [PATCH,RFC] Add __GFP_ZERO to GFP_LEVEL

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]

Message-Id: <20061013143107.1e8fcb00.akpm@osdl.org>
Date:	Fri, 13 Oct 2006 14:31:07 -0700
From:	Andrew Morton <akpm@...l.org>
To:	corbet@....net (Jonathan Corbet)
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH,RFC] Add __GFP_ZERO to GFP_LEVEL_MASK

On Fri, 13 Oct 2006 15:00:22 -0600
corbet@....net (Jonathan Corbet) wrote:

> Andrew Morton <akpm@...l.org> wrote:
> 
> > It would be a bit odd to pass __GFP_ZERO into the slab allocator.  Slab
> > doesn't need that hint: it has its own ways of initialising the memory.
> > 
> > What is the callsite?
> 
> It's vmalloc_user(), which does this:
> 
>   ret = __vmalloc(size, GFP_KERNEL | __GFP_HIGHMEM | __GFP_ZERO, PAGE_KERNEL);
> 

oic, yes, that was a recent change.

I guess this will do the trick?


diff -puN mm/vmalloc.c~vmalloc-dont-pass-__gfp_zero-to-slab mm/vmalloc.c
--- a/mm/vmalloc.c~vmalloc-dont-pass-__gfp_zero-to-slab
+++ a/mm/vmalloc.c
@@ -428,8 +428,11 @@ void *__vmalloc_area_node(struct vm_stru
 	if (array_size > PAGE_SIZE) {
 		pages = __vmalloc_node(array_size, gfp_mask, PAGE_KERNEL, node);
 		area->flags |= VM_VPAGES;
-	} else
-		pages = kmalloc_node(array_size, (gfp_mask & ~__GFP_HIGHMEM), node);
+	} else {
+		pages = kmalloc_node(array_size,
+				(gfp_mask & ~(__GFP_HIGHMEM | __GFP_ZERO)),
+				node);
+	}
 	area->pages = pages;
 	if (!area->pages) {
 		remove_vm_area(area->addr);
_



(hmm, __vmalloc_area_node and __vmalloc_node are mutually recursive. ick.)
-
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/