Robert Watson b783025921 When handling msgsys(2), semsys(2), and shmsys(2) multiplex system calls, ... map the 'which' argument into a suitable audit event identifier for the specific operation requested. Obtained from: TrustedBSD Project MFC after: 3 weeks Sponsored by: DARPA, AFRL		2017-03-29 23:31:35 +00:00
..
audit_arg.c	When handling msgsys(2), semsys(2), and shmsys(2) multiplex system calls,	2017-03-29 23:31:35 +00:00
audit_bsm_klib.c	When handling msgsys(2), semsys(2), and shmsys(2) multiplex system calls,	2017-03-29 23:31:35 +00:00
audit_bsm.c	Introduce an audit event identifier -> audit event name mapping	2017-03-27 10:38:53 +00:00
audit_dtrace.c	Add an experimental DTrace audit provider, which allows users of DTrace to	2017-03-29 19:58:00 +00:00
audit_ioctl.h
audit_pipe.c
audit_private.h	When handling msgsys(2), semsys(2), and shmsys(2) multiplex system calls,	2017-03-29 23:31:35 +00:00
audit_syscalls.c	Introduce an audit event identifier -> audit event name mapping	2017-03-27 10:38:53 +00:00
audit_trigger.c
audit_worker.c	Add an experimental DTrace audit provider, which allows users of DTrace to	2017-03-29 19:58:00 +00:00
audit.c	When handling msgsys(2), semsys(2), and shmsys(2) multiplex system calls,	2017-03-29 23:31:35 +00:00
audit.h	When handling msgsys(2), semsys(2), and shmsys(2) multiplex system calls,	2017-03-29 23:31:35 +00:00
bsm_domain.c
bsm_errno.c
bsm_fcntl.c
bsm_socket_type.c
bsm_token.c