From: Keith Owens <kaos@ocs.com.au>
To: coywolf@sosdg.org
Cc: akpm@osdl.org, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
Josh Boyer <jdub@us.ibm.com>
Subject: Re: [patch] mark text section read-only
Date: Sun, 13 Nov 2005 15:50:03 +1100 [thread overview]
Message-ID: <3066.1131857403@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 12 Nov 2005 11:34:55 CDT." <20051112163455.GA1425@everest.sosdg.org>
On Sat, 12 Nov 2005 11:34:55 -0500,
Coywolf Qi Hunt <coywolf@sosdg.org> wrote:
>+config DEBUG_ROTEXT
>+ bool "Write protect kernel text"
>+ depends on DEBUG_KERNEL
>+ help
>+ Mark the kernel text as write-protected in the pagetables,
>+ in order to catch accidental (and incorrect) writes to kernel text
>+ area. This option will increase TLB pressure thus impact performance.
>+ Note this may conflict with kprobes. If in doubt, say "N".
Also conflicts with kdb, kgdb, and any other kernel debugger that uses
software breakpoints.
next prev parent reply other threads:[~2005-11-13 4:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 10:56 [patch 01/02] Debug option to write-protect rodata: change_page_attr fixes arjan
2005-11-07 10:58 ` [patch 02/02] Debug option to write-protect rodata: the write protect logic and config option arjan
2005-11-07 14:06 ` Josh Boyer
2005-11-07 14:20 ` Arjan van de Ven
2005-11-11 9:39 ` Coywolf Qi Hunt
2005-11-11 9:47 ` Arjan van de Ven
2005-11-11 18:57 ` Coywolf Qi Hunt
2005-11-11 19:04 ` [patch] mark text section read-only Coywolf Qi Hunt
2005-11-11 19:09 ` Arjan van de Ven
2005-11-11 19:34 ` linux-os (Dick Johnson)
2005-11-12 14:01 ` Coywolf Qi Hunt
2005-11-11 21:43 ` Andi Kleen
2005-11-11 23:30 ` Nikita Danilov
2005-11-12 17:26 ` Andi Kleen
2005-11-12 14:32 ` Coywolf Qi Hunt
2005-11-12 16:34 ` Coywolf Qi Hunt
2005-11-13 4:50 ` Keith Owens [this message]
2005-11-14 13:34 ` Linh Dang
[not found] <56cTZ-2PF-5@gated-at.bofh.it>
[not found] ` <56cTZ-2PF-3@gated-at.bofh.it>
[not found] ` <56fRE-7wr-21@gated-at.bofh.it>
[not found] ` <56gaT-7Un-17@gated-at.bofh.it>
[not found] ` <57DHW-jb-21@gated-at.bofh.it>
[not found] ` <57DHW-jb-19@gated-at.bofh.it>
[not found] ` <57Mia-4BG-5@gated-at.bofh.it>
[not found] ` <57MrY-50s-39@gated-at.bofh.it>
2005-11-11 23:03 ` Bodo Eggert
2005-11-12 4:42 ` Coywolf Qi Hunt
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=3066.1131857403@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=coywolf@sosdg.org \
--cc=jdub@us.ibm.com \
--cc=linux-kernel@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