From: <mika.penttila@nextfour.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, rientjes@google.com, linux@arm.linux.org.uk,
"Mika Penttilä" <mika.penttila@nextfour.com>
Subject: [PATCH 3/4] arm64: let set_memory_xx(addr, 0) succeed.
Date: Sat, 23 Jan 2016 17:05:42 +0200 [thread overview]
Message-ID: <1453561543-14756-4-git-send-email-mika.penttila@nextfour.com> (raw)
In-Reply-To: <1453561543-14756-1-git-send-email-mika.penttila@nextfour.com>
From: Mika PenttilA? <mika.penttila@nextfour.com>
This makes set_memory_xx() consistent with x86.
Signed-off-by: Mika PenttilA? mika.penttila@nextfour.com
---
arch/arm64/mm/pageattr.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/mm/pageattr.c b/arch/arm64/mm/pageattr.c
index 3571c73..52220dd 100644
--- a/arch/arm64/mm/pageattr.c
+++ b/arch/arm64/mm/pageattr.c
@@ -51,6 +51,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;
--
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-23 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 15:05 [PATCH 0/4] set_memory_xx fixes mika.penttila
2016-01-23 15:05 ` [PATCH 1/4] arm: Fix wrong bounds check mika.penttila
2016-01-25 18:37 ` Laura Abbott
2016-01-23 15:05 ` [PATCH 2/4] arm: let set_memory_xx(addr, 0) succeed mika.penttila
2016-01-25 18:41 ` Laura Abbott
2016-01-23 15:05 ` mika.penttila [this message]
2016-01-25 18:44 ` [PATCH 3/4] arm64: " Laura Abbott
2016-01-26 2:34 ` David Rientjes
2016-01-23 15:05 ` [PATCH 4/4] make apply_to_page_range() more robust mika.penttila
2016-01-26 2:32 ` David Rientjes
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=1453561543-14756-4-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 \
--cc=rientjes@google.com \
/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