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]
Date:	Tue, 01 May 2007 12:40:55 -0400
From:	Chuck Ebbert <cebbert@...hat.com>
To:	Bill Irwin <bill.irwin@...cle.com>,
	Chuck Ebbert <cebbert@...hat.com>,
	linux-kernel@...r.kernel.org, bunk@...sta.de, akpm@...l.org,
	gcoady@...il.com, zlynx@....org, dgc@....com,
	alan@...rguk.ukuu.org.uk, andi@...stfloor.org, hch@...radead.org,
	jengelh@...ux01.gwdg.de, zwane@...radead.org, neilb@...e.de,
	jens.axboe@...cle.com, eric@...venscaling.com
Subject: Re: [3/3] use vmalloc() to arrange guard pages for stacks

Bill Irwin wrote:
> 
> It's a shame that the resource scalability implications of vmallocspace
> allocations prevent this from being useful in production. One could, in
> principle, establish guard pages within ZONE_NORMAL, but for 4KB stacks
> it's somewhat awkward to dredge up 3 contigous pages, and 4 defeats the
> purpose. Alignment with 8KB stacks wants 2 contiguous order 1 pages that
> span an order 2 page boundary. I guess I could rewrite the page allocator
> (again), but people seem to feel safest with the buddy allocator affairs.
> 
> BTW, did the original patches for this prove to be of any use to you?
> 

No, I never tried them. Seems like I never get to anything these days but
answering bug reports and merging fixes... Putting the feature in-kernel
means I might get to use it though. :)
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ