noinstr
https://docs.kernel.org/core-api/entry.html
syscall entry must not be instrumented because :
starts in assembly and interacts with love-level C and stack frames (registers should not get overwritten)
this function set up
lockdep
,RCU/Context tracking
and tracing for the call usingsyscall_eter_from_user_mode()
. It then invokes various entry functions like ptrace, seccomp, audit, syscall tracing, etc. (RCU is not yet setup at the beginning, hence must not be instrumented)
Do not nest syscalls. Nested systcalls will cause RCU and/or context tracking to print a warning.
Last updated