Lines Matching refs:ioctl

19 submission ioctl exactly should look like. Learning these lessons is probably
56  * Have a clear way for userspace to figure out whether your new ioctl or ioctl
62    the structure. The drm core checks the passed-in size for each ioctl call
69    and reject the ioctl if that's not the case. Otherwise your nice plan for
71    an ioctl struct with random stack garbage in the yet unused parts. Which
86  * The ioctl must check for array overflows. Also it needs to check for
93  * Have simple testcases for every input validation failure case in your ioctl.
97    the ioctl already and shadow the codepath you actually want to test, hiding
105    how you handle ioctl restarting - e.g. drm has a tiny drmIoctl helper in its
106    userspace library. The i915 driver botched this with the set_tiling ioctl,
146    ioctl restartable relative timeouts tend to be too coarse and can
188    command submission ioctl. But then if objects are shareable userspace needs
199 Not every problem needs a new ioctl:
216 be stuck with a given ioctl essentially forever. You can try to deprecate