[PATCHv4 7/7] man2: Add uretprobe syscall page
From: Jiri Olsa <jolsa@kernel.org>
Date: 2024-05-02 12:24:46
Also in:
bpf, linux-man, linux-trace-kernel, lkml
Subsystem:
the rest · Maintainer:
Linus Torvalds
Adding man page for new uretprobe syscall. Signed-off-by: Jiri Olsa <jolsa@kernel.org> --- man2/uretprobe.2 | 45 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 man2/uretprobe.2
diff --git a/man2/uretprobe.2 b/man2/uretprobe.2
new file mode 100644
index 000000000000..08fe6a670430
--- /dev/null
+++ b/man2/uretprobe.2@@ -0,0 +1,45 @@ +.\" Copyright (C) 2024, Jiri Olsa <jolsa@kernel.org> +.\" +.\" SPDX-License-Identifier: Linux-man-pages-copyleft +.\" +.TH uretprobe 2 (date) "Linux man-pages (unreleased)" +.SH NAME +uretprobe \- execute pending return uprobes +.SH SYNOPSIS +.nf +.B int uretprobe(void) +.fi +.SH DESCRIPTION +Kernel is using +.BR uretprobe() +syscall to trigger uprobe return probe consumers instead of using +standard breakpoint instruction. + +The uretprobe syscall is not supposed to be called directly by user, it's allowed +to be invoked only through user space trampoline provided by kernel. +When called from outside of this trampoline, the calling process will receive +.BR SIGILL . + +.SH RETURN VALUE +.BR uretprobe() +return value is specific for given architecture. + +.SH VERSIONS +This syscall is not specified in POSIX, +and details of its behavior vary across systems. +.SH STANDARDS +None. +.SH NOTES +.BR uretprobe() +syscall is initially introduced on x86-64 architecture, because doing syscall +is faster than doing breakpoint trap on it. It might be extended to other +architectures. + +.BR uretprobe() +syscall exists only to allow the invocation of return uprobe consumers. +It should +.B never +be called directly. +Details of the arguments (if any) passed to +.BR uretprobe () +and the return value are specific for given architecture.
--
2.44.0