| 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: Thu, 3 Sep 2015 09:00:28 +0100 From: Russell King - ARM Linux <linux@....linux.org.uk> To: Yongtaek Lee <ytk.lee@...sung.com> Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Nicolas Pitre <nicolas.pitre@...aro.org> Subject: Re: [PATCH] ARM: fix bug which VMALLOC_START is lowwer than 0xf0000000 On Thu, Sep 03, 2015 at 11:24:47AM +0900, Yongtaek Lee wrote: > default value of vmalloc_min was set 0xf0000000 for ARM by commit > 0536bdf3. But actually vmalloc_min is 0xef800000 not 0xf0000000. > > VMALLOC_END - (240 << 20) - VMALLOC_OFFSET) > 0xff000000 - 0x0f000000 - 0x00800000 = 0xef800000 > > In case of 768MB ram without CONFIG_HIGHMEM=y, last 8MB could not be > allocated. Kernel log also print out warning message as below. > "Truncating RAM at 80000000-afffffff to -af7fffff (vmalloc region overlap)." > > Although it could be solved by state "vmalloc=size" in cmdline but i think > it would be better to change default value to 232 from 240. > > Signed-off-by: Yongtaek Lee <ytk.lee@...sung.com> I fail to see what the problem is here. You're adjusting the size of the vmalloc space to accomodate the size of RAM you have. That's not a bug. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- 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