Return to Answer

added 19 characters in body

Source Link

edited Jan 24, 2012 at 3:12

41.7k
17
91
113

System calls are usually wrapped in the SYSCALL_DEFINEx()SYSCALL_DEFINEx() macro, which is why a simple grepgrep doesn't find them:

fs/namei.c:SYSCALL_DEFINE2(mkdir, const char __user *, pathname, int, mode)

fs/namei.c:SYSCALL_DEFINE2(mkdir, const char __user *, pathname, int, mode)

The final function name after the macro is expanded ends up being "sys_mkdir"sys_mkdir. The SYSCALL_DEFINEx()SYSCALL_DEFINEx() macro adds boilerplate things like tracing code that each syscall definition needs to have.

System calls are usually wrapped in the SYSCALL_DEFINEx() macro, which is why a simple grep doesn't find them:

fs/namei.c:SYSCALL_DEFINE2(mkdir, const char __user *, pathname, int, mode)

The final function name after the macro is expanded ends up being "sys_mkdir". The SYSCALL_DEFINEx() macro adds boilerplate like tracing code that each syscall definition needs to have.

System calls are usually wrapped in the SYSCALL_DEFINEx() macro, which is why a simple grep doesn't find them:

fs/namei.c:SYSCALL_DEFINE2(mkdir, const char __user *, pathname, int, mode)

The final function name after the macro is expanded ends up being sys_mkdir. The SYSCALL_DEFINEx() macro adds boilerplate things like tracing code that each syscall definition needs to have.

Source Link

answered Aug 20, 2010 at 6:16

stefanha

System calls are usually wrapped in the SYSCALL_DEFINEx() macro, which is why a simple grep doesn't find them:

fs/namei.c:SYSCALL_DEFINE2(mkdir, const char __user *, pathname, int, mode)

The final function name after the macro is expanded ends up being "sys_mkdir". The SYSCALL_DEFINEx() macro adds boilerplate like tracing code that each syscall definition needs to have.