suse man page for tracehook_report_syscall_exit

Query: tracehook_report_syscall_exit

OS: suse

Section: 9

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

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
task_current_syscall(9) - suse
schedule_hrtimeout_range(9) - centos
swapcontext(2) - centos
kgdb_arch_handle_exception(9) - suse
reset(3) - php
Similar Topics in the Unix Linux Community
Getting command output to putty window title.
Update kernel Linux without reboot?!
Docker learning Phase-I
The Future of the PM (Private Message) System at UNIX.com
Shopt -s histappend