On Monday 28 August 2006 04:20, Randy.Dunlap wrote:
> Question:
> All other syscalls (in syscalls.h) return long or unsigned long
> or ssize_t etc. I.e., none of them return int. Does this one
> return int because it's strictly an inside-the-kernel "syscall",
> not exposed to userspace?
Well, it's not really a system call in the first place, but
I could not find any other place where it would fit.
The prototype of the kernel_execve function is the one from
the man execve page, and also similar to those that were
generated by the _syscall3() macro before.
Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
