user_disable_single_step(9)

💅 user_disable_single_step(9) 💅

okay so this is a page from the Kernel API Manual, section 9, and it's about turning off single-step mode for a user-mode task. it's short, it's sweet, it's lowkey iconic. let's get into it 🫶

---

✨ NAME ✨

user_disable_single_step — cancel user-mode single-step, bestie. that's the whole vibe check.

---

🌸 SYNOPSIS 🌸

void user_disable_single_step (struct task_struct *task );

literally just one function, one argument, returns nothing (void). clean. minimal. ate. 💅

---

🎀 ARGUMENTS 🎀

• task — either current or a task stopped in TASK_TRACED. no in-between, no "hmm what about…", those are the two moods. 🦋

---

💖 DESCRIPTION 💖

okay so what this does: it clears task of the effects of user_enable_single_step and user_enable_block_step. like, undoes the whole single-steppy situation. bye 👋

and here's the part that's genuinely so chill of it — this can be called whether or not either of those was ever called on task. never enabled it? still fine. and it works even if arch_has_single_step returned zero. no cap. it just does the thing and doesn't make a whole drama about preconditions. 🌈

ngl it's giving "idempotent queen" energy and we respect it.

---

⭐ SEE ALSO ⭐

so you wanna go down the ptrace rabbit hole? valid. here's the whole friend group, no gatekeeping 💜

• Kernel file ./include/linux/ptrace.h
• ptrace_may_access(9)
• ptrace_parent(9)
• ptrace_event_enabled(9)
• ptrace_event(9)
• ptrace_event_pid(9)
• ptrace_init_task(9)
• ptrace_release_task(9)
• arch_has_single_step(9)
• user_enable_single_step(9)
• arch_has_block_step(9)
• user_enable_block_step(9)
• arch_ptrace_stop_needed(9)
• arch_ptrace_stop(9)
• ptrace_report_syscall_permit_entry(9)
• ptrace_report_syscall_exit(9)

---

mwah 💋 this page lives in ./include/linux, dated October 2026, and it's fr fr the user_disable_single_step(9) moment. go forth and un-step. 🧚✨