From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Nirmoy Das <nirmoy.das@linux.intel.com>,
Nirmoy Das <nirmoy.das@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org,
Andi Shyti <andi.shyti@linux.intel.com>,
Shawn Lee <shawn.c.lee@intel.com>
Subject: Re: [PATCH] drm/i915: check before removing mm notifier
Date: Tue, 27 Feb 2024 09:04:45 +0000 [thread overview]
Message-ID: <96eec421-090a-4420-ab94-098414334e29@linux.intel.com> (raw)
In-Reply-To: <3c1a25f9-b1ee-4832-a89c-68813cc72416@linux.intel.com>
On 21/02/2024 11:52, Nirmoy Das wrote:
> Merged it to drm-intel-gt-next with s/check/Check
Shouldn't this have had:
Fixes: ed29c2691188 ("drm/i915: Fix userptr so we do not have to worry about obj->mm.lock, v7.")
Cc: <stable@vger.kernel.org> # v5.13+
?
Regards,
Tvrtko
> On 2/19/2024 1:50 PM, Nirmoy Das wrote:
>> Error in mmu_interval_notifier_insert() can leave a NULL
>> notifier.mm pointer. Catch that and return early.
>>
>> Cc: Andi Shyti <andi.shyti@linux.intel.com>
>> Cc: Shawn Lee <shawn.c.lee@intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>> drivers/gpu/drm/i915/gem/i915_gem_userptr.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
>> b/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
>> index 0e21ce9d3e5a..61abfb505766 100644
>> --- a/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
>> +++ b/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
>> @@ -349,6 +349,9 @@ i915_gem_userptr_release(struct
>> drm_i915_gem_object *obj)
>> {
>> GEM_WARN_ON(obj->userptr.page_ref);
>> + if (!obj->userptr.notifier.mm)
>> + return;
>> +
>> mmu_interval_notifier_remove(&obj->userptr.notifier);
>> obj->userptr.notifier.mm = NULL;
>> }
next prev parent reply other threads:[~2024-02-27 9:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 12:50 [PATCH] drm/i915: check before removing mm notifier Nirmoy Das
2024-02-19 16:44 ` ✓ Fi.CI.BAT: success for drm/i915: check before removing mm notifier (rev2) Patchwork
2024-02-19 20:12 ` [PATCH] drm/i915: check before removing mm notifier Rodrigo Vivi
2024-02-20 9:05 ` Nirmoy Das
2024-02-19 21:38 ` ✗ Fi.CI.IGT: failure for drm/i915: check before removing mm notifier (rev2) Patchwork
2024-02-20 13:51 ` ✓ Fi.CI.BAT: success for drm/i915: check before removing mm notifier (rev3) Patchwork
2024-02-20 15:04 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-02-21 11:52 ` [PATCH] drm/i915: check before removing mm notifier Nirmoy Das
2024-02-27 9:04 ` Tvrtko Ursulin [this message]
2024-02-27 9:26 ` Nirmoy Das
2024-02-28 13:24 ` Tvrtko Ursulin
2024-02-28 14:14 ` Nirmoy Das
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=96eec421-090a-4420-ab94-098414334e29@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@intel.com \
--cc=nirmoy.das@linux.intel.com \
--cc=shawn.c.lee@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