From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Francois Dugast <francois.dugast@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Cc: intel-xe@lists.freedesktop.org, Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH 2/2] drm/xe/ufence: Warn if mmget_not_zero() fails
Date: Mon, 14 Oct 2024 12:58:29 +0200 [thread overview]
Message-ID: <f2646225-171e-4101-a0b6-73a0dfd017fd@linux.intel.com> (raw)
In-Reply-To: <Zwzj4N466Z3uZryR@fdugast-desk>
I believe this is triggerable from userspace, so this should be a
XE_IOCTL_DBG
Den 2024-10-14 kl. 11:27, skrev Francois Dugast:
> On Fri, Oct 11, 2024 at 01:57:15PM +0200, Nirmoy Das wrote:
>> This shouldn't happen but seen this while debugging ufence timeout
>> issue time to time so log it to isolate this particular case.
>>
>> Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1630
>> Cc: Matthew Brost <matthew.brost@intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>
> Reviewed-by: Francois Dugast <francois.dugast@intel.com>
>
>> ---
>> drivers/gpu/drm/xe/xe_sync.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_sync.c b/drivers/gpu/drm/xe/xe_sync.c
>> index 6a2e4dd41d56..41758f528d7c 100644
>> --- a/drivers/gpu/drm/xe/xe_sync.c
>> +++ b/drivers/gpu/drm/xe/xe_sync.c
>> @@ -83,6 +83,8 @@ static void user_fence_worker(struct work_struct *w)
>> XE_WARN_ON("Copy to user failed");
>> kthread_unuse_mm(ufence->mm);
>> mmput(ufence->mm);
>> + } else {
>> + XE_WARN_ON("mmget_not_zero() failed");
>> }
>>
>> wake_up_all(&ufence->xe->ufence_wq);
>> --
>> 2.46.0
>>
next prev parent reply other threads:[~2024-10-14 10:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 11:57 [PATCH 1/2] drm/xe/ufence: Prefetch ufence addr to catch bogus address Nirmoy Das
2024-10-11 11:57 ` [PATCH 2/2] drm/xe/ufence: Warn if mmget_not_zero() fails Nirmoy Das
2024-10-14 9:27 ` Francois Dugast
2024-10-14 10:58 ` Maarten Lankhorst [this message]
2024-10-14 11:37 ` Francois Dugast
2024-10-11 13:16 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe/ufence: Prefetch ufence addr to catch bogus address Patchwork
2024-10-11 13:17 ` ✓ CI.checkpatch: " Patchwork
2024-10-11 13:18 ` ✓ CI.KUnit: " Patchwork
2024-10-11 13:34 ` ✓ CI.Build: " Patchwork
2024-10-11 13:37 ` ✓ CI.Hooks: " Patchwork
2024-10-11 13:39 ` ✓ CI.checksparse: " Patchwork
2024-10-11 14:07 ` ✗ CI.BAT: failure " Patchwork
2024-10-11 16:01 ` ✗ CI.FULL: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-10-15 9:05 [PATCH 0/2] Improve ufence addr validation and error handling Nirmoy Das
2024-10-15 9:05 ` [PATCH 2/2] drm/xe/ufence: Warn if mmget_not_zero() fails Nirmoy Das
2024-10-15 12:48 ` Maarten Lankhorst
2024-10-15 12:59 ` 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=f2646225-171e-4101-a0b6-73a0dfd017fd@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=nirmoy.das@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.