* [Intel-gfx] [PATCH] drm/i915: Fix a VMA UAF for multi-gt platform
@ 2023-06-05 20:10 Nirmoy Das
2023-06-05 20:27 ` Andi Shyti
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Nirmoy Das @ 2023-06-05 20:10 UTC (permalink / raw)
To: intel-gfx
Cc: Andrzej Hajda, Thomas Hellström, dri-devel, Chris Wilson,
Rodrigo Vivi, Nirmoy Das
Ensure correct handling of closed VMAs on multi-gt platforms to prevent
Use-After-Free. Currently, when GT0 goes idle, closed VMAs that are
exclusively added to GT0's closed_vma link (gt->closed_vma) and
subsequently freed by i915_vma_parked(), which assumes the entire GPU is
idle. However, on platforms with multiple GTs, such as MTL, GT1 may
remain active while GT0 is idle. This causes GT0 to mistakenly consider
the closed VMAs in its closed_vma list as unnecessary, potentially
leading to Use-After-Free issues if a job for GT1 attempts to access a
freed VMA.
Although we do take a wakeref for GT0 but it happens later, after
evaluating VMAs. To mitigate this, it is necessary to hold a GT0 wakeref
early.
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Cc: Chris Wilson <chris.p.wilson@intel.com>
Cc: Andi Shyti <andi.shyti@linux.intel.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>
Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
---
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
index 5fb459ea4294..adcf8837dfe6 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
@@ -2692,6 +2692,7 @@ static int
eb_select_engine(struct i915_execbuffer *eb)
{
struct intel_context *ce, *child;
+ struct intel_gt *gt;
unsigned int idx;
int err;
@@ -2715,10 +2716,16 @@ eb_select_engine(struct i915_execbuffer *eb)
}
}
eb->num_batches = ce->parallel.number_children + 1;
+ gt = ce->engine->gt;
for_each_child(ce, child)
intel_context_get(child);
intel_gt_pm_get(ce->engine->gt);
+ /* Keep GT0 active on MTL so that i915_vma_parked() doesn't
+ * free VMAs while execbuf ioctl is validating VMAs.
+ */
+ if (gt != to_gt(gt->i915))
+ intel_gt_pm_get(to_gt(ce->engine->gt->i915));
if (!test_bit(CONTEXT_ALLOC_BIT, &ce->flags)) {
err = intel_context_alloc_state(ce);
@@ -2757,6 +2764,9 @@ eb_select_engine(struct i915_execbuffer *eb)
return err;
err:
+ if (ce->engine->gt != to_gt(ce->engine->gt->i915))
+ intel_gt_pm_get(to_gt(ce->engine->gt->i915));
+
intel_gt_pm_put(ce->engine->gt);
for_each_child(ce, child)
intel_context_put(child);
@@ -2770,6 +2780,8 @@ eb_put_engine(struct i915_execbuffer *eb)
struct intel_context *child;
i915_vm_put(eb->context->vm);
+ if (eb->gt != to_gt(eb->gt->i915))
+ intel_gt_pm_put(to_gt(eb->gt->i915));
intel_gt_pm_put(eb->gt);
for_each_child(eb->context, child)
intel_context_put(child);
--
2.39.0
^ permalink raw reply related [flat|nested] 6+ messages in thread* Re: [Intel-gfx] [PATCH] drm/i915: Fix a VMA UAF for multi-gt platform 2023-06-05 20:10 [Intel-gfx] [PATCH] drm/i915: Fix a VMA UAF for multi-gt platform Nirmoy Das @ 2023-06-05 20:27 ` Andi Shyti 2023-06-06 9:06 ` Nirmoy Das 2023-06-06 1:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork 2023-06-06 22:58 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork 2 siblings, 1 reply; 6+ messages in thread From: Andi Shyti @ 2023-06-05 20:27 UTC (permalink / raw) To: Nirmoy Das Cc: Andrzej Hajda, Thomas Hellström, intel-gfx, dri-devel, Chris Wilson, Rodrigo Vivi Hi Nirmoy, On Mon, Jun 05, 2023 at 10:10:21PM +0200, Nirmoy Das wrote: > Ensure correct handling of closed VMAs on multi-gt platforms to prevent > Use-After-Free. Currently, when GT0 goes idle, closed VMAs that are > exclusively added to GT0's closed_vma link (gt->closed_vma) and > subsequently freed by i915_vma_parked(), which assumes the entire GPU is > idle. However, on platforms with multiple GTs, such as MTL, GT1 may > remain active while GT0 is idle. This causes GT0 to mistakenly consider > the closed VMAs in its closed_vma list as unnecessary, potentially > leading to Use-After-Free issues if a job for GT1 attempts to access a > freed VMA. > > Although we do take a wakeref for GT0 but it happens later, after > evaluating VMAs. To mitigate this, it is necessary to hold a GT0 wakeref > early. hooray! this is great, Nirmoy! I will give it a shot. > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> > Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> > Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com> > Cc: Chris Wilson <chris.p.wilson@intel.com> > Cc: Andi Shyti <andi.shyti@linux.intel.com> > Cc: Andrzej Hajda <andrzej.hajda@intel.com> > Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> > --- > drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c > index 5fb459ea4294..adcf8837dfe6 100644 > --- a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c > +++ b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c > @@ -2692,6 +2692,7 @@ static int > eb_select_engine(struct i915_execbuffer *eb) > { > struct intel_context *ce, *child; > + struct intel_gt *gt; > unsigned int idx; > int err; > > @@ -2715,10 +2716,16 @@ eb_select_engine(struct i915_execbuffer *eb) > } > } > eb->num_batches = ce->parallel.number_children + 1; > + gt = ce->engine->gt; > > for_each_child(ce, child) > intel_context_get(child); > intel_gt_pm_get(ce->engine->gt); > + /* Keep GT0 active on MTL so that i915_vma_parked() doesn't > + * free VMAs while execbuf ioctl is validating VMAs. > + */ > + if (gt != to_gt(gt->i915)) you can use gt->info.id > + intel_gt_pm_get(to_gt(ce->engine->gt->i915)); > > if (!test_bit(CONTEXT_ALLOC_BIT, &ce->flags)) { > err = intel_context_alloc_state(ce); > @@ -2757,6 +2764,9 @@ eb_select_engine(struct i915_execbuffer *eb) > return err; > > err: > + if (ce->engine->gt != to_gt(ce->engine->gt->i915)) if (gt->info.id) gt is already ce->engine->gt > + intel_gt_pm_get(to_gt(ce->engine->gt->i915)); > + > intel_gt_pm_put(ce->engine->gt); > for_each_child(ce, child) > intel_context_put(child); > @@ -2770,6 +2780,8 @@ eb_put_engine(struct i915_execbuffer *eb) > struct intel_context *child; > > i915_vm_put(eb->context->vm); > + if (eb->gt != to_gt(eb->gt->i915)) > + intel_gt_pm_put(to_gt(eb->gt->i915)); this wakeref going up and down is a bit ugly... Perhaps we can add some flag about the GT type in the info structure. MTL is a weird multi-gt platform and, indeed, you can't shut down GT0 without affecting GT1. For now it's OK, though, as to test it. Andi > intel_gt_pm_put(eb->gt); > for_each_child(eb->context, child) > intel_context_put(child); > -- > 2.39.0 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Fix a VMA UAF for multi-gt platform 2023-06-05 20:27 ` Andi Shyti @ 2023-06-06 9:06 ` Nirmoy Das 2023-06-06 20:11 ` Andi Shyti 0 siblings, 1 reply; 6+ messages in thread From: Nirmoy Das @ 2023-06-06 9:06 UTC (permalink / raw) To: Andi Shyti Cc: Thomas Hellström, intel-gfx, dri-devel, Chris Wilson, Andrzej Hajda, Rodrigo Vivi On 6/5/2023 10:27 PM, Andi Shyti wrote: > Hi Nirmoy, > > On Mon, Jun 05, 2023 at 10:10:21PM +0200, Nirmoy Das wrote: >> Ensure correct handling of closed VMAs on multi-gt platforms to prevent >> Use-After-Free. Currently, when GT0 goes idle, closed VMAs that are >> exclusively added to GT0's closed_vma link (gt->closed_vma) and >> subsequently freed by i915_vma_parked(), which assumes the entire GPU is >> idle. However, on platforms with multiple GTs, such as MTL, GT1 may >> remain active while GT0 is idle. This causes GT0 to mistakenly consider >> the closed VMAs in its closed_vma list as unnecessary, potentially >> leading to Use-After-Free issues if a job for GT1 attempts to access a >> freed VMA. >> >> Although we do take a wakeref for GT0 but it happens later, after >> evaluating VMAs. To mitigate this, it is necessary to hold a GT0 wakeref >> early. > hooray! this is great, Nirmoy! I will give it a shot. > >> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> >> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> >> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> >> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com> >> Cc: Chris Wilson <chris.p.wilson@intel.com> >> Cc: Andi Shyti <andi.shyti@linux.intel.com> >> Cc: Andrzej Hajda <andrzej.hajda@intel.com> >> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> >> --- >> drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 12 ++++++++++++ >> 1 file changed, 12 insertions(+) >> >> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c >> index 5fb459ea4294..adcf8837dfe6 100644 >> --- a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c >> +++ b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c >> @@ -2692,6 +2692,7 @@ static int >> eb_select_engine(struct i915_execbuffer *eb) >> { >> struct intel_context *ce, *child; >> + struct intel_gt *gt; >> unsigned int idx; >> int err; >> >> @@ -2715,10 +2716,16 @@ eb_select_engine(struct i915_execbuffer *eb) >> } >> } >> eb->num_batches = ce->parallel.number_children + 1; >> + gt = ce->engine->gt; >> >> for_each_child(ce, child) >> intel_context_get(child); >> intel_gt_pm_get(ce->engine->gt); >> + /* Keep GT0 active on MTL so that i915_vma_parked() doesn't >> + * free VMAs while execbuf ioctl is validating VMAs. >> + */ >> + if (gt != to_gt(gt->i915)) > you can use gt->info.id > >> + intel_gt_pm_get(to_gt(ce->engine->gt->i915)); >> >> if (!test_bit(CONTEXT_ALLOC_BIT, &ce->flags)) { >> err = intel_context_alloc_state(ce); >> @@ -2757,6 +2764,9 @@ eb_select_engine(struct i915_execbuffer *eb) >> return err; >> >> err: >> + if (ce->engine->gt != to_gt(ce->engine->gt->i915)) > if (gt->info.id) Thanks, was wondering if there is a better way to detect that. > > gt is already ce->engine->gt > >> + intel_gt_pm_get(to_gt(ce->engine->gt->i915)); >> + >> intel_gt_pm_put(ce->engine->gt); >> for_each_child(ce, child) >> intel_context_put(child); >> @@ -2770,6 +2780,8 @@ eb_put_engine(struct i915_execbuffer *eb) >> struct intel_context *child; >> >> i915_vm_put(eb->context->vm); >> + if (eb->gt != to_gt(eb->gt->i915)) >> + intel_gt_pm_put(to_gt(eb->gt->i915)); > this wakeref going up and down is a bit ugly... Perhaps we can > add some flag about the GT type in the info structure. Chris pointed out that there is a patch[1] in internal branch which fixes a regression by moving the intel_context_enter() before vma lookup. That should have same effect as this one. But for now I didn't mange to make it work on drm-tip(causing some crash) yet. [1] drm/i915/gem: Push wait-for-execbuf outside of ww_mutex > MTL is a > weird multi-gt platform and, indeed, you can't shut down GT0 > without affecting GT1. > > For now it's OK, though, as to test it. Looking forward to that. I did test it extensively and ChromeOS team as well. Regards, Nirmoy > > Andi > >> intel_gt_pm_put(eb->gt); >> for_each_child(eb->context, child) >> intel_context_put(child); >> -- >> 2.39.0 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Fix a VMA UAF for multi-gt platform 2023-06-06 9:06 ` Nirmoy Das @ 2023-06-06 20:11 ` Andi Shyti 0 siblings, 0 replies; 6+ messages in thread From: Andi Shyti @ 2023-06-06 20:11 UTC (permalink / raw) To: Nirmoy Das Cc: Andrzej Hajda, Thomas Hellström, intel-gfx, dri-devel, Chris Wilson, Rodrigo Vivi Hi Nirmoy, > > MTL is a > > weird multi-gt platform and, indeed, you can't shut down GT0 > > without affecting GT1. > > > > For now it's OK, though, as to test it. > > Looking forward to that. I did test it extensively and ChromeOS team as > well. great job, Nirmoy! I haven't been able to reproduce the issue. This is a great news! Tested-by: Andi Shyti <andi.shyti@linux.intel.com> Andi ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix a VMA UAF for multi-gt platform 2023-06-05 20:10 [Intel-gfx] [PATCH] drm/i915: Fix a VMA UAF for multi-gt platform Nirmoy Das 2023-06-05 20:27 ` Andi Shyti @ 2023-06-06 1:21 ` Patchwork 2023-06-06 22:58 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork 2 siblings, 0 replies; 6+ messages in thread From: Patchwork @ 2023-06-06 1:21 UTC (permalink / raw) To: Nirmoy Das; +Cc: intel-gfx [-- Attachment #1: Type: text/plain, Size: 5566 bytes --] == Series Details == Series: drm/i915: Fix a VMA UAF for multi-gt platform URL : https://patchwork.freedesktop.org/series/118887/ State : success == Summary == CI Bug Log - changes from CI_DRM_13233 -> Patchwork_118887v1 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/index.html Participating hosts (38 -> 37) ------------------------------ Missing (1): fi-snb-2520m Known issues ------------ Here are the changes found in Patchwork_118887v1 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@i915_pm_backlight@basic-brightness@edp-1: - bat-rplp-1: NOTRUN -> [ABORT][1] ([i915#7077]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/bat-rplp-1/igt@i915_pm_backlight@basic-brightness@edp-1.html * igt@i915_selftest@live@gt_heartbeat: - fi-kbl-soraka: [PASS][2] -> [DMESG-FAIL][3] ([i915#5334] / [i915#7872]) [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/fi-kbl-soraka/igt@i915_selftest@live@gt_heartbeat.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/fi-kbl-soraka/igt@i915_selftest@live@gt_heartbeat.html * igt@i915_selftest@live@reset: - bat-rpls-2: NOTRUN -> [ABORT][4] ([i915#4983] / [i915#7461] / [i915#7913] / [i915#8347]) [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/bat-rpls-2/igt@i915_selftest@live@reset.html * igt@i915_suspend@basic-s3-without-i915: - bat-rpls-1: NOTRUN -> [ABORT][5] ([i915#6687] / [i915#7978]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/bat-rpls-1/igt@i915_suspend@basic-s3-without-i915.html #### Possible fixes #### * igt@i915_selftest@live@migrate: - bat-dg2-11: [DMESG-WARN][6] ([i915#7699]) -> [PASS][7] [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/bat-dg2-11/igt@i915_selftest@live@migrate.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/bat-dg2-11/igt@i915_selftest@live@migrate.html * igt@i915_selftest@live@requests: - bat-rpls-2: [ABORT][8] ([i915#7913] / [i915#7982]) -> [PASS][9] [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/bat-rpls-2/igt@i915_selftest@live@requests.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/bat-rpls-2/igt@i915_selftest@live@requests.html - {bat-mtlp-8}: [DMESG-FAIL][10] ([i915#8497]) -> [PASS][11] [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/bat-mtlp-8/igt@i915_selftest@live@requests.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/bat-mtlp-8/igt@i915_selftest@live@requests.html - bat-rpls-1: [ABORT][12] ([i915#7911] / [i915#7920] / [i915#7982]) -> [PASS][13] [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/bat-rpls-1/igt@i915_selftest@live@requests.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/bat-rpls-1/igt@i915_selftest@live@requests.html #### Warnings #### * igt@kms_setmode@basic-clone-single-crtc: - bat-rplp-1: [ABORT][14] ([i915#4579] / [i915#8260]) -> [SKIP][15] ([i915#3555] / [i915#4579]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/bat-rplp-1/igt@kms_setmode@basic-clone-single-crtc.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/bat-rplp-1/igt@kms_setmode@basic-clone-single-crtc.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555 [i915#4423]: https://gitlab.freedesktop.org/drm/intel/issues/4423 [i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579 [i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983 [i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334 [i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367 [i915#6687]: https://gitlab.freedesktop.org/drm/intel/issues/6687 [i915#7077]: https://gitlab.freedesktop.org/drm/intel/issues/7077 [i915#7461]: https://gitlab.freedesktop.org/drm/intel/issues/7461 [i915#7699]: https://gitlab.freedesktop.org/drm/intel/issues/7699 [i915#7872]: https://gitlab.freedesktop.org/drm/intel/issues/7872 [i915#7911]: https://gitlab.freedesktop.org/drm/intel/issues/7911 [i915#7913]: https://gitlab.freedesktop.org/drm/intel/issues/7913 [i915#7920]: https://gitlab.freedesktop.org/drm/intel/issues/7920 [i915#7978]: https://gitlab.freedesktop.org/drm/intel/issues/7978 [i915#7982]: https://gitlab.freedesktop.org/drm/intel/issues/7982 [i915#8260]: https://gitlab.freedesktop.org/drm/intel/issues/8260 [i915#8347]: https://gitlab.freedesktop.org/drm/intel/issues/8347 [i915#8497]: https://gitlab.freedesktop.org/drm/intel/issues/8497 Build changes ------------- * Linux: CI_DRM_13233 -> Patchwork_118887v1 CI-20190529: 20190529 CI_DRM_13233: ee6c4040676a668d5d54c54ef5d957a56f23a030 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_7319: 2e1bcd49944452b5f9516eecee48e1fa3ae6a636 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_118887v1: ee6c4040676a668d5d54c54ef5d957a56f23a030 @ git://anongit.freedesktop.org/gfx-ci/linux ### Linux commits 4bd97db120a9 drm/i915: Fix a VMA UAF for multi-gt platform == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/index.html [-- Attachment #2: Type: text/html, Size: 6414 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Fix a VMA UAF for multi-gt platform 2023-06-05 20:10 [Intel-gfx] [PATCH] drm/i915: Fix a VMA UAF for multi-gt platform Nirmoy Das 2023-06-05 20:27 ` Andi Shyti 2023-06-06 1:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork @ 2023-06-06 22:58 ` Patchwork 2 siblings, 0 replies; 6+ messages in thread From: Patchwork @ 2023-06-06 22:58 UTC (permalink / raw) To: Nirmoy Das; +Cc: intel-gfx [-- Attachment #1: Type: text/plain, Size: 7390 bytes --] == Series Details == Series: drm/i915: Fix a VMA UAF for multi-gt platform URL : https://patchwork.freedesktop.org/series/118887/ State : success == Summary == CI Bug Log - changes from CI_DRM_13233_full -> Patchwork_118887v1_full ==================================================== Summary ------- **SUCCESS** No regressions found. Participating hosts (7 -> 6) ------------------------------ Missing (1): shard-dg1 Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_118887v1_full: ### IGT changes ### #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * igt@kms_cursor_legacy@cursora-vs-flipa-varying-size: - {shard-rkl}: [PASS][1] -> [INCOMPLETE][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/shard-rkl-4/igt@kms_cursor_legacy@cursora-vs-flipa-varying-size.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-rkl-7/igt@kms_cursor_legacy@cursora-vs-flipa-varying-size.html Known issues ------------ Here are the changes found in Patchwork_118887v1_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_ctx_persistence@engines-hang: - shard-snb: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#1099]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-snb7/igt@gem_ctx_persistence@engines-hang.html * igt@gem_exec_fair@basic-pace-share@rcs0: - shard-glk: [PASS][4] -> [FAIL][5] ([i915#2842]) [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/shard-glk5/igt@gem_exec_fair@basic-pace-share@rcs0.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-glk2/igt@gem_exec_fair@basic-pace-share@rcs0.html * igt@gem_exec_schedule@thriceslice: - shard-snb: NOTRUN -> [SKIP][6] ([fdo#109271]) +98 similar issues [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-snb7/igt@gem_exec_schedule@thriceslice.html * igt@kms_content_protection@atomic-dpms: - shard-snb: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#4579]) +16 similar issues [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-snb7/igt@kms_content_protection@atomic-dpms.html * igt@kms_setmode@basic@pipe-a-hdmi-a-1: - shard-snb: NOTRUN -> [FAIL][8] ([i915#5465]) +1 similar issue [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-snb1/igt@kms_setmode@basic@pipe-a-hdmi-a-1.html #### Possible fixes #### * igt@gem_ctx_exec@basic-nohangcheck: - {shard-tglu}: [FAIL][9] ([i915#6268]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/shard-tglu-5/igt@gem_ctx_exec@basic-nohangcheck.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-tglu-6/igt@gem_ctx_exec@basic-nohangcheck.html * igt@gem_exec_fair@basic-pace-solo@rcs0: - {shard-rkl}: [FAIL][11] ([i915#2842]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/shard-rkl-3/igt@gem_exec_fair@basic-pace-solo@rcs0.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-rkl-1/igt@gem_exec_fair@basic-pace-solo@rcs0.html - shard-apl: [FAIL][13] ([i915#2842]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/shard-apl4/igt@gem_exec_fair@basic-pace-solo@rcs0.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-apl1/igt@gem_exec_fair@basic-pace-solo@rcs0.html * igt@gem_mmap_gtt@fault-concurrent-x: - shard-snb: [ABORT][15] ([i915#5161]) -> [PASS][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/shard-snb4/igt@gem_mmap_gtt@fault-concurrent-x.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-snb7/igt@gem_mmap_gtt@fault-concurrent-x.html * igt@i915_pm_rpm@dpms-lpsp: - {shard-rkl}: [SKIP][17] ([i915#1397]) -> [PASS][18] +1 similar issue [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/shard-rkl-3/igt@i915_pm_rpm@dpms-lpsp.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-rkl-7/igt@i915_pm_rpm@dpms-lpsp.html * igt@i915_pm_rps@engine-order: - shard-apl: [FAIL][19] ([i915#6537]) -> [PASS][20] [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/shard-apl1/igt@i915_pm_rps@engine-order.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-apl7/igt@i915_pm_rps@engine-order.html * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size: - shard-glk: [FAIL][21] ([i915#2346]) -> [PASS][22] [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/shard-glk3/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-glk9/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html * igt@kms_cursor_legacy@single-move@pipe-b: - {shard-rkl}: [INCOMPLETE][23] ([i915#8011]) -> [PASS][24] +1 similar issue [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13233/shard-rkl-7/igt@kms_cursor_legacy@single-move@pipe-b.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/shard-rkl-4/igt@kms_cursor_legacy@single-move@pipe-b.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189 [i915#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099 [i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397 [i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346 [i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842 [i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955 [i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579 [i915#5161]: https://gitlab.freedesktop.org/drm/intel/issues/5161 [i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176 [i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235 [i915#5465]: https://gitlab.freedesktop.org/drm/intel/issues/5465 [i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268 [i915#6537]: https://gitlab.freedesktop.org/drm/intel/issues/6537 [i915#7742]: https://gitlab.freedesktop.org/drm/intel/issues/7742 [i915#8011]: https://gitlab.freedesktop.org/drm/intel/issues/8011 [i915#8292]: https://gitlab.freedesktop.org/drm/intel/issues/8292 Build changes ------------- * Linux: CI_DRM_13233 -> Patchwork_118887v1 CI-20190529: 20190529 CI_DRM_13233: ee6c4040676a668d5d54c54ef5d957a56f23a030 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_7319: 2e1bcd49944452b5f9516eecee48e1fa3ae6a636 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_118887v1: ee6c4040676a668d5d54c54ef5d957a56f23a030 @ git://anongit.freedesktop.org/gfx-ci/linux piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v1/index.html [-- Attachment #2: Type: text/html, Size: 8193 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-06-06 22:58 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2023-06-05 20:10 [Intel-gfx] [PATCH] drm/i915: Fix a VMA UAF for multi-gt platform Nirmoy Das 2023-06-05 20:27 ` Andi Shyti 2023-06-06 9:06 ` Nirmoy Das 2023-06-06 20:11 ` Andi Shyti 2023-06-06 1:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork 2023-06-06 22:58 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox