Messages in this thread | | | From | "Dinesh K Subhraveti" <> | Subject | Isn't wait4 amenable to interception? | Date | Fri, 9 Apr 1999 02:10:35 -0400 |
| |
Hello,
I am trying to intercept wait4 and having problems with it. Does wait4 differ from other system calls in any peculiar way? The new system call routine just returns original sys_wait4. After inserting the module, system works just fine. But rmmod causes a kernel oops with "Bad EIP" message and shell gets killed. After kernel oops everything seems just fine too. I'd greatly appreciate any insight on this. Am attaching the code below. Please reply to dinesh@cs.columbia.edu.
Thanks in advance, Dinesh
----------------------------------------------- #include <linux/kernel.h> #include <linux/module.h> #include <linux/resource.h> #include <sys/syscall.h>
extern void *sys_call_table[];
static int (*original_sys_wait4) (pid_t, int*, int, struct rusage*);
asmlinkage int my_wait4 (pid_t a, int *b, int c, struct rusage *d) { return original_sys_wait4 (a, b, c, d); }
int init_module() { original_sys_wait4 = sys_call_table[__NR_wait4]; sys_call_table[__NR_wait4] = my_wait4; return 0; }
void cleanup_module() { sys_call_table[__NR_wait4] = original_sys_wait4; }
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |