summaryrefslogtreecommitdiffstats
path: root/mm/vmalloc.c
diff options
context:
space:
mode:
authorFlorian Fainelli <f.fainelli@gmail.com>2017-04-27 11:19:00 -0700
committerCatalin Marinas <catalin.marinas@arm.com>2017-05-11 14:41:26 +0100
commit03497d761c55438144fd63534d4223418fdfd345 (patch)
tree05cf30cdf2a6285de419802147c7bf1140f4bf9d /mm/vmalloc.c
parentd135b8b5060ea91dd751ff172d179eb4eab1e966 (diff)
downloadop-kernel-dev-03497d761c55438144fd63534d4223418fdfd345.zip
op-kernel-dev-03497d761c55438144fd63534d4223418fdfd345.tar.gz
mm: Silence vmap() allocation failures based on caller gfp_flags
If the caller has set __GFP_NOWARN don't print the following message: vmap allocation for size 15736832 failed: use vmalloc=<size> to increase size. This can happen with the ARM/Linux or ARM64/Linux module loader built with CONFIG_ARM{,64}_MODULE_PLTS=y which does a first attempt at loading a large module from module space, then falls back to vmalloc space. Acked-by: Michal Hocko <mhocko@suse.com> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'mm/vmalloc.c')
-rw-r--r--mm/vmalloc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 0b05762..b74f1d0 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -521,7 +521,7 @@ overflow:
}
}
- if (printk_ratelimit())
+ if (!(gfp_mask & __GFP_NOWARN) && printk_ratelimit())
pr_warn("vmap allocation for size %lu failed: use vmalloc=<size> to increase size\n",
size);
kfree(va);
OpenPOWER on IntegriCloud