linux-kernel - Re: [Xen-devel] [PATCH] extend_brk and fixes to users of extend

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: <501826EF0200007800091AE9@nat28.tlf.novell.com>
Date:	Tue, 31 Jul 2012 17:41:51 +0100
From:	"Jan Beulich" <JBeulich@...e.com>
To:	"Konrad Rzeszutek Wilk" <konrad.wilk@...cle.com>
Cc:	<Ian.Campbell@...rix.com>, <x86@...nel.org>,
	<xen-devel@...ts.xensource.com>, <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [Xen-devel] [PATCH] extend_brk and fixes to users of
 extend_brk (v1).

>>> On 31.07.12 at 18:15, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> wrote:
> On Tue, Jul 31, 2012 at 08:49:21AM -0700, H. Peter Anvin wrote:
>> This means you're either abusing the brk allocator to do something
>> it is not meant to do... which may mean you can a failure in *other*
>> code, or you have a bug in your code that you haven't fixed.
> 
> Its the latter - and of one of the patches in this patchset fixes that.

But then you also can't assume that fitting a 2Gb MMIO hole will
suffice; I have a machine here that I can configure to have a
3Gb hole, so I think you really need to be on the safe side and
allow to cover all the way up to 4Gb with the space you reserve.

Jan

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