| 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
| ||
|
Message-Id: <1344244999-5081-23-git-send-email-laijs@cn.fujitsu.com> Date: Mon, 6 Aug 2012 17:23:16 +0800 From: Lai Jiangshan <laijs@...fujitsu.com> To: Mel Gorman <mel@....ul.ie>, linux-kernel@...r.kernel.org Cc: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>, Lai Jiangshan <laijs@...fujitsu.com>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org, Jarkko Sakkinen <jarkko.sakkinen@...el.com>, Matt Fleming <matt.fleming@...el.com>, Andrew Morton <akpm@...ux-foundation.org> Subject: [RFC V3 PATCH 22/25] x86: use memblock_set_current_limit() to set memblock.current_limit From: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com> memblock.current_limit is set directly though memblock_set_current_limit() is prepared. So fix it. Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com> Signed-off-by: Lai Jiangshan <laijs@...fujitsu.com> --- arch/x86/kernel/setup.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c index f4b9b80..bb9d9f8 100644 --- a/arch/x86/kernel/setup.c +++ b/arch/x86/kernel/setup.c @@ -889,7 +889,7 @@ void __init setup_arch(char **cmdline_p) cleanup_highmap(); - memblock.current_limit = get_max_mapped(); + memblock_set_current_limit(get_max_mapped()); memblock_x86_fill(); /* @@ -925,7 +925,7 @@ void __init setup_arch(char **cmdline_p) max_low_pfn = max_pfn; } #endif - memblock.current_limit = get_max_mapped(); + memblock_set_current_limit(get_max_mapped()); dma_contiguous_reserve(0); /* -- 1.7.4.4 -- 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