tracehook_report_syscall_exit(9) suse man page | unix.com

Man Page: tracehook_report_syscall_exit

Operating Environment: suse

Section: 9

TRACEHOOK_REPORT_SYS(9) 					 Kernel Internals					   TRACEHOOK_REPORT_SYS(9)

NAME
tracehook_report_syscall_exit - task has just finished a system call
SYNOPSIS
void tracehook_report_syscall_exit(struct pt_regs * regs, int step);
ARGUMENTS
regs user register state of current task step nonzero if simulating single-step or block-step
DESCRIPTION
This will be called if TIF_SYSCALL_TRACE has been set, when the current task has just finished an attempted system call. Full user register state is available here. It is safe to block here, preventing signals from being processed. If step is nonzero, this report is also in lieu of the normal trap that would follow the system call instruction because user_enable_block_step or user_enable_single_step was used. In this case, TIF_SYSCALL_TRACE might not be set. Called without locks, just before checking for pending signals. Kernel Hackers Manual 2.6. July 2010 TRACEHOOK_REPORT_SYS(9)
Related Man Pages
iv_task(3) - debian
slurm_jobinfo_ctx_get(3) - debian
abrt-retrace-client(1) - centos
struct_utrace_engine_ops(9) - suse
slurm::stepctx(3pm) - debian
Similar Topics in the Unix Linux Community
How to restrict user to a specific directory in solaris 10
Is UNIX an open source OS ?
Getting command output to putty window title.
Cut command on RHEL 6.8 compatibility issues
Tar Command