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: Tue, 7 Jul 2020 17:13:52 +0800 From: Tian Tao <tiantao6@...ilicon.com> To: <akpm@...ux-foundation.org>, <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org> CC: <linuxarm@...wei.com> Subject: [PATCH] vmalloc: Removing incorrect logs when vmalloc failed It is not possible to increase size with vmalloc=<size> in arm64 architecture and it will mislead.however vmalloc return failure is a rare occurrence in 'many architectures including arm64'. Signed-off-by: Tian Tao <tiantao6@...ilicon.com> --- mm/vmalloc.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 89e83d3..c7b5a9a 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@ -1238,8 +1238,7 @@ static struct vmap_area *alloc_vmap_area(unsigned long size, } if (!(gfp_mask & __GFP_NOWARN) && printk_ratelimit()) - pr_warn("vmap allocation for size %lu failed: use vmalloc=<size> to increase size\n", - size); + pr_warn("vmap allocation for size %lu failed\n", size); kmem_cache_free(vmap_area_cachep, va); return ERR_PTR(-EBUSY); -- 2.7.4
Powered by blists - more mailing lists