From: "Thomas Hellström (Intel)" <thomas_os@shipmail.org>
To: "Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
"David Airlie" <airlied@linux.ie>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Chia-I Wu" <olvaffe@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Emil Velikov" <emil.l.velikov@gmail.com>,
"Christian König" <christian.koenig@amd.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Dmitry Osipenko <digetx@gmail.com>,
linux-tegra@vger.kernel.org, kernel@collabora.com,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v7 2/2] drm/gem: Don't map imported GEMs
Date: Thu, 30 Jun 2022 22:15:10 +0200 [thread overview]
Message-ID: <75b677b6-c704-e270-c921-93c982020c38@shipmail.org> (raw)
In-Reply-To: <20220630200405.1883897-3-dmitry.osipenko@collabora.com>
Hi, Dmitry,
On 6/30/22 22:04, Dmitry Osipenko wrote:
> Drivers that use drm_gem_mmap() and drm_gem_mmap_obj() helpers don't
> handle imported dma-bufs properly, which results in mapping of something
> else than the imported dma-buf. On NVIDIA Tegra we get a hard lockup when
> userspace writes to the memory mapping of a dma-buf that was imported into
> Tegra's DRM GEM.
>
> Majority of DRM drivers prohibit mapping of the imported GEM objects.
> Mapping of imported GEMs require special care from userspace since it
> should sync dma-buf because mapping coherency of the exporter device may
> not match the DRM device. Let's prohibit the mapping for all DRM drivers
> for consistency.
>
> Cc: stable@vger.kernel.org
> Suggested-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
This might break drivers whose obj->funcs->mmap() callback already
handles this case, and has userspace that does the right thing.
I think the disabling must be checked on a per-driver basis to avoid
that; in particular drivers that already call dma_buf_mmap() should be
able to continue doing this.
Also the Fixes: review comment remains,
thanks,
Thomas
> ---
> drivers/gpu/drm/drm_gem.c | 4 ++++
> drivers/gpu/drm/drm_gem_shmem_helper.c | 9 ---------
> 2 files changed, 4 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c
> index 86d670c71286..fc9ec42fa0ab 100644
> --- a/drivers/gpu/drm/drm_gem.c
> +++ b/drivers/gpu/drm/drm_gem.c
> @@ -1034,6 +1034,10 @@ int drm_gem_mmap_obj(struct drm_gem_object *obj, unsigned long obj_size,
> {
> int ret;
>
> + /* Don't allow imported objects to be mapped */
> + if (obj->import_attach)
> + return -EINVAL;
> +
> /* Check for valid size. */
> if (obj_size < vma->vm_end - vma->vm_start)
> return -EINVAL;
> diff --git a/drivers/gpu/drm/drm_gem_shmem_helper.c b/drivers/gpu/drm/drm_gem_shmem_helper.c
> index 8ad0e02991ca..6190f5018986 100644
> --- a/drivers/gpu/drm/drm_gem_shmem_helper.c
> +++ b/drivers/gpu/drm/drm_gem_shmem_helper.c
> @@ -609,17 +609,8 @@ EXPORT_SYMBOL_GPL(drm_gem_shmem_vm_ops);
> */
> int drm_gem_shmem_mmap(struct drm_gem_shmem_object *shmem, struct vm_area_struct *vma)
> {
> - struct drm_gem_object *obj = &shmem->base;
> int ret;
>
> - if (obj->import_attach) {
> - /* Drop the reference drm_gem_mmap_obj() acquired.*/
> - drm_gem_object_put(obj);
> - vma->vm_private_data = NULL;
> -
> - return dma_buf_mmap(obj->dma_buf, vma, 0);
> - }
> -
> ret = drm_gem_shmem_get_pages(shmem);
> if (ret) {
> drm_gem_vm_close(vma);
next prev parent reply other threads:[~2022-06-30 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 20:04 [PATCH v7 0/2] DRM GEM fixes Dmitry Osipenko
2022-06-30 20:04 ` [PATCH v7 1/2] drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error Dmitry Osipenko
2022-08-09 16:41 ` Daniel Vetter
2022-06-30 20:04 ` [PATCH v7 2/2] drm/gem: Don't map imported GEMs Dmitry Osipenko
2022-06-30 20:15 ` Thomas Hellström (Intel) [this message]
2022-06-30 20:22 ` Dmitry Osipenko
2022-06-30 20:26 ` Thomas Hellström (Intel)
2022-07-01 8:22 ` Dmitry Osipenko
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=75b677b6-c704-e270-c921-93c982020c38@shipmail.org \
--to=thomas_os@shipmail.org \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=digetx@gmail.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=gurchetansingh@chromium.org \
--cc=kernel@collabora.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®