[PATCH v2] mm: make apply_to_page_range more robust

From: Mika PenttilÃ
Date: Wed Jan 20 2016 - 00:50:00 EST

Recent changes (4.4.0+) in module loader triggered oops on ARM.

can be 0 triggering the bug BUG_ON(addr >= end);.

The call path is SyS_init_module()->set_memory_xx()->apply_to_page_range(),
and apply_to_page_range gets zero length resulting in triggering :

BUG_ON(addr >= end)

This is a consequence of changes in module section handling (Rusty CC:ed).
This may be triggable only with certain modules and/or gcc versions.

Plus, I think the spirit of the BUG_ON is to catch overflows,
not to bug on zero length legitimate callers. So whatever the
reason for this triggering, some day we have another caller with
zero length.

Fix by letting call with zero size succeed.

v2: add more explanation

Signed-off-by: Mika Penttilà mika.penttila@xxxxxxxxxxxx
Reviewed-by: Pekka Enberg <penberg@xxxxxxxxxx>

diff --git a/mm/memory.c b/mm/memory.c
index c387430..c3d1a2e 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -1884,6 +1884,9 @@ int apply_to_page_range(struct mm_struct *mm, unsigned long addr,
unsigned long end = addr + size;
int err;

+ if (!size)
+ return 0;
BUG_ON(addr >= end);
pgd = pgd_offset(mm, addr);
do {