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: Sat, 8 Jun 2019 09:49:59 +0200 From: Borislav Petkov <bp@...e.de> To: Baoquan He <bhe@...hat.com> Cc: tglx@...utronix.de, stable@...r.kernel.org, mingo@...nel.org, x86@...nel.org, linux-kernel@...r.kernel.org, peterz@...radead.org, keescook@...omium.org, luto@...nel.org, hpa@...or.com, kirill@...ux.intel.com, dave.hansen@...ux.intel.com, linux-tip-commits@...r.kernel.org Subject: Re: [tip:x86/urgent] x86/mm/KASLR: Compute the size of the vmemmap section properly On Sat, Jun 08, 2019 at 10:14:04AM +0800, Baoquan He wrote: > Here, 4PB = 4*2^50 = 4*1024^5, the vmemmap should be 64 TB, am I right? PB is 1000^5 petabytes. 1024^5 is PiB or pebibytes. https://en.wikipedia.org/wiki/Petabyte -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nürnberg) --
Powered by blists - more mailing lists