From: Christoph Lameter <christoph@lameter.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, ak@suse.de
Subject: Re: [PATCH] Read only syscall tables for x86_64 and i386
Date: Tue, 28 Jun 2005 12:26:43 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0506281224030.1523@graphe.net> (raw)
In-Reply-To: <1119984975.3175.41.camel@laptopd505.fenrus.org>
On Tue, 28 Jun 2005, Arjan van de Ven wrote:
> I like it.. however I think the 32 bit compat syscall table on x86-64
> deserves the same treatment....
Ok.
---
Place x86_64 and i386 syscall table into the read only section.
Remove the syscall tables from the data section and place them into the
readonly section (like IA64). Includes the ia32 syscall table on x86_64.
Note that AFS seems to be modifying the syscall table. Is that legit?
Signed-off-by: Christoph Lameter <christoph@scalex86.org>
Index: linux-2.6.12-mm2/arch/i386/kernel/entry.S
===================================================================
--- linux-2.6.12-mm2.orig/arch/i386/kernel/entry.S 2005-06-28 18:34:11.000000000 +0000
+++ linux-2.6.12-mm2/arch/i386/kernel/entry.S 2005-06-28 19:06:42.000000000 +0000
@@ -680,6 +680,7 @@ ENTRY(spurious_interrupt_bug)
pushl $do_spurious_interrupt_bug
jmp error_code
+.section .rodata,"a"
#include "syscall_table.S"
syscall_table_size=(.-sys_call_table)
Index: linux-2.6.12-mm2/arch/i386/kernel/syscall_table.S
===================================================================
--- linux-2.6.12-mm2.orig/arch/i386/kernel/syscall_table.S 2005-06-28 18:34:11.000000000 +0000
+++ linux-2.6.12-mm2/arch/i386/kernel/syscall_table.S 2005-06-28 19:06:42.000000000 +0000
@@ -1,4 +1,3 @@
-.data
ENTRY(sys_call_table)
.long sys_restart_syscall /* 0 - old "setup()" system call, used for restarting */
.long sys_exit
Index: linux-2.6.12-mm2/arch/x86_64/kernel/syscall.c
===================================================================
--- linux-2.6.12-mm2.orig/arch/x86_64/kernel/syscall.c 2005-06-28 18:34:11.000000000 +0000
+++ linux-2.6.12-mm2/arch/x86_64/kernel/syscall.c 2005-06-28 19:06:42.000000000 +0000
@@ -19,7 +19,7 @@ typedef void (*sys_call_ptr_t)(void);
extern void sys_ni_syscall(void);
-sys_call_ptr_t sys_call_table[__NR_syscall_max+1] __cacheline_aligned = {
+const sys_call_ptr_t sys_call_table[__NR_syscall_max+1] = {
/* Smells like a like a compiler bug -- it doesn't work when the & below is removed. */
[0 ... __NR_syscall_max] = &sys_ni_syscall,
#include <asm-x86_64/unistd.h>
Index: linux-2.6.12-mm2/arch/x86_64/ia32/ia32entry.S
===================================================================
--- linux-2.6.12-mm2.orig/arch/x86_64/ia32/ia32entry.S 2005-06-28 17:46:31.000000000 +0000
+++ linux-2.6.12-mm2/arch/x86_64/ia32/ia32entry.S 2005-06-28 19:13:20.000000000 +0000
@@ -298,7 +298,7 @@ ENTRY(ia32_ptregs_common)
jmp ia32_sysret /* misbalances the return cache */
CFI_ENDPROC
- .data
+ .section .rodata,"a"
.align 8
.globl ia32_sys_call_table
ia32_sys_call_table:
next prev parent reply other threads:[~2005-06-28 19:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 18:47 Christoph Lameter
2005-06-28 18:56 ` Arjan van de Ven
2005-06-28 19:26 ` Christoph Lameter [this message]
2005-06-28 19:41 ` Christoph Hellwig
[not found] ` <87oe9q70no.fsf@jbms.ath.cx>
[not found] ` <Pine.LNX.4.62.0506281218030.1454@graphe.net>
2005-06-28 19:27 ` Jeremy Maitin-Shepard
2005-06-28 19:31 ` Christoph Lameter
2005-06-28 19:41 ` Jeremy Maitin-Shepard
2005-06-28 19:42 ` Christoph Hellwig
2005-06-28 19:52 ` Jeremy Maitin-Shepard
2005-06-28 20:11 ` Arjan van de Ven
2005-06-28 20:23 ` Jeremy Maitin-Shepard
2005-06-28 19:47 ` Arjan van de Ven
2005-06-28 20:00 ` Jeremy Maitin-Shepard
[not found] <Pine.LNX.4.62.0506281141050.959@graphe.net.suse.lists.linux.kernel>
2005-06-28 19:33 ` Andi Kleen
2005-06-28 19:41 ` Christoph Lameter
2005-06-29 0:06 ` Arnd Bergmann
2005-06-29 2:49 ` Andi Kleen
2005-07-01 20:10 ` Christoph Lameter
2005-07-01 20:28 ` Andi Kleen
2005-07-01 20:47 ` Richard B. Johnson
2005-07-01 21:13 ` Alan Cox
2005-07-01 20:34 ` Richard B. Johnson
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=Pine.LNX.4.62.0506281224030.1523@graphe.net \
--to=christoph@lameter.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--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
all inboxes | Powered by JetHome®