From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
Rob Clark <robdclark@chromium.org>,
linux-kernel@vger.kernel.org (open list),
Marijn Suijten <marijn.suijten@somainline.org>,
Sean Paul <sean@poorly.run>
Subject: [PATCH 0/2] drm/msm: Fix a couple submit leaks
Date: Wed, 14 May 2025 09:33:31 -0700 [thread overview]
Message-ID: <20250514163334.23544-1-robdclark@gmail.com> (raw)
From: Rob Clark <robdclark@chromium.org>
A couple things I found in the process of debugging VM_BIND, with all
the kernel debug knobs turned on.
Rob Clark (2):
drm/msm: Fix a fence leak in submit error path
drm/msm: Fix another leak in the submit error path
drivers/gpu/drm/msm/msm_gem_submit.c | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
--
2.49.0
next reply other threads:[~2025-05-14 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 16:33 Rob Clark [this message]
2025-05-14 16:33 ` [PATCH 1/2] drm/msm: Fix a fence leak in submit error path Rob Clark
2025-05-14 16:33 ` [PATCH 2/2] drm/msm: Fix another leak in the " Rob Clark
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=20250514163334.23544-1-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robdclark@chromium.org \
--cc=sean@poorly.run \
/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