From: <mika.penttila@nextfour.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, linux@arm.linux.org.uk,
"Mika Penttilä" <mika.penttila@nextfour.com>
Subject: [PATCH 1/2 v2] arm, arm64: change_memory_common with numpages == 0 should be no-op.
Date: Tue, 26 Jan 2016 08:33:08 +0200 [thread overview]
Message-ID: <1453789989-13260-2-git-send-email-mika.penttila@nextfour.com> (raw)
In-Reply-To: <1453789989-13260-1-git-send-email-mika.penttila@nextfour.com>
From: Mika PenttilA? <mika.penttila@nextfour.com>
This makes the caller set_memory_xx() consistent with x86.
arm64 part is rebased on 4.5.0-rc1 with Ard's patch
lkml.kernel.org/g/<1453125665-26627-1-git-send-email-ard.biesheuvel@linaro.org>
applied.
Signed-off-by: Mika PenttilA? mika.penttila@nextfour.com
Reviewed-by: Laura Abbott <labbott@redhat.com>
Acked-by: David Rientjes <rientjes@google.com>
---
arch/arm/mm/pageattr.c | 3 +++
arch/arm64/mm/pageattr.c | 3 +++
2 files changed, 6 insertions(+)
diff --git a/arch/arm/mm/pageattr.c b/arch/arm/mm/pageattr.c
index cf30daf..d19b1ad 100644
--- a/arch/arm/mm/pageattr.c
+++ b/arch/arm/mm/pageattr.c
@@ -49,6 +49,9 @@ static int change_memory_common(unsigned long addr, int numpages,
WARN_ON_ONCE(1);
}
+ if (!numpages)
+ return 0;
+
if (start < MODULES_VADDR || start >= MODULES_END)
return -EINVAL;
diff --git a/arch/arm64/mm/pageattr.c b/arch/arm64/mm/pageattr.c
index 1360a02..b582fc2 100644
--- a/arch/arm64/mm/pageattr.c
+++ b/arch/arm64/mm/pageattr.c
@@ -53,6 +53,9 @@ static int change_memory_common(unsigned long addr, int numpages,
WARN_ON_ONCE(1);
}
+ if (!numpages)
+ return 0;
+
/*
* Kernel VA mappings are always live, and splitting live section
* mappings into page mappings may cause TLB conflicts. This means
--
1.9.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-01-26 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 6:33 [PATCH 0/2 v2] set_memory_xx fixes mika.penttila
2016-01-26 6:33 ` mika.penttila [this message]
2016-01-26 6:33 ` [PATCH 2/2 v2] make apply_to_page_range() more robust mika.penttila
2016-01-26 14:31 ` [PATCH 0/2 v2] set_memory_xx fixes Russell King - ARM Linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1453789989-13260-2-git-send-email-mika.penttila@nextfour.com \
--to=mika.penttila@nextfour.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox