socketcall - socket system calls
Contents
Description
socketcall() is a common kernel entry point for the socket system calls. call determines which socket
function to invoke. args points to a block containing the actual arguments, which are passed through to
the appropriate call.
User programs should call the appropriate functions by their usual names. Only standard library
implementors and kernel hackers need to know about socketcall().
call Man page
SYS_SOCKETsocket(2)
SYS_BINDbind(2)
SYS_CONNECTconnect(2)
SYS_LISTENlisten(2)
SYS_ACCEPTaccept(2)
SYS_GETSOCKNAMEgetsockname(2)
SYS_GETPEERNAMEgetpeername(2)
SYS_SOCKETPAIRsocketpair(2)
SYS_SENDsend(2)
SYS_RECVrecv(2)
SYS_SENDTOsendto(2)
SYS_RECVFROMrecvfrom(2)
SYS_SHUTDOWNshutdown(2)
SYS_SETSOCKOPTsetsockopt(2)
SYS_GETSOCKOPTgetsockopt(2)
SYS_SENDMSGsendmsg(2)
SYS_RECVMSGrecvmsg(2)
SYS_ACCEPT4accept4(2)
SYS_RECVMMSGrecvmmsg(2)
SYS_SENDMMSGsendmmsg(2)
Library
Standard C library (libc, -lc)
Name
socketcall - socket system calls
See Also
accept(2), bind(2), connect(2), getpeername(2), getsockname(2), getsockopt(2), listen(2), recv(2),
recvfrom(2), recvmsg(2), send(2), sendmsg(2), sendto(2), setsockopt(2), shutdown(2), socket(2),
socketpair(2)
Linux man-pages 6.9.1 2024-05-02 socketcall(2)
Standards
Linux.
On x86-32, socketcall() was historically the only entry point for the sockets API. However, starting in
Linux 4.3, direct system calls are provided on x86-32 for the sockets API. This facilitates the creation
of seccomp(2) filters that filter sockets system calls (for new user-space binaries that are compiled to
use the new entry points) and also provides a (very) small performance improvement.
Synopsis
#include<linux/net.h> /* Definition of SYS_* constants */
#include<sys/syscall.h> /* Definition of SYS_socketcall */
#include<unistd.h>intsyscall(SYS_socketcall,intcall,unsignedlong*args);Note: glibc provides no wrapper for socketcall(), necessitating the use of syscall(2).
Versions
On some architectures—for example, x86-64 and ARM—there is no socketcall() system call; instead
socket(2), accept(2), bind(2), and so on really are implemented as separate system calls.
