syscall_exit_work(9)
π syscall_exit_work(9) β from the Kernel API Manual, bestie π
okay so picture this: you're a syscall, you've done your little tasks, and now you're this close to sliding back into user mode. but before you go β there's a tiny bit of cleanup. that's this function. she's the last vibe check before you leave the building. β¨
β¨ NAME β¨
syscall_exit_work β handle work before returning to user mode π«Ά
πΈ SYNOPSIS πΈ
void syscall_exit_work (struct pt_regs *regs , unsigned long work );
π¦ ARGUMENTS π¦
regsβ pointer to the currentpt_regs. literally the receipts of where your registers are at rn. πworkβ the current thread syscall work. this is the to-do list she's carrying out the door. π
π DESCRIPTION π
do one-time syscall specific work.
that's it. that's the whole description. she's lowkey iconic for being this short about it. one-time, syscall-specific, and then you're free. no cap. π§
π₯ SEE ALSO π₯
- kernel file
./include/linux/entry-common.hβ go read the source bestie, it's giving receipts π arch_ptrace_report_syscall_permit_entry(9)syscall_enter_from_user_mode_work(9)enter_from_user_mode_randomize_stack(9)syscall_enter_from_user_mode_randomize_stack(9)β yes she's listed twice in the original and we're keeping it that way, it's a stylistic choice, don't @ me πarch_ptrace_report_syscall_exit(9)syscall_exit_to_user_mode_work(9)syscall_exit_to_user_mode(9)
reminder bestie: this page is short on purpose. don't go inventing behaviour that isn't written here β if it's not in the description, it's not canon. π
β and that's the page! brought to you from ./include/linux, dated October 2026, and yes the footer still says syscall_exit_work(9) because we never forget where we came from. mwah πππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms