From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-fsdevel@vger.kernel.org
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [PATCHES] [drm] file descriptor fixes
Date: Mon, 12 Aug 2024 07:56:56 +0100 [thread overview]
Message-ID: <20240812065656.GI13701@ZenIV> (raw)
Resurrecting the stuff from last cycle.
Context: several places in drm have racy uses of close_fd().
Not hard to fix, thankfully.
Changed since the last posting: as requested, KFD
fix had been split in two commits - introduction of helper
(drm_gem_prime_handle_to_dmabuf()) and switching kfd_mem_export_dmabuf()
to that.
Branch in git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git #for-drm,
individual patches in followups.
Please, review; IMO that ought to go through drm and amd-gfx
trees.
Shortlog:
Al Viro (4):
new helper: drm_gem_prime_handle_to_dmabuf()
amdgpu: fix a race in kfd_mem_export_dmabuf()
amdkfd CRIU fixes
amdgpu: get rid of bogus includes of fdtable.h
Diffstat:
.../gpu/drm/amd/amdgpu/amdgpu_amdkfd_arcturus.c | 1 -
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 12 +---
drivers/gpu/drm/amd/amdgpu/amdgpu_sched.c | 1 -
drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 64 ++++++++++++-----
drivers/gpu/drm/drm_prime.c | 84 +++++++++++-----------
include/drm/drm_prime.h | 3 +
6 files changed, 95 insertions(+), 70 deletions(-)
next reply other threads:[~2024-08-12 6:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 6:56 Al Viro [this message]
2024-08-12 6:59 ` [PATCH 1/4] new helper: drm_gem_prime_handle_to_dmabuf() Al Viro
2024-08-12 6:59 ` [PATCH 2/4] amdgpu: fix a race in kfd_mem_export_dmabuf() Al Viro
2024-08-14 22:15 ` Felix Kuehling
2024-08-22 0:29 ` Al Viro
2024-08-22 18:02 ` Alex Deucher
2024-08-12 6:59 ` [PATCH 3/4] amdkfd CRIU fixes Al Viro
2024-08-12 6:59 ` [PATCH 4/4] amdgpu: get rid of bogus includes of fdtable.h Al Viro
2024-08-22 14:41 ` [PATCH 1/4] new helper: drm_gem_prime_handle_to_dmabuf() Thomas Zimmermann
2024-08-22 15:20 ` Al Viro
2024-08-23 1:57 ` Al Viro
2024-08-23 7:21 ` Thomas Zimmermann
2024-08-23 7:53 ` Al Viro
2024-09-10 16:36 ` Alex Deucher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240812065656.GI13701@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).