drm_ioctl_flags(9)
π NAME π
drm_ioctl_flags β bestie, this one checks for a core ioctl and hands back the ioctl permission flags β¨ (and yes, it's from the Kernel API Manual, we're in the kernel docs now π«Ά)
πΈ SYNOPSIS πΈ
bool drm_ioctl_flags (unsigned int nr , unsigned int *flags );
π ARGUMENTS π
nrβ the ioctl number, literally the number you're checking πflagsβ the spot where the ioctl permission flags get returned, so this is your output destination bestie π
π¦ DESCRIPTION π¦
Okay so here's the tea: this ioctl is only used by the vmwgfx driver to augment the access checks done by the DRM core β and insofar it's a pretty decent layering violation ππ. It shouldn't be used by any drivers. Like, at all. Not you, not your driver, not your friend's driver. Periodt. π
Ngl this is giving "we know this is questionable but it's here" energy. Do not copy this behavior into your own code, fr fr.
β¨ RETURN β¨
It returns True if nr corresponds to a DRM core ioctl number, and false otherwise. Slay π
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/drm_ioctl.cβ thegetuniqueandsetversionstory(9) π drm_noop(9)drm_invalid_op(9)- driver specific ioctls(9)
drm_ioctl(9)
That's the whole vibe, bestie β brought to you from ./drivers/gpu/drm, dated October 2026. Go forth and maybe don't use this in your driver, 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