From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <srostedt@redhat.com>
Subject: [PATCH 5/5] ftrace, x86: do not depend on system state for kernel text info
Date: Fri, 20 Feb 2009 11:38:51 -0500 [thread overview]
Message-ID: <20090220164046.528070886@goodmis.org> (raw)
In-Reply-To: 20090220163846.709775139@goodmis.org
[-- Attachment #1: 0005-ftrace-x86-do-not-depend-on-system-state-for-kerne.patch --]
[-- Type: text/plain, Size: 3481 bytes --]
From: Steven Rostedt <srostedt@redhat.com>
Andrew Morton pointed out that using SYSTEM_STATE is a bad idea
since there is no guarantee to what its state will actually be.
Instead, I moved the check into the set_kernel_text_* functions
themselves, and use a local variable to determine when it is
OK to change the kernel text RW permissions.
Reported-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Steven Rostedt <srostedt@redhat.com>
---
arch/x86/kernel/ftrace.c | 8 --------
arch/x86/mm/init_32.c | 10 ++++++++++
arch/x86/mm/init_64.c | 10 ++++++++++
3 files changed, 20 insertions(+), 8 deletions(-)
diff --git a/arch/x86/kernel/ftrace.c b/arch/x86/kernel/ftrace.c
index c9ba2f9..025d783 100644
--- a/arch/x86/kernel/ftrace.c
+++ b/arch/x86/kernel/ftrace.c
@@ -28,20 +28,12 @@
int ftrace_arch_modify_prepare(void)
{
- /* at boot up, we are still writable */
- if (system_state != SYSTEM_RUNNING)
- return 0;
-
set_kernel_text_rw();
return 0;
}
int ftrace_arch_modify_post_process(void)
{
- /* at boot up, we are still writable */
- if (system_state != SYSTEM_RUNNING)
- return 0;
-
set_kernel_text_ro();
return 0;
}
diff --git a/arch/x86/mm/init_32.c b/arch/x86/mm/init_32.c
index bcd7f00..9ca4c57 100644
--- a/arch/x86/mm/init_32.c
+++ b/arch/x86/mm/init_32.c
@@ -1155,12 +1155,17 @@ static noinline int do_test_wp_bit(void)
const int rodata_test_data = 0xC3;
EXPORT_SYMBOL_GPL(rodata_test_data);
+static int kernel_set_to_readonly;
+
/* used by ftrace */
void set_kernel_text_rw(void)
{
unsigned long start = PFN_ALIGN(_text);
unsigned long size = PFN_ALIGN(_etext) - start;
+ if (!kernel_set_to_readonly)
+ return;
+
printk(KERN_INFO "Set kernel text: %lx - %lx for read write\n",
start, start+size);
@@ -1173,6 +1178,9 @@ void set_kernel_text_ro(void)
unsigned long start = PFN_ALIGN(_text);
unsigned long size = PFN_ALIGN(_etext) - start;
+ if (!kernel_set_to_readonly)
+ return;
+
printk(KERN_INFO "Set kernel text: %lx - %lx for read only\n",
start, start+size);
@@ -1188,6 +1196,8 @@ void mark_rodata_ro(void)
printk(KERN_INFO "Write protecting the kernel text: %luk\n",
size >> 10);
+ kernel_set_to_readonly = 1;
+
#ifdef CONFIG_CPA_DEBUG
printk(KERN_INFO "Testing CPA: Reverting %lx-%lx\n",
start, start+size);
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index 8c1b5ee..c204433 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -986,12 +986,17 @@ void free_initmem(void)
const int rodata_test_data = 0xC3;
EXPORT_SYMBOL_GPL(rodata_test_data);
+static int kernel_set_to_readonly;
+
/* used by ftrace */
void set_kernel_text_rw(void)
{
unsigned long start = PFN_ALIGN(_stext);
unsigned long end = PFN_ALIGN(__start_rodata);
+ if (!kernel_set_to_readonly)
+ return;
+
printk(KERN_INFO "Set kernel text: %lx - %lx for read write\n",
start, end);
@@ -1004,6 +1009,9 @@ void set_kernel_text_ro(void)
unsigned long start = PFN_ALIGN(_stext);
unsigned long end = PFN_ALIGN(__start_rodata);
+ if (!kernel_set_to_readonly)
+ return;
+
printk(KERN_INFO "Set kernel text: %lx - %lx for read only\n",
start, end);
@@ -1020,6 +1028,8 @@ void mark_rodata_ro(void)
(end - start) >> 10);
set_memory_ro(start, (end - start) >> PAGE_SHIFT);
+ kernel_set_to_readonly = 1;
+
/*
* The rodata section (but not the kernel text!) should also be
* not-executable.
--
1.5.6.5
--
next prev parent reply other threads:[~2009-02-20 16:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 16:38 [git pull] updates for tip Steven Rostedt
2009-02-20 16:38 ` [PATCH 1/5] ftrace: allow archs to preform pre and post process for code modification Steven Rostedt
2009-02-20 17:25 ` Ingo Molnar
2009-02-20 17:32 ` Steven Rostedt
2009-02-20 16:38 ` [PATCH 2/5] ftrace, x86: make kernel text writable only for conversions Steven Rostedt
2009-02-20 17:30 ` Ingo Molnar
2009-02-20 17:52 ` Steven Rostedt
2009-02-20 17:55 ` Ingo Molnar
2009-02-20 18:00 ` Steven Rostedt
2009-02-20 16:38 ` [PATCH 3/5] ftrace: immediately stop code modification if failure is detected Steven Rostedt
2009-02-20 16:38 ` [PATCH 4/5] ftrace: break out modify loop immediately on detection of error Steven Rostedt
2009-02-20 17:33 ` Ingo Molnar
2009-02-20 17:54 ` Steven Rostedt
2009-02-20 16:38 ` Steven Rostedt [this message]
2009-02-20 17:34 ` [PATCH 5/5] ftrace, x86: do not depend on system state for kernel text info Ingo Molnar
2009-02-20 17:54 ` Steven Rostedt
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=20090220164046.528070886@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
/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).