From: Sven Schnelle <svens@stackframe.org>
To: deller@gmx.de
Cc: linux-parisc@vger.kernel.org, Sven Schnelle <svens@stackframe.org>
Subject: [PATCH v3 2/6] parisc: add spinlock to patch function
Date: Wed, 5 Jun 2019 22:32:18 +0200 [thread overview]
Message-ID: <20190605203222.6194-3-svens@stackframe.org> (raw)
In-Reply-To: <20190605203222.6194-1-svens@stackframe.org>
If multiple CPUs are patching code we need the spinlock
to protect against parallel fixmap maps/unmap calls.
Signed-off-by: Sven Schnelle <svens@stackframe.org>
---
arch/parisc/kernel/patch.c | 25 +++++++++++++++++++------
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git a/arch/parisc/kernel/patch.c b/arch/parisc/kernel/patch.c
index 70e9997a3f80..80a0ab372802 100644
--- a/arch/parisc/kernel/patch.c
+++ b/arch/parisc/kernel/patch.c
@@ -23,7 +23,9 @@ struct patch {
static DEFINE_RAW_SPINLOCK(patch_lock);
-static void __kprobes *patch_map(void *addr, int fixmap, int *need_unmap)
+static void __kprobes *patch_map(void *addr, int fixmap, unsigned long *flags,
+ int *need_unmap)
+{
unsigned long uintaddr = (uintptr_t) addr;
bool module = !core_kernel_text(uintaddr);
struct page *page;
@@ -38,19 +40,29 @@ static void __kprobes *patch_map(void *addr, int fixmap, int *need_unmap)
*need_unmap = 1;
set_fixmap(fixmap, page_to_phys(page));
+ if (flags)
+ raw_spin_lock_irqsave(&patch_lock, *flags);
+ else
+ __acquire(&patch_lock);
return (void *) (__fix_to_virt(fixmap) + (uintaddr & ~PAGE_MASK));
}
-static void __kprobes patch_unmap(int fixmap)
+static void __kprobes patch_unmap(int fixmap, unsigned long *flags)
{
clear_fixmap(fixmap);
+
+ if (flags)
+ raw_spin_unlock_irqrestore(&patch_lock, *flags);
+ else
+ __release(&patch_lock);
}
void __kprobes __patch_text_multiple(void *addr, u32 *insn, unsigned int len)
{
unsigned long start = (unsigned long)addr;
unsigned long end = (unsigned long)addr + len;
+ unsigned long flags;
u32 *p, *fixmap;
int mapped;
@@ -58,7 +70,7 @@ void __kprobes __patch_text_multiple(void *addr, u32 *insn, unsigned int len)
flush_kernel_vmap_range(addr, len);
flush_icache_range(start, end);
- p = fixmap = patch_map(addr, FIX_TEXT_POKE0, &mapped);
+ p = fixmap = patch_map(addr, FIX_TEXT_POKE0, &flags, &mapped);
while (len >= 4) {
*p++ = *insn++;
@@ -72,14 +84,15 @@ void __kprobes __patch_text_multiple(void *addr, u32 *insn, unsigned int len)
flush_kernel_vmap_range((void *)fixmap,
(p-fixmap) * sizeof(*p));
if (mapped)
- patch_unmap(FIX_TEXT_POKE0);
- p = fixmap = patch_map(addr, FIX_TEXT_POKE0, &mapped);
+ patch_unmap(FIX_TEXT_POKE0, &flags);
+ p = fixmap = patch_map(addr, FIX_TEXT_POKE0, &flags,
+ &mapped);
}
}
flush_kernel_vmap_range((void *)fixmap, (p-fixmap) * sizeof(*p));
if (mapped)
- patch_unmap(FIX_TEXT_POKE0);
+ patch_unmap(FIX_TEXT_POKE0, &flags);
flush_icache_range(start, end);
}
--
2.20.1
next prev parent reply other threads:[~2019-06-05 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 20:32 [PATCH v3 0/6] Dynamic FTRACE for PA-RISC Sven Schnelle
2019-06-05 20:32 ` [PATCH v3 1/6] parisc: add support for patching multiple words Sven Schnelle
2019-06-05 20:32 ` Sven Schnelle [this message]
2019-06-05 20:32 ` [PATCH v3 3/6] parisc: add WARN_ON() to clear_fixmap Sven Schnelle
2019-06-05 20:32 ` [PATCH v3 4/6] parisc: use pr_debug() in kernel/module.c Sven Schnelle
2019-06-05 20:32 ` [PATCH v3 5/6] compiler.h: add CC_USING_PATCHABLE_FUNCTION_ENTRY Sven Schnelle
2019-06-05 20:32 ` [PATCH v3 6/6] parisc: add dynamic ftrace Sven Schnelle
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=20190605203222.6194-3-svens@stackframe.org \
--to=svens@stackframe.org \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).