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: Wed, 20 Jan 2010 13:50:16 -0600 (CST) From: Christoph Lameter <cl@...ux-foundation.org> To: Yinghai Lu <yinghai@...nel.org> cc: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>, "H. Peter Anvin" <hpa@...or.com>, Andrew Morton <akpm@...ux-foundation.org>, Jesse Barnes <jbarnes@...tuousgeek.org>, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org Subject: Re: [PATCH 02/37] x86: check range in update range On Wed, 20 Jan 2010, Yinghai Lu wrote: > On 01/19/2010 08:56 AM, Christoph Lameter wrote: > > On Fri, 15 Jan 2010, Yinghai Lu wrote: > > > >> fend off wrong range > > > > Why is it ok now to call these functions with start >= end? Bootmem > > compatibilty? > > and amd_bus/intel_bus etc will be use 32bit etc Can you be more detailed? -- 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