[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221030154412.8320-1-dmitry.osipenko@collabora.com>
Date: Sun, 30 Oct 2022 18:44:10 +0300
From: Dmitry Osipenko <dmitry.osipenko@...labora.com>
To: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Sumit Semwal <sumit.semwal@...aro.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
Christian König <christian.koenig@....com>,
David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>, noralf@...nnes.org,
Dan Carpenter <dan.carpenter@...cle.com>
Cc: dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/2] Fixes for dma-buf locking issues found by Smatch
Hello,
Here are the two patches fixing minor problems introduced by my
"dma-buf locking convention" series. Thanks to Dan Carpenter who
checked linux-next with Smatch and reported the found issues.
Changelog:
v2: - Added ack from Christian König to the dma-buf patch and improved
the dma-buf/attachment pointer check.
- Dropped v1 patch that added GEM NULL-checking to
drm_gem_vunmap_unlocked() and replaced it with the NULL-checking
in drm_client_buffer_delete(), like was suggested by Christian König.
Dmitry Osipenko (2):
dma-buf: Make locking consistent in dma_buf_detach()
drm/client: Prevent NULL dereference in drm_client_buffer_delete()
drivers/dma-buf/dma-buf.c | 4 ++--
drivers/gpu/drm/drm_client.c | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
--
2.37.3
Powered by blists - more mailing lists