| 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
| ||
|
Date: Fri, 17 Dec 2010 15:33:49 +0100 From: Stanislaw Gruszka <sgruszka@...hat.com> To: "tip-bot for H. Peter Anvin" <hpa@...ux.intel.com> Cc: linux-tip-commits@...r.kernel.org, linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com, yinghai@...nel.org, tglx@...utronix.de Subject: Re: [tip:x86/urgent] x86-32: Make sure we can map all of lowmem if we need to On Fri, Dec 17, 2010 at 03:19:03AM +0000, tip-bot for H. Peter Anvin wrote: > Commit-ID: 147dd5610c8d1bacb88a6c1dfdaceaf257946ed0 > Gitweb: http://git.kernel.org/tip/147dd5610c8d1bacb88a6c1dfdaceaf257946ed0 > Author: H. Peter Anvin <hpa@...ux.intel.com> > AuthorDate: Thu, 16 Dec 2010 19:11:09 -0800 > Committer: H. Peter Anvin <hpa@...ux.intel.com> > CommitDate: Thu, 16 Dec 2010 19:11:09 -0800 > > x86-32: Make sure we can map all of lowmem if we need to > > A relocatable kernel can be anywhere in lowmem -- and in the case of a > kdump kernel, is likely to be fairly high. Since the early page > tables map everything from address zero up we need to make sure we > allocate enough brk that we can map all of lowmem if we need to. > > Reported-by: Stanislaw Gruszka <sgruszka@...hat.com> Fix confirmed, thanks Stanislaw -- 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