diff options
author | 2018-03-22 09:02:33 +0100 | |
---|---|---|
committer | 2018-03-26 17:42:06 +0200 | |
commit | 3903117609f40a0bc21b8c48533ac07a574c4cdc (patch) | |
tree | 2de4db493464148719b73231d6480b081de8b1ed /drivers/gpu/drm/tinydrm/core | |
parent | gpu: drm: nouveau: Use list_{next/prev}_entry instead of list_entry (diff) | |
download | wireguard-linux-3903117609f40a0bc21b8c48533ac07a574c4cdc.tar.xz wireguard-linux-3903117609f40a0bc21b8c48533ac07a574c4cdc.zip |
drm/gem: Document that handle_create must be the last step
It published the gem object to userspace, by that point other threads
can guess the id and start using it. And gem IDs are _very_ easy to
guess (it's just an idr).
Since gem objects is the only thing we allow drivers to create
themselves (all the kms/prime/syncobj stuff is handled by the core) no
other functions seem to be in need of this clarification.
Motivated by reviewing the xen-front kms driver.
Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Reviewed-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180322080233.17266-1-daniel.vetter@ffwll.ch
Diffstat (limited to 'drivers/gpu/drm/tinydrm/core')
0 files changed, 0 insertions, 0 deletions