diff options
| author | Rui Miguel Silva <rui.silva@linaro.org> | 2018-02-09 10:59:08 +0000 |
|---|---|---|
| committer | Bryan O'Donoghue <bryan.odonoghue@linaro.org> | 2019-05-01 11:51:22 +0100 |
| commit | 98b3b4ab29b851335051fb9447c468ffb79649b9 (patch) | |
| tree | a7eea9e2d0d6472856395c5deaf02f0c52dfe3bc | |
| parent | 964b198482b0189431800e8548b65b984bd7d377 (diff) | |
mm: Drop "PFNs busy" printk in an expected path
For CMA allocations, we expect to occasionally hit this error path, at
which point CMA will retry. Given that, we shouldn't be spamming
dmesg about it.
This is based on the discussion here:
https://patchwork.kernel.org/patch/9490969/
Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
| -rw-r--r-- | mm/page_alloc.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 923deb33bf34..3874602cf38f 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -7618,8 +7618,6 @@ int alloc_contig_range(unsigned long start, unsigned long end, /* Make sure the range is really isolated. */ if (test_pages_isolated(outer_start, end, false)) { - pr_info_ratelimited("%s: [%lx, %lx) PFNs busy\n", - __func__, outer_start, end); ret = -EBUSY; goto done; } |