proc_uint_conv(9)

📦 version 7.3.1, in nixpkgs unstable

💻 proc_uint_conv 💅

okay bestie, welcome to the proc_uint_conv(9) page from the Kernel API Manual ✨ this one is literally all about changing a user pointer or a kernel pointer depending on which way the data is flowing 🦋

🌸 SYNOPSIS 🌸

int proc_uint_conv (ulong *u_ptr , uint *k_ptr , int dir , const struct
ctl_table *tbl , bool k_ptr_range_check , int (*user_to_kern)(const
ulong *u_ptr, uint *k_ptr) , int (*kern_to_user)(ulong *u_ptr, const
uint *k_ptr) );

like, that's the whole signature bestie — don't let the line wrapping scare you 🫶

🎀 ARGUMENTS 🎀

  • u_ptr — pointer to the user variable 💖
  • k_ptr — pointer to the kernel variable 🧚
  • dir — TRUE if this is a write to the sysctl file 👑
  • tbl — the sysctl table 📋
  • k_ptr_range_check — check the range for k_ptr when this is TRUE 🔥
  • user_to_kern — callback used to assign the value from the user var to the kernel var 🦋
  • kern_to_user — callback used to assign the value from the kernel var to the user var 🌈

✨ DESCRIPTION ✨

so here's the vibe check: when the direction is kernel to user, then u_ptr is the one getting modified 💅 and when the direction is user to kernel, then k_ptr is the one getting modified 😭 that's it, that's the whole plot 🍓

⭐ RETURN ⭐

0 on success 🎉 (slay)

🦋 SEE ALSO 🦋

ngl bestie, that's a whole friend group of functions right there — go read them too, iykyk 💜

and that's a wrap, angel 💖 this page is from ./kernel, dated October 2026, and it's literally the proc_uint_conv(9) page — periodt ✨💅🎀

📦 where this page comes from