[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070517220638.GA6532@localhost.localdomain>
Date: Fri, 18 May 2007 00:06:38 +0200
From: Philipp Kohlbecher <pk031698@...-greifswald.de>
To: Dave Jones <davej@...emonkey.org.uk>,
"H. Peter Anvin" <hpa@...or.com>
Cc: Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
linux-assembly@...r.kernel.org
Subject: [PATCH 2.6.21.1] i386: save registers before intra-privilege syscall
From: Philipp Kohlbecher <pk031698@...-greifswald.de>
The kernel_execve function issues a software interrupt (int 0x80) to make
a system call to sys_execve. This function expects to find the stack segment
and stack pointer of the function that issued the system call in the pt_regs
struct. The syscall entry code that sets up this struct expects the stack
segment and the stack pointer of the issuing function already on the stack.
But the Intel processor saves these registers only if a stack-switch occurs,
i.e. for inter-privilege interrupts and exceptions (cf. Intel Software
Developer’s Manual, Vol. 3A, p. 5-17,
http://www.intel.com/design/processor/manuals/253668.pdf).
For an intra-privilege interrupt like the one issued in kernel_execve, these
registers must be saved manually.
Signed-off-by: Philipp Kohlbecher <pk031698@...-greifswald.de>
---
I am a total newbie and this is my first patch, so please be merciful...
Also, please CC me, I am not on the list.
--- a/arch/i386/kernel/sys_i386.c 2007-05-13 18:40:33.000000000 +0200
+++ b/arch/i386/kernel/sys_i386.c 2007-05-13 17:23:10.000000000 +0200
@@ -258,7 +258,8 @@ int kernel_execve(const char *filename,
int kernel_execve(const char *filename, char *const argv[], char *const envp[])
{
long __res;
- asm volatile ("push %%ebx ; movl %2,%%ebx ; int $0x80 ; pop %%ebx"
+ asm volatile ("push %%ebx ; movl %2,%%ebx ; push %%ss ; push %%esp;"
+ "int $0x80 ; addl $(4*2),%%esp ; pop %%ebx"
: "=a" (__res)
: "0" (__NR_execve),"ri" (filename),"c" (argv), "d" (envp) : "memory");
return __res;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists