drm_ioctl_flags(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 🌈


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