From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: "Katragadda, MastanX" <mastanx.katragadda@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gem: missing boundary check in vm_access leads to OOB read/write (rev2)
Date: Thu, 10 Mar 2022 16:33:25 +0000 [thread overview]
Message-ID: <58b4eb80d22143388e4d80e06cffd842@intel.com> (raw)
In-Reply-To: <CAM0jSHOyD9J3T7vY7sP4Xbo3eTPkHhPhpRj9AmbH1ULrkRCeKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 8822 bytes --]
From: Matthew Auld <matthew.william.auld@gmail.com>
Sent: Thursday, March 10, 2022 1:21 AM
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Cc: Katragadda, MastanX <mastanx.katragadda@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gem: missing boundary check in vm_access leads to OOB read/write (rev2)
On Thu, 3 Mar 2022 at 06:48, Patchwork <patchwork@emeril.freedesktop.org<mailto:patchwork@emeril.freedesktop.org>> wrote:
Patch Details
Series:
drm/i915/gem: missing boundary check in vm_access leads to OOB read/write (rev2)
URL:
https://patchwork.freedesktop.org/series/100932/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/index.html
CI Bug Log - changes from CI_DRM_11316 -> Patchwork_22468
Summary
FAILURE
Serious unknown changes coming with Patchwork_22468 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_22468, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/index.html
Participating hosts (50 -> 41)
Additional (1): bat-adlp-4
Missing (10): fi-kbl-soraka shard-tglu bat-dg1-5 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 shard-rkl shard-dg1 bat-jsl-2 fi-bdw-samus
Possible new issues
Here are the unknown changes that may have been introduced in Patchwork_22468:
IGT changes
Possible regressions
* igt@gem_exec_suspend@basic-s0@smem:
* fi-kbl-7567u: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/fi-kbl-7567u/igt@gem_exec_suspend@basic-s0@smem.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/fi-kbl-7567u/igt@gem_exec_suspend@basic-s0@smem.html>
Lakshmi: This issue is related to https://gitlab.freedesktop.org/drm/intel/-/issues/4116
* igt@i915_pm_rpm@basic-pci-d3-state:
* fi-skl-6600u: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/fi-skl-6600u/igt@i915_pm_rpm@basic-pci-d3-state.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/fi-skl-6600u/igt@i915_pm_rpm@basic-pci-d3-state.html>
Lakshmi: This looks like a new issue, so filed
https://gitlab.freedesktop.org/drm/intel/-/issues/5290
igt@i915_pm_rpm@basic-pci-d3-state - fail - Failed assertion: igt_wait(device_in_pci_d3(), \d+, \d+)
These failures are not related.
*
Known issues
Here are the changes found in Patchwork_22468 that come from known issues:
IGT changes
Issues hit
* igt@gem_lmem_swapping@basic:
* bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@gem_lmem_swapping@basic.html> (i915#4613<https://gitlab.freedesktop.org/drm/intel/issues/4613>) +3 similar issues
* igt@gem_tiled_pread_basic:
* bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@gem_tiled_pread_basic.html> (i915#3282<https://gitlab.freedesktop.org/drm/intel/issues/3282>)
* igt@kms_busy@basic@modeset:
* bat-adlp-4: NOTRUN -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@kms_busy@basic@modeset.html> (i915#3576<https://gitlab.freedesktop.org/drm/intel/issues/3576>)
* igt@kms_chamelium@vga-hpd-fast:
* bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@kms_chamelium@vga-hpd-fast.html> (fdo#111827<https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +8 similar issues
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
* bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html> (i915#4103<https://gitlab.freedesktop.org/drm/intel/issues/4103>) +1 similar issue
* igt@kms_force_connector_basic@force-load-detect:
* bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@kms_force_connector_basic@force-load-detect.html> (fdo#109285<https://bugs.freedesktop.org/show_bug.cgi?id=109285>)
* igt@prime_vgem@basic-fence-read:
* bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@prime_vgem@basic-fence-read.html> (i915#3291<https://gitlab.freedesktop.org/drm/intel/issues/3291> / i915#3708<https://gitlab.freedesktop.org/drm/intel/issues/3708>) +2 similar issues
* igt@prime_vgem@basic-userptr:
* bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@prime_vgem@basic-userptr.html> (i915#3301<https://gitlab.freedesktop.org/drm/intel/issues/3301> / i915#3708<https://gitlab.freedesktop.org/drm/intel/issues/3708>)
* igt@runner@aborted:
* fi-kbl-7567u: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/fi-kbl-7567u/igt@runner@aborted.html> (i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312>)
* fi-bdw-5557u: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/fi-bdw-5557u/igt@runner@aborted.html> (i915#2426<https://gitlab.freedesktop.org/drm/intel/issues/2426> / i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312>)
Possible fixes
* igt@gem_exec_suspend@basic-s3@smem:
* fi-bdw-5557u: INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html> (i915#146<https://gitlab.freedesktop.org/drm/intel/issues/146>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html>
* igt@i915_pm_rpm@module-reload:
* fi-icl-u2: FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/fi-icl-u2/igt@i915_pm_rpm@module-reload.html> (i915#3049<https://gitlab.freedesktop.org/drm/intel/issues/3049>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/fi-icl-u2/igt@i915_pm_rpm@module-reload.html>
* igt@i915_selftest@live@evict:
* {bat-rpls-2}: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/bat-rpls-2/igt@i915_selftest@live@evict.html> (i915#4391<https://gitlab.freedesktop.org/drm/intel/issues/4391>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-rpls-2/igt@i915_selftest@live@evict.html> +1 similar issue
* igt@i915_selftest@live@hangcheck:
* fi-icl-u2: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/fi-icl-u2/igt@i915_selftest@live@hangcheck.html> (i915#2867<https://gitlab.freedesktop.org/drm/intel/issues/2867>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/fi-icl-u2/igt@i915_selftest@live@hangcheck.html> +7 similar issues
* bat-dg1-6: DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/bat-dg1-6/igt@i915_selftest@live@hangcheck.html> (i915#4494<https://gitlab.freedesktop.org/drm/intel/issues/4494> / i915#4957<https://gitlab.freedesktop.org/drm/intel/issues/4957>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-dg1-6/igt@i915_selftest@live@hangcheck.html>
* igt@i915_selftest@live@workarounds:
* {bat-adlp-6}: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/bat-adlp-6/igt@i915_selftest@live@workarounds.html> (i915#5068<https://gitlab.freedesktop.org/drm/intel/issues/5068>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-6/igt@i915_selftest@live@workarounds.html>
* igt@kms_busy@basic@flip:
* {bat-adlp-6}: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/bat-adlp-6/igt@kms_busy@basic@flip.html> (i915#3576<https://gitlab.freedesktop.org/drm/intel/issues/3576>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-6/igt@kms_busy@basic@flip.html> +1 similar issue
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
Build changes
* Linux: CI_DRM_11316 -> Patchwork_22468
CI-20190529: 20190529
CI_DRM_11316: 41f05cc5d1eed1879e572ef203ef2dbe9a75aff8 @ git://anongit.freedesktop.org/gfx-ci/linux<http://anongit.freedesktop.org/gfx-ci/linux>
IGT_6361: 2372a4beb6a33c5f0799a4a8ccbb93794f52dbca @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_22468: 49f7781dc74065aad8b8517b6a9e2d963890da62 @ git://anongit.freedesktop.org/gfx-ci/linux<http://anongit.freedesktop.org/gfx-ci/linux>
== Linux commits ==
49f7781dc740 drm/i915/gem: missing boundary check in vm_access leads to OOB read/write
[-- Attachment #2: Type: text/html, Size: 31318 bytes --]
next prev parent reply other threads:[~2022-03-10 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 6:04 [Intel-gfx] [v2] drm/i915/gem: missing boundary check in vm_access leads to OOB read/write Mastan Katragadda
2022-03-03 6:48 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gem: missing boundary check in vm_access leads to OOB read/write (rev2) Patchwork
2022-03-10 9:20 ` Matthew Auld
2022-03-10 16:33 ` Vudum, Lakshminarayana [this message]
2022-03-03 9:00 ` [Intel-gfx] [v2] drm/i915/gem: missing boundary check in vm_access leads to OOB read/write Tvrtko Ursulin
2022-03-03 10:43 ` Matthew Auld
2022-03-04 4:07 ` Katragadda, MastanX
2022-03-09 1:46 ` Katragadda, MastanX
2022-03-09 11:19 ` Katragadda, MastanX
2022-03-09 11:45 ` Matthew Auld
2022-03-11 10:37 ` Matthew Auld
2022-03-03 9:33 ` Jani Nikula
2022-03-10 15:40 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gem: missing boundary check in vm_access leads to OOB read/write (rev2) Patchwork
2022-03-10 15:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-10 18:48 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=58b4eb80d22143388e4d80e06cffd842@intel.com \
--to=lakshminarayana.vudum@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mastanx.katragadda@intel.com \
--cc=matthew.william.auld@gmail.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.