audit_syscall_entry(9) [suse man page]

AUDIT_SYSCALL_ENTRY(9)						 Audit Interfaces					    AUDIT_SYSCALL_ENTRY(9)

NAME

       audit_syscall_entry - fill in an audit record at syscall entry

SYNOPSIS

       void audit_syscall_entry(int arch, int major, unsigned long a1, unsigned long a2, unsigned long a3, unsigned long a4);

ARGUMENTS

       arch
	   architecture type

       major
	   major syscall type (function)

       a1
	   additional syscall register 1

       a2
	   additional syscall register 2

       a3
	   additional syscall register 3

       a4
	   additional syscall register 4

DESCRIPTION

       Fill in audit context at syscall entry. This only happens if the audit context was created when the task was created and the state or
       filters demand the audit context be built. If the state from the per-task filter or from the per-syscall filter is AUDIT_RECORD_CONTEXT,
       then the record will be written at syscall exit time (otherwise, it will only be written if another part of the kernel requests that it be
       written).

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010						    AUDIT_SYSCALL_ENTRY(9)

syscall(3UCB)                                        SunOS/BSD Compatibility Library Functions                                       syscall(3UCB)

NAME

       syscall - indirect system call

SYNOPSIS

       /usr/ucb/cc [ flag ... ] file ...
       #include <sys/syscall.h>

       int syscall(number,  arg,  ...);

DESCRIPTION

       syscall()  performs the function whose assembly language interface has the specified number, and arguments arg ....  Symbolic constants for
       functions can be found in the header <sys/syscall.h>.

RETURN VALUES

       On error syscall() returns -1 and sets the external variable errno (see intro(2)).

FILES

       <sys/syscall.h>

SEE ALSO

       intro(2), pipe(2)

NOTES

       Use of these interfaces should be restricted to only applications written on BSD platforms.  Use of these interfaces with any of the system
       libraries or in multi-thread applications is unsupported.

WARNINGS

       There is no way to use syscall() to call functions such as pipe(2) which return values that do not fit into one hardware register.

       Since  many  system  calls  are  implemented  as library wrappers around traps to the kernel, these calls may not behave as documented when
       called from syscall(), which bypasses these wrappers. For these reasons, using syscall() is not recommended.

SunOS 5.10                                                          22 Jan 1993                                                      syscall(3UCB)