cap_task_setioprio(9)

📦 version 7.3.1, in nixpkgs unstable

💖 cap_task_setioprio(9) — a Kernel API Manual moment 💖

okay so bestie, we're in the Kernel API Manual section 9 today, and this page is called cap_task_setioprio. it's short, it's sweet, it's literally the vibe check for I/O priority changes 🎀

✨ NAME ✨

cap_task_setioprio — determine if I/O priority change is permitted 💅

🦋 SYNOPSIS 🦋

int cap_task_setioprio (struct task_struct *p , int ioprio );

like yes, that's the whole signature. she's compact. she's iconic. no cap. 👑

🌸 ARGUMENTS 🌸

  • p — the task to affect 💖 this is the little guy you're asking about.
  • ioprio — the I/O priority to set ⭐ this is the value you're trying to give them.

💜 DESCRIPTION 💜

so basically? this function determines if the requested I/O priority change is permitted for the specified task. that's the whole plot 🫶 you hand her a task and an I/O priority, and she checks whether that change is allowed. main character energy of a permission check, honestly.

🌈 RETURN 🌈

  • 0 if permission is granted ✨ slay, go ahead
  • -ve if denied 😭 not today, bestie — note it's -ve, i.e. a negative value, not some cute little error code you get to interpret however you want.

👑 SEE ALSO 👑

the whole friend group 💅 — plus, heads up, the kernel file she lives in is ./security/commoncap.c:

fr fr, that's the entire page — no hidden options, no env vars, no exit statuses lurking in the shadows. just vibes and a permission check 🧚

and that's a wrap, bestie 🎀 this little number comes to you from ./security, dated October 2026, and yes the title, manual name and that footer all say cap_task_setioprio(9) because she's consistent like that 💅💖 see you in the next man page 🦋

📦 where this page comes from