You'll need the Linux kernel sources in order to see the actual source of the system calls. Manual pages, if installed on your local system, only contain the documentation of the calls and not their source itself.
Unfortunately for you, system calls aren't stored in just one particular location in the whole kernel tree. This is because various system calls can refer to different parts of the system (process management, filesystem management, etc.) and therefore it would be infeasible to store them apart from the part of the tree related to that particular part of the system.
The best thing you can do is look for the SYSCALL_DEFINE[0-6]
macro. It is used (obviously) to define the given block of code as a system call. For example, fs/ioctl.c
has the following code :
SYSCALL_DEFINE3(ioctl, unsigned int, fd, unsigned int, cmd, unsigned long, arg)
{
/* do freaky ioctl stuff */
}
Such a definition means that the ioctl
syscall is declared and takes three arguments. The number next to the SYSCALL_DEFINE
means the number of arguments. For example, in the case of getpid(void)
, declared in kernel/timer.c
, we have the following code :
SYSCALL_DEFINE0(getpid)
{
return task_tgid_vnr(current);
}
Hope that clears things up a little.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…