Re: req to trace sys_execve systemcall regarding...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 10, 2001 at 08:21:45PM +0530, kannan ram wrote:

> (plz refer below).The messgage is displayed after that segmentation fault is
> coming.My code may be wrong.Plz clear me for which i would be thankful.Thank

your code is wrong. As a hint, look at the prototype of sys_execve :

asmlinkage int sys_execve(struct pt_regs regs)

NOT

asmlinkage int sys_execve(struct pt_regs * regs)

and think about how the system call might need to change a process's saved registers
to ensure when it returns to user space, it executes the startup code for the execve()d
image.

We get quite a few people asking about sys call overloading - my suggestion
is to check on kernelnewbies.org/patches/ for existing things that do this like
overloader or syscalltracker (note: I haven't actually looked at these sources, they may
be wrong).

regards
john

-- 
"Beware of bugs in the above code; I have only proved it correct, not tried
it."
	- Donald Knuth
-
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
IRC Channel:   irc.openprojects.net / #kernelnewbies
Web Page:      http://www.kernelnewbies.org/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux