* [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free
@ 2019-08-12 15:42 Chris Wilson
2019-08-12 16:13 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
` (5 more replies)
0 siblings, 6 replies; 9+ messages in thread
From: Chris Wilson @ 2019-08-12 15:42 UTC (permalink / raw)
To: dri-devel
Cc: intel-gfx, Chris Wilson, Sumit Semwal, Sean Paul, Gustavo Padovan,
Christian König, stable
During release of the syncpt, we remove it from the list of syncpt and
the tree, but only if it is not already been removed. However, during
signaling, we first remove the syncpt from the list. So, if we
concurrently free and signal the syncpt, the free may decide that it is
not part of the tree and immediately free itself -- meanwhile the
signaler goes onto to use the now freed datastructure.
In particular, we get struct by commit 0e2f733addbf ("dma-buf: make
dma_fence structure a bit smaller v2") as the cb_list is immediately
clobbered by the kfree_rcu.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111381
Fixes: d3862e44daa7 ("dma-buf/sw-sync: Fix locking around sync_timeline lists")
References: 0e2f733addbf ("dma-buf: make dma_fence structure a bit smaller v2")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Sumit Semwal <sumit.semwal@linaro.org>
Cc: Sean Paul <seanpaul@chromium.org>
Cc: Gustavo Padovan <gustavo@padovan.org>
Cc: Christian König <christian.koenig@amd.com>
Cc: <stable@vger.kernel.org> # v4.14+
---
drivers/dma-buf/sw_sync.c | 13 +++++--------
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/dma-buf/sw_sync.c b/drivers/dma-buf/sw_sync.c
index 051f6c2873c7..27b1d549ed38 100644
--- a/drivers/dma-buf/sw_sync.c
+++ b/drivers/dma-buf/sw_sync.c
@@ -132,17 +132,14 @@ static void timeline_fence_release(struct dma_fence *fence)
{
struct sync_pt *pt = dma_fence_to_sync_pt(fence);
struct sync_timeline *parent = dma_fence_parent(fence);
+ unsigned long flags;
+ spin_lock_irqsave(fence->lock, flags);
if (!list_empty(&pt->link)) {
- unsigned long flags;
-
- spin_lock_irqsave(fence->lock, flags);
- if (!list_empty(&pt->link)) {
- list_del(&pt->link);
- rb_erase(&pt->node, &parent->pt_tree);
- }
- spin_unlock_irqrestore(fence->lock, flags);
+ list_del(&pt->link);
+ rb_erase(&pt->node, &parent->pt_tree);
}
+ spin_unlock_irqrestore(fence->lock, flags);
sync_timeline_put(parent);
dma_fence_free(fence);
--
2.23.0.rc1
^ permalink raw reply related [flat|nested] 9+ messages in thread* ✗ Fi.CI.CHECKPATCH: warning for dma-buf/sw_sync: Synchronize signal vs syncpt free 2019-08-12 15:42 [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free Chris Wilson @ 2019-08-12 16:13 ` Patchwork 2019-08-12 16:46 ` ✓ Fi.CI.BAT: success " Patchwork ` (4 subsequent siblings) 5 siblings, 0 replies; 9+ messages in thread From: Patchwork @ 2019-08-12 16:13 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: dma-buf/sw_sync: Synchronize signal vs syncpt free URL : https://patchwork.freedesktop.org/series/65092/ State : warning == Summary == $ dim checkpatch origin/drm-tip 857ced2942e5 dma-buf/sw_sync: Synchronize signal vs syncpt free -:22: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #22: References: 0e2f733addbf ("dma-buf: make dma_fence structure a bit smaller v2") -:22: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0e2f733addbf ("dma-buf: make dma_fence structure a bit smaller v2")' #22: References: 0e2f733addbf ("dma-buf: make dma_fence structure a bit smaller v2") total: 1 errors, 1 warnings, 0 checks, 22 lines checked _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* ✓ Fi.CI.BAT: success for dma-buf/sw_sync: Synchronize signal vs syncpt free 2019-08-12 15:42 [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free Chris Wilson 2019-08-12 16:13 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork @ 2019-08-12 16:46 ` Patchwork 2019-08-12 17:04 ` [PATCH] " Koenig, Christian ` (3 subsequent siblings) 5 siblings, 0 replies; 9+ messages in thread From: Patchwork @ 2019-08-12 16:46 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: dma-buf/sw_sync: Synchronize signal vs syncpt free URL : https://patchwork.freedesktop.org/series/65092/ State : success == Summary == CI Bug Log - changes from CI_DRM_6687 -> Patchwork_13987 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/ Known issues ------------ Here are the changes found in Patchwork_13987 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_sync@basic-many-each: - fi-snb-2600: [PASS][1] -> [INCOMPLETE][2] ([fdo#105411]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/fi-snb-2600/igt@gem_sync@basic-many-each.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/fi-snb-2600/igt@gem_sync@basic-many-each.html * igt@i915_selftest@live_execlists: - fi-skl-gvtdvm: [PASS][3] -> [DMESG-FAIL][4] ([fdo#111108]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/fi-skl-gvtdvm/igt@i915_selftest@live_execlists.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/fi-skl-gvtdvm/igt@i915_selftest@live_execlists.html * igt@kms_chamelium@dp-edid-read: - fi-kbl-7500u: [PASS][5] -> [WARN][6] ([fdo#109483]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/fi-kbl-7500u/igt@kms_chamelium@dp-edid-read.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/fi-kbl-7500u/igt@kms_chamelium@dp-edid-read.html #### Possible fixes #### * igt@i915_module_load@reload-no-display: - fi-skl-6260u: [INCOMPLETE][7] -> [PASS][8] [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/fi-skl-6260u/igt@i915_module_load@reload-no-display.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/fi-skl-6260u/igt@i915_module_load@reload-no-display.html * igt@kms_chamelium@dp-crc-fast: - fi-cml-u2: [FAIL][9] ([fdo#110627]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html * igt@kms_chamelium@hdmi-hpd-fast: - fi-kbl-7500u: [FAIL][11] ([fdo#109485]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html * igt@kms_prop_blob@basic: - {fi-icl-u4}: [DMESG-WARN][13] ([fdo#105602]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/fi-icl-u4/igt@kms_prop_blob@basic.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/fi-icl-u4/igt@kms_prop_blob@basic.html - fi-icl-u3: [DMESG-WARN][15] ([fdo#107724]) -> [PASS][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/fi-icl-u3/igt@kms_prop_blob@basic.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/fi-icl-u3/igt@kms_prop_blob@basic.html #### Warnings #### * igt@i915_pm_rpm@basic-pci-d3-state: - fi-kbl-guc: [SKIP][17] ([fdo#109271]) -> [FAIL][18] ([fdo#107707]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/fi-kbl-guc/igt@i915_pm_rpm@basic-pci-d3-state.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/fi-kbl-guc/igt@i915_pm_rpm@basic-pci-d3-state.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411 [fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602 [fdo#107707]: https://bugs.freedesktop.org/show_bug.cgi?id=107707 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [fdo#109483]: https://bugs.freedesktop.org/show_bug.cgi?id=109483 [fdo#109485]: https://bugs.freedesktop.org/show_bug.cgi?id=109485 [fdo#110627]: https://bugs.freedesktop.org/show_bug.cgi?id=110627 [fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045 [fdo#111046 ]: https://bugs.freedesktop.org/show_bug.cgi?id=111046 [fdo#111108]: https://bugs.freedesktop.org/show_bug.cgi?id=111108 Participating hosts (54 -> 46) ------------------------------ Missing (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_6687 -> Patchwork_13987 CI-20190529: 20190529 CI_DRM_6687: 36e9b72a9b9150ffca7e5613c0e421570b8e92ce @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5128: a49a3a6cdbc4949c0ae8df5f3d8c3e476aefdea1 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_13987: 857ced2942e529fa3fc938274e6836bf4722e8c8 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 857ced2942e5 dma-buf/sw_sync: Synchronize signal vs syncpt free == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/ _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free 2019-08-12 15:42 [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free Chris Wilson 2019-08-12 16:13 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2019-08-12 16:46 ` ✓ Fi.CI.BAT: success " Patchwork @ 2019-08-12 17:04 ` Koenig, Christian 2019-08-12 19:05 ` Sasha Levin ` (2 subsequent siblings) 5 siblings, 0 replies; 9+ messages in thread From: Koenig, Christian @ 2019-08-12 17:04 UTC (permalink / raw) To: Chris Wilson, dri-devel@lists.freedesktop.org Cc: Gustavo Padovan, intel-gfx@lists.freedesktop.org, Sean Paul, stable@vger.kernel.org Am 12.08.19 um 17:42 schrieb Chris Wilson: > During release of the syncpt, we remove it from the list of syncpt and > the tree, but only if it is not already been removed. However, during > signaling, we first remove the syncpt from the list. So, if we > concurrently free and signal the syncpt, the free may decide that it is > not part of the tree and immediately free itself -- meanwhile the > signaler goes onto to use the now freed datastructure. > > In particular, we get struct by commit 0e2f733addbf ("dma-buf: make > dma_fence structure a bit smaller v2") as the cb_list is immediately > clobbered by the kfree_rcu. > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111381 > Fixes: d3862e44daa7 ("dma-buf/sw-sync: Fix locking around sync_timeline lists") > References: 0e2f733addbf ("dma-buf: make dma_fence structure a bit smaller v2") > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > Cc: Sumit Semwal <sumit.semwal@linaro.org> > Cc: Sean Paul <seanpaul@chromium.org> > Cc: Gustavo Padovan <gustavo@padovan.org> > Cc: Christian König <christian.koenig@amd.com> > Cc: <stable@vger.kernel.org> # v4.14+ Acked-by: Christian König <christian.koenig@amd.com> > --- > drivers/dma-buf/sw_sync.c | 13 +++++-------- > 1 file changed, 5 insertions(+), 8 deletions(-) > > diff --git a/drivers/dma-buf/sw_sync.c b/drivers/dma-buf/sw_sync.c > index 051f6c2873c7..27b1d549ed38 100644 > --- a/drivers/dma-buf/sw_sync.c > +++ b/drivers/dma-buf/sw_sync.c > @@ -132,17 +132,14 @@ static void timeline_fence_release(struct dma_fence *fence) > { > struct sync_pt *pt = dma_fence_to_sync_pt(fence); > struct sync_timeline *parent = dma_fence_parent(fence); > + unsigned long flags; > > + spin_lock_irqsave(fence->lock, flags); > if (!list_empty(&pt->link)) { > - unsigned long flags; > - > - spin_lock_irqsave(fence->lock, flags); > - if (!list_empty(&pt->link)) { > - list_del(&pt->link); > - rb_erase(&pt->node, &parent->pt_tree); > - } > - spin_unlock_irqrestore(fence->lock, flags); > + list_del(&pt->link); > + rb_erase(&pt->node, &parent->pt_tree); > } > + spin_unlock_irqrestore(fence->lock, flags); > > sync_timeline_put(parent); > dma_fence_free(fence); _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free 2019-08-12 15:42 [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free Chris Wilson ` (2 preceding siblings ...) 2019-08-12 17:04 ` [PATCH] " Koenig, Christian @ 2019-08-12 19:05 ` Sasha Levin 2019-08-12 23:52 ` ✗ Fi.CI.IGT: failure for " Patchwork [not found] ` <20190812190548.450CF20684@mail.kernel.org> 5 siblings, 0 replies; 9+ messages in thread From: Sasha Levin @ 2019-08-12 19:05 UTC (permalink / raw) To: Sasha Levin, Chris Wilson, dri-devel Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: d3862e44daa7 dma-buf/sw-sync: Fix locking around sync_timeline lists. The bot has tested the following trees: v5.2.8, v4.19.66, v4.14.138, v4.9.189. v5.2.8: Build OK! v4.19.66: Build OK! v4.14.138: Build OK! v4.9.189: Failed to apply! Possible dependencies: Unable to calculate NOTE: The patch will not be queued to stable trees until it is upstream. How should we proceed with this patch? -- Thanks, Sasha _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* ✗ Fi.CI.IGT: failure for dma-buf/sw_sync: Synchronize signal vs syncpt free 2019-08-12 15:42 [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free Chris Wilson ` (3 preceding siblings ...) 2019-08-12 19:05 ` Sasha Levin @ 2019-08-12 23:52 ` Patchwork [not found] ` <20190812190548.450CF20684@mail.kernel.org> 5 siblings, 0 replies; 9+ messages in thread From: Patchwork @ 2019-08-12 23:52 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: dma-buf/sw_sync: Synchronize signal vs syncpt free URL : https://patchwork.freedesktop.org/series/65092/ State : failure == Summary == CI Bug Log - changes from CI_DRM_6687_full -> Patchwork_13987_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_13987_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_13987_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_13987_full: ### IGT changes ### #### Possible regressions #### * igt@kms_plane@plane-position-hole-dpms-pipe-b-planes: - shard-kbl: NOTRUN -> [DMESG-WARN][1] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-kbl4/igt@kms_plane@plane-position-hole-dpms-pipe-b-planes.html * igt@sw_sync@sync_multi_producer_single_consumer: - shard-skl: [PASS][2] -> [INCOMPLETE][3] [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-skl1/igt@sw_sync@sync_multi_producer_single_consumer.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-skl2/igt@sw_sync@sync_multi_producer_single_consumer.html Known issues ------------ Here are the changes found in Patchwork_13987_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_exec_schedule@pi-ringfull-bsd: - shard-iclb: [PASS][4] -> [SKIP][5] ([fdo#111325]) +4 similar issues [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb7/igt@gem_exec_schedule@pi-ringfull-bsd.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb2/igt@gem_exec_schedule@pi-ringfull-bsd.html * igt@gem_userptr_blits@sync-unmap-cycles: - shard-apl: [PASS][6] -> [INCOMPLETE][7] ([fdo#103927]) +4 similar issues [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-apl6/igt@gem_userptr_blits@sync-unmap-cycles.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-apl7/igt@gem_userptr_blits@sync-unmap-cycles.html * igt@i915_suspend@sysfs-reader: - shard-apl: [PASS][8] -> [DMESG-WARN][9] ([fdo#108566]) +5 similar issues [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-apl2/igt@i915_suspend@sysfs-reader.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-apl4/igt@i915_suspend@sysfs-reader.html * igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled: - shard-skl: [PASS][10] -> [FAIL][11] ([fdo#103184] / [fdo#103232]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-skl6/igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-skl3/igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled.html * igt@kms_flip@2x-flip-vs-expired-vblank-interruptible: - shard-glk: [PASS][12] -> [FAIL][13] ([fdo#102887]) [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-glk3/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-glk5/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible.html * igt@kms_frontbuffer_tracking@fbc-badstride: - shard-iclb: [PASS][14] -> [FAIL][15] ([fdo#103167]) +6 similar issues [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb6/igt@kms_frontbuffer_tracking@fbc-badstride.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-badstride.html * igt@kms_plane_alpha_blend@pipe-a-coverage-7efc: - shard-skl: [PASS][16] -> [FAIL][17] ([fdo#108145]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-skl6/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-skl3/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html * igt@kms_psr@psr2_primary_blt: - shard-iclb: [PASS][18] -> [SKIP][19] ([fdo#109441]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb2/igt@kms_psr@psr2_primary_blt.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb1/igt@kms_psr@psr2_primary_blt.html * igt@kms_setmode@basic: - shard-apl: [PASS][20] -> [FAIL][21] ([fdo#99912]) [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-apl6/igt@kms_setmode@basic.html [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-apl4/igt@kms_setmode@basic.html * igt@prime_busy@hang-bsd2: - shard-iclb: [PASS][22] -> [SKIP][23] ([fdo#109276]) +16 similar issues [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb2/igt@prime_busy@hang-bsd2.html [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb3/igt@prime_busy@hang-bsd2.html * igt@sw_sync@sync_multi_producer_single_consumer: - shard-kbl: [PASS][24] -> [INCOMPLETE][25] ([fdo#103665]) [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-kbl2/igt@sw_sync@sync_multi_producer_single_consumer.html [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-kbl1/igt@sw_sync@sync_multi_producer_single_consumer.html - shard-hsw: [PASS][26] -> [INCOMPLETE][27] ([fdo#103540]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-hsw5/igt@sw_sync@sync_multi_producer_single_consumer.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-hsw7/igt@sw_sync@sync_multi_producer_single_consumer.html - shard-snb: [PASS][28] -> [INCOMPLETE][29] ([fdo#105411]) [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-snb2/igt@sw_sync@sync_multi_producer_single_consumer.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-snb6/igt@sw_sync@sync_multi_producer_single_consumer.html - shard-iclb: [PASS][30] -> [INCOMPLETE][31] ([fdo#107713]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb5/igt@sw_sync@sync_multi_producer_single_consumer.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb6/igt@sw_sync@sync_multi_producer_single_consumer.html - shard-glk: [PASS][32] -> [INCOMPLETE][33] ([fdo#103359] / [k.org#198133]) [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-glk6/igt@sw_sync@sync_multi_producer_single_consumer.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-glk8/igt@sw_sync@sync_multi_producer_single_consumer.html #### Possible fixes #### * igt@gem_ctx_shared@exec-single-timeline-bsd: - shard-iclb: [SKIP][34] ([fdo#110841]) -> [PASS][35] [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb1/igt@gem_ctx_shared@exec-single-timeline-bsd.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb5/igt@gem_ctx_shared@exec-single-timeline-bsd.html * igt@gem_eio@in-flight-internal-1us: - shard-skl: [DMESG-WARN][36] ([fdo#106107]) -> [PASS][37] [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-skl7/igt@gem_eio@in-flight-internal-1us.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-skl10/igt@gem_eio@in-flight-internal-1us.html * igt@gem_eio@reset-stress: - shard-snb: [FAIL][38] ([fdo#109661]) -> [PASS][39] [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-snb2/igt@gem_eio@reset-stress.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-snb6/igt@gem_eio@reset-stress.html * igt@gem_exec_balancer@smoke: - shard-iclb: [SKIP][40] ([fdo#110854]) -> [PASS][41] [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb7/igt@gem_exec_balancer@smoke.html [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb4/igt@gem_exec_balancer@smoke.html * igt@gem_exec_schedule@promotion-bsd1: - shard-iclb: [SKIP][42] ([fdo#109276]) -> [PASS][43] +17 similar issues [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb3/igt@gem_exec_schedule@promotion-bsd1.html [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb4/igt@gem_exec_schedule@promotion-bsd1.html * igt@gem_exec_schedule@reorder-wide-bsd: - shard-iclb: [SKIP][44] ([fdo#111325]) -> [PASS][45] +6 similar issues [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb1/igt@gem_exec_schedule@reorder-wide-bsd.html [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb5/igt@gem_exec_schedule@reorder-wide-bsd.html * igt@kms_cursor_crc@pipe-c-cursor-suspend: - shard-skl: [INCOMPLETE][46] ([fdo#110741]) -> [PASS][47] [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-skl3/igt@kms_cursor_crc@pipe-c-cursor-suspend.html [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-skl8/igt@kms_cursor_crc@pipe-c-cursor-suspend.html * igt@kms_flip@flip-vs-expired-vblank: - shard-glk: [FAIL][48] ([fdo#105363]) -> [PASS][49] +1 similar issue [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-glk2/igt@kms_flip@flip-vs-expired-vblank.html [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-glk3/igt@kms_flip@flip-vs-expired-vblank.html * igt@kms_flip@flip-vs-expired-vblank-interruptible: - shard-skl: [FAIL][50] ([fdo#105363]) -> [PASS][51] [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-skl9/igt@kms_flip@flip-vs-expired-vblank-interruptible.html [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-skl7/igt@kms_flip@flip-vs-expired-vblank-interruptible.html * igt@kms_flip@flip-vs-suspend-interruptible: - shard-kbl: [INCOMPLETE][52] ([fdo#103665]) -> [PASS][53] [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-kbl6/igt@kms_flip@flip-vs-suspend-interruptible.html [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-kbl4/igt@kms_flip@flip-vs-suspend-interruptible.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render: - shard-iclb: [FAIL][54] ([fdo#103167]) -> [PASS][55] +3 similar issues [54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render.html [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render.html * igt@kms_plane_alpha_blend@pipe-c-coverage-7efc: - shard-skl: [FAIL][56] ([fdo#108145] / [fdo#110403]) -> [PASS][57] [56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-skl4/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-skl5/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html * igt@kms_vblank@pipe-b-ts-continuation-suspend: - shard-apl: [DMESG-WARN][58] ([fdo#108566]) -> [PASS][59] +3 similar issues [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-apl8/igt@kms_vblank@pipe-b-ts-continuation-suspend.html [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-apl6/igt@kms_vblank@pipe-b-ts-continuation-suspend.html * igt@kms_vblank@pipe-b-wait-busy-hang: - shard-iclb: [INCOMPLETE][60] ([fdo#107713]) -> [PASS][61] +1 similar issue [60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb7/igt@kms_vblank@pipe-b-wait-busy-hang.html [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb8/igt@kms_vblank@pipe-b-wait-busy-hang.html * igt@perf@blocking: - shard-skl: [FAIL][62] ([fdo#110728]) -> [PASS][63] [62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-skl4/igt@perf@blocking.html [63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-skl5/igt@perf@blocking.html #### Warnings #### * igt@gem_mocs_settings@mocs-reset-bsd2: - shard-iclb: [SKIP][64] ([fdo#109276]) -> [FAIL][65] ([fdo#111330]) +1 similar issue [64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb7/igt@gem_mocs_settings@mocs-reset-bsd2.html [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb4/igt@gem_mocs_settings@mocs-reset-bsd2.html * igt@kms_dp_dsc@basic-dsc-enable-edp: - shard-iclb: [SKIP][66] ([fdo#109349]) -> [DMESG-WARN][67] ([fdo#107724]) [66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6687/shard-iclb5/igt@kms_dp_dsc@basic-dsc-enable-edp.html [67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13987/shard-iclb2/igt@kms_dp_dsc@basic-dsc-enable-edp.html [fdo#102887]: https://bugs.freedesktop.org/show_bug.cgi?id=102887 [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 [fdo#103184]: https://bugs.freedesktop.org/show_bug.cgi?id=103184 [fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232 [fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359 [fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540 [fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665 [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927 [fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363 [fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411 [fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145 [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566 [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276 [fdo#109349]: https://bugs.freedesktop.org/show_bug.cgi?id=109349 [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 [fdo#109661]: https://bugs.freedesktop.org/show_bug.cgi?id=109661 [fdo#110403]: https://bugs.freedesktop.org/show_bug.cgi?id=110403 [fdo#110728]: https://bugs.freedesktop.org/show_bug.cgi?id=110728 [fdo#110741]: https://bugs.freedesktop.org/show_bug.cgi?id=110741 [fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841 [fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854 [fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325 [fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330 [fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912 [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133 Participating hosts (10 -> 10) ------------------------------ No changes in participating hosts Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_6687 -> Patchwork_13987 CI-20190529: 20190529 CI_DRM_6687: 36e9b72a9b9150ffca7e5613c0e421570b8e92ce @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5128: a49a3a6cdbc4949c0ae8df5f3d8c3e476aefdea1 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_13987: 857ced2942e529fa3fc938274e6836bf4722e8c8 @ 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_13987/ _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
[parent not found: <20190812190548.450CF20684@mail.kernel.org>]
* Re: [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free [not found] ` <20190812190548.450CF20684@mail.kernel.org> @ 2019-08-14 17:24 ` Daniel Vetter 2019-08-15 1:46 ` Sasha Levin 0 siblings, 1 reply; 9+ messages in thread From: Daniel Vetter @ 2019-08-14 17:24 UTC (permalink / raw) To: Sasha Levin Cc: Gustavo Padovan, intel-gfx, stable, Sean Paul, dri-devel, Christian König Hi Sasha, On Mon, Aug 12, 2019 at 07:05:47PM +0000, Sasha Levin wrote: > Hi, > > [This is an automated email] > > This commit has been processed because it contains a "Fixes:" tag, > fixing commit: d3862e44daa7 dma-buf/sw-sync: Fix locking around sync_timeline lists. > > The bot has tested the following trees: v5.2.8, v4.19.66, v4.14.138, v4.9.189. > > v5.2.8: Build OK! > v4.19.66: Build OK! > v4.14.138: Build OK! > v4.9.189: Failed to apply! Possible dependencies: > Unable to calculate > > > NOTE: The patch will not be queued to stable trees until it is upstream. > > How should we proceed with this patch? The backporting instruction has an explicit # v4.14+ in there, so failure to apply to older kernels is expected. Can you perhaps teach this trick to your script perhaps? Iirc we're using the official format even. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free 2019-08-14 17:24 ` [PATCH] " Daniel Vetter @ 2019-08-15 1:46 ` Sasha Levin 2019-08-15 6:47 ` Daniel Vetter 0 siblings, 1 reply; 9+ messages in thread From: Sasha Levin @ 2019-08-15 1:46 UTC (permalink / raw) To: Daniel Vetter Cc: Chris Wilson, dri-devel, Gustavo Padovan, intel-gfx, stable, Christian König, Sean Paul On Wed, Aug 14, 2019 at 07:24:15PM +0200, Daniel Vetter wrote: >Hi Sasha, > >On Mon, Aug 12, 2019 at 07:05:47PM +0000, Sasha Levin wrote: >> Hi, >> >> [This is an automated email] >> >> This commit has been processed because it contains a "Fixes:" tag, >> fixing commit: d3862e44daa7 dma-buf/sw-sync: Fix locking around sync_timeline lists. >> >> The bot has tested the following trees: v5.2.8, v4.19.66, v4.14.138, v4.9.189. >> >> v5.2.8: Build OK! >> v4.19.66: Build OK! >> v4.14.138: Build OK! >> v4.9.189: Failed to apply! Possible dependencies: >> Unable to calculate >> >> >> NOTE: The patch will not be queued to stable trees until it is upstream. >> >> How should we proceed with this patch? > >The backporting instruction has an explicit # v4.14+ in there, so failure >to apply to older kernels is expected. > >Can you perhaps teach this trick to your script perhaps? Iirc we're using >the official format even. Hey Daniel, The script knows how to read stable tags :) It tested out 4.9 because the commit also has a fixes tag pointing to d3862e44daa7 ("dma-buf/sw-sync: Fix locking around sync_timeline lists."), which was backported to 4.9. Should this not be backported to 4.9, even though the commit it fixes is there? ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free 2019-08-15 1:46 ` Sasha Levin @ 2019-08-15 6:47 ` Daniel Vetter 0 siblings, 0 replies; 9+ messages in thread From: Daniel Vetter @ 2019-08-15 6:47 UTC (permalink / raw) To: Sasha Levin Cc: Daniel Vetter, Chris Wilson, dri-devel, Gustavo Padovan, intel-gfx, stable, Christian König, Sean Paul On Wed, Aug 14, 2019 at 09:46:41PM -0400, Sasha Levin wrote: > On Wed, Aug 14, 2019 at 07:24:15PM +0200, Daniel Vetter wrote: > > Hi Sasha, > > > > On Mon, Aug 12, 2019 at 07:05:47PM +0000, Sasha Levin wrote: > > > Hi, > > > > > > [This is an automated email] > > > > > > This commit has been processed because it contains a "Fixes:" tag, > > > fixing commit: d3862e44daa7 dma-buf/sw-sync: Fix locking around sync_timeline lists. > > > > > > The bot has tested the following trees: v5.2.8, v4.19.66, v4.14.138, v4.9.189. > > > > > > v5.2.8: Build OK! > > > v4.19.66: Build OK! > > > v4.14.138: Build OK! > > > v4.9.189: Failed to apply! Possible dependencies: > > > Unable to calculate > > > > > > > > > NOTE: The patch will not be queued to stable trees until it is upstream. > > > > > > How should we proceed with this patch? > > > > The backporting instruction has an explicit # v4.14+ in there, so failure > > to apply to older kernels is expected. > > > > Can you perhaps teach this trick to your script perhaps? Iirc we're using > > the official format even. > > Hey Daniel, > > The script knows how to read stable tags :) > > It tested out 4.9 because the commit also has a fixes tag pointing to > d3862e44daa7 ("dma-buf/sw-sync: Fix locking around sync_timeline > lists."), which was backported to 4.9. Ah makes sense, might be good to add a bit of output explaining that. > Should this not be backported to 4.9, even though the commit it fixes is > there? I guess it might actually be needed there. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2019-08-15 6:47 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-08-12 15:42 [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free Chris Wilson
2019-08-12 16:13 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-08-12 16:46 ` ✓ Fi.CI.BAT: success " Patchwork
2019-08-12 17:04 ` [PATCH] " Koenig, Christian
2019-08-12 19:05 ` Sasha Levin
2019-08-12 23:52 ` ✗ Fi.CI.IGT: failure for " Patchwork
[not found] ` <20190812190548.450CF20684@mail.kernel.org>
2019-08-14 17:24 ` [PATCH] " Daniel Vetter
2019-08-15 1:46 ` Sasha Levin
2019-08-15 6:47 ` Daniel Vetter
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox