From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<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: Mon, 19 Feb 2024 15:12:17 -0500 [thread overview]
Message-ID: <ZdO2IYev7Amcbtt1@intel.com> (raw)
In-Reply-To: <20240219125047.28906-1-nirmoy.das@intel.com>
On Mon, Feb 19, 2024 at 01:50:47PM +0100, 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;
> +
hmmm... right, it looks that we need this protection. But...
I mean, feel free to use
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
for this patch,
but I believe that if this mmu insert failed we might have other
deeper problems like when checking i915_gem_object_is_userptr() ?
No?!
> mmu_interval_notifier_remove(&obj->userptr.notifier);
> obj->userptr.notifier.mm = NULL;
> }
> --
> 2.42.0
>
next prev parent reply other threads:[~2024-02-19 20:12 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 ` Rodrigo Vivi [this message]
2024-02-20 9:05 ` [PATCH] drm/i915: check before removing mm notifier 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
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=ZdO2IYev7Amcbtt1@intel.com \
--to=rodrigo.vivi@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.