From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Brost" <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checkpatch: success for drm/xe: Fix ref counting leak on page fault
Date: Fri, 01 Mar 2024 04:48:16 -0000 [thread overview]
Message-ID: <170926849692.434929.11923155073729789208@8e613ede5ea5> (raw)
In-Reply-To: <20240301041036.238471-1-matthew.brost@intel.com>
== Series Details ==
Series: drm/xe: Fix ref counting leak on page fault
URL : https://patchwork.freedesktop.org/series/130590/
State : success
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
4dc7d0cc630cdd9ac56065b1a22afc329345a519
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 2d4c32ae147a95957df92600380db96ed8cc6e5b
Author: Matthew Brost <matthew.brost@intel.com>
Date: Thu Feb 29 20:10:36 2024 -0800
drm/xe: Fix ref counting leak on page fault
If a page fault occurs on VM not in fault a ref can be leaked. Fix this.
Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
+ /mt/dim checkpatch 59dffb55de2d697868cc26b9f61d7326a8f11917 drm-intel
2d4c32ae147a drm/xe: Fix ref counting leak on page fault
next prev parent reply other threads:[~2024-03-01 4:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 4:10 [PATCH] drm/xe: Fix ref counting leak on page fault Matthew Brost
2024-03-01 4:48 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-01 4:48 ` Patchwork [this message]
2024-03-01 4:49 ` ✓ CI.KUnit: " Patchwork
2024-03-01 4:59 ` ✓ CI.Build: " Patchwork
2024-03-01 5:00 ` ✓ CI.Hooks: " Patchwork
2024-03-01 5:01 ` ✓ CI.checksparse: " Patchwork
2024-03-01 5:22 ` ✓ CI.BAT: " Patchwork
2024-03-01 8:07 ` [PATCH] " Mika Kuoppala
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=170926849692.434929.11923155073729789208@8e613ede5ea5 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
/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