August 2019 - Linux-stable-mirror

stable-rc/linux-4.4.y boot: 98 boots: 2 failed, 83 passed with 12 offline, 1 conflict (v4.4.189-80-gae3cc2f8a3ef)

by kernelci.org bot

stable-rc/linux-4.4.y boot: 98 boots: 2 failed, 83 passed with 12 offline, 1 conflict (v4.4.189-80-gae3cc2f8a3ef) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.189-80-… Tree: stable-rc Branch: linux-4.4.y Git Describe: v4.4.189-80-gae3cc2f8a3ef Git Commit: ae3cc2f8a3ef3c529b3d8b981e7da05b2b2fc8ee Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 46 unique boards, 19 SoC families, 14 builds out of 190 Boot Regressions Detected: arm: bcm2835_defconfig: gcc-8: bcm2835-rpi-b: lab-baylibre-seattle: new failure (last pass: v4.4.189-75-g138891b71be5) qcom_defconfig: gcc-8: qcom-apq8064-cm-qs600: lab-baylibre-seattle: failing since 6 days (last pass: v4.4.189 - first fail: v4.4.189-32-g35ba3146be27) qcom-apq8064-ifc6410: lab-baylibre-seattle: failing since 6 days (last pass: v4.4.189 - first fail: v4.4.189-32-g35ba3146be27) sama5_defconfig: gcc-8: at91-sama5d4_xplained: lab-baylibre-seattle: new failure (last pass: v4.4.189-75-g138891b71be5) Boot Failures Detected: arm64: defconfig: gcc-8: qcom-qdf2400: 1 failed lab arm: multi_v7_defconfig: gcc-8: stih410-b2120: 1 failed lab Offline Platforms: arm64: defconfig: gcc-8 apq8016-sbc: 1 offline lab arm: bcm2835_defconfig: gcc-8 bcm2835-rpi-b: 1 offline lab sama5_defconfig: gcc-8 at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: gcc-8 alpine-db: 1 offline lab at91-sama5d4_xplained: 1 offline lab qcom-apq8064-cm-qs600: 1 offline lab qcom-apq8064-ifc6410: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab qcom-apq8064-ifc6410: 1 offline lab sunxi_defconfig: gcc-8 sun5i-r8-chip: 1 offline lab Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) x86_64: x86_64_defconfig: qemu: lab-baylibre: FAIL (gcc-8) lab-drue: PASS (gcc-8) lab-linaro-lkft: PASS (gcc-8) lab-mhart: PASS (gcc-8) lab-collabora: PASS (gcc-8) --- For more info write to <info(a)kernelci.org>

5 years, 4 months

1
0
0 0

✅ PASS: Test report for kernel 5.2.10-rc1-6451706.cki (stable)

by CKI Project

Hello, We ran automated tests on a recent commit from this kernel tree: Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: 6451706234b4 - Linux 5.2.10-rc1 The results of these automated tests are provided below. Overall result: PASSED Merge: OK Compile: OK Tests: OK All kernel binaries, config files, and logs are available for download here: https://artifacts.cki-project.org/pipelines/114911 Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Compile testing --------------- We compiled the kernel for 3 architectures: aarch64: make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg ppc64le: make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg x86_64: make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test [0] ✅ Podman system integration test (as root) [1] ✅ Podman system integration test (as user) [1] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ jvm test suite [4] ✅ Memory function: memfd_create [5] ✅ AMTU (Abstract Machine Test Utility) [6] ✅ LTP: openposix test suite [7] ✅ Ethernet drivers sanity [8] ✅ Networking socket: fuzz [9] ✅ Networking sctp-auth: sockopts test [10] ✅ Networking: igmp conformance test [11] ✅ Networking TCP: keepalive test [12] ✅ Networking UDP: socket [13] ✅ Networking tunnel: gre basic [14] ✅ Networking tunnel: vxlan basic [15] ✅ audit: audit testsuite test [16] ✅ httpd: mod_ssl smoke sanity [17] ✅ iotop: sanity [18] ✅ tuned: tune-processes-through-perf [19] ✅ Usex - version 1.9-29 [20] ✅ storage: SCSI VPD [21] 🚧 ✅ Networking route: pmtu [22] 🚧 ✅ Networking route_func: local [23] 🚧 ✅ Networking route_func: forward [23] 🚧 ✅ Networking tunnel: geneve basic test [24] 🚧 ✅ Networking ipsec: basic netns transport [25] 🚧 ✅ Networking ipsec: basic netns tunnel [25] 🚧 ✅ trace: ftrace/tracer [26] Host 2: ✅ Boot test [0] ✅ xfstests: ext4 [27] ✅ xfstests: xfs [27] ✅ selinux-policy: serge-testsuite [28] ✅ lvm thinp sanity [29] ✅ storage: software RAID testing [30] 🚧 ✅ Storage blktests [31] ppc64le: Host 1: ✅ Boot test [0] ✅ Podman system integration test (as root) [1] ✅ Podman system integration test (as user) [1] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ jvm test suite [4] ✅ Memory function: memfd_create [5] ✅ AMTU (Abstract Machine Test Utility) [6] ✅ LTP: openposix test suite [7] ✅ Ethernet drivers sanity [8] ✅ Networking socket: fuzz [9] ✅ Networking sctp-auth: sockopts test [10] ✅ Networking TCP: keepalive test [12] ✅ Networking UDP: socket [13] ✅ Networking tunnel: gre basic [14] ✅ Networking tunnel: vxlan basic [15] ✅ audit: audit testsuite test [16] ✅ httpd: mod_ssl smoke sanity [17] ✅ iotop: sanity [18] ✅ tuned: tune-processes-through-perf [19] ✅ Usex - version 1.9-29 [20] 🚧 ✅ Networking route: pmtu [22] 🚧 ✅ Networking route_func: local [23] 🚧 ✅ Networking route_func: forward [23] 🚧 ✅ Networking tunnel: geneve basic test [24] 🚧 ✅ Networking ipsec: basic netns tunnel [25] 🚧 ✅ trace: ftrace/tracer [26] Host 2: ✅ Boot test [0] ✅ xfstests: ext4 [27] ✅ xfstests: xfs [27] ✅ selinux-policy: serge-testsuite [28] ✅ lvm thinp sanity [29] ✅ storage: software RAID testing [30] 🚧 ✅ Storage blktests [31] x86_64: Host 1: ✅ Boot test [0] ✅ Podman system integration test (as root) [1] ✅ Podman system integration test (as user) [1] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ jvm test suite [4] ✅ Memory function: memfd_create [5] ✅ AMTU (Abstract Machine Test Utility) [6] ✅ LTP: openposix test suite [7] ✅ Ethernet drivers sanity [8] ✅ Networking socket: fuzz [9] ✅ Networking sctp-auth: sockopts test [10] ✅ Networking: igmp conformance test [11] ✅ Networking TCP: keepalive test [12] ✅ Networking UDP: socket [13] ✅ Networking tunnel: gre basic [14] ✅ Networking tunnel: vxlan basic [15] ✅ audit: audit testsuite test [16] ✅ httpd: mod_ssl smoke sanity [17] ✅ iotop: sanity [18] ✅ tuned: tune-processes-through-perf [19] ✅ pciutils: sanity smoke test [32] ✅ Usex - version 1.9-29 [20] ✅ storage: SCSI VPD [21] ✅ stress: stress-ng [33] 🚧 ✅ Networking route: pmtu [22] 🚧 ✅ Networking route_func: local [23] 🚧 ✅ Networking route_func: forward [23] 🚧 ✅ Networking tunnel: geneve basic test [24] 🚧 ✅ Networking ipsec: basic netns transport [25] 🚧 ✅ Networking ipsec: basic netns tunnel [25] 🚧 ✅ trace: ftrace/tracer [26] Host 2: ✅ Boot test [0] ✅ xfstests: ext4 [27] ✅ xfstests: xfs [27] ✅ selinux-policy: serge-testsuite [28] ✅ lvm thinp sanity [29] ✅ storage: software RAID testing [30] 🚧 ✅ Storage blktests [31] Test source: 💚 Pull requests are welcome for new tests or improvements to existing tests! [0]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution… [1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/container/p… [2]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution… [3]: https://github.com/CKI-project/tests-beaker/archive/master.zip#filesystems/… [4]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/jvm [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/memory/func… [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#misc/amtu [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution… [8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/… [9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/… [10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#networking/s… [11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#networking/i… [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#networking/t… [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#networking/u… [14]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/… [15]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/… [16]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/aud… [17]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/htt… [18]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/iot… [19]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tun… [20]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/us… [21]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/scsi… [22]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/… [23]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/… [24]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/… [25]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/… [26]: https://github.com/CKI-project/tests-beaker/archive/master.zip#trace/ftrace… [27]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/filesystems… [28]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/se… [29]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/… [30]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/swra… [31]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/blk [32]: https://github.com/CKI-project/tests-beaker/archive/master.zip#pciutils/san… [33]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stres… Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed.

5 years, 4 months

1
0
0 0

stable-rc/linux-5.2.y boot: 134 boots: 0 failed, 114 passed with 18 offline, 1 untried/unknown, 1 conflict (v5.2.9-136-g6451706234b4)

by kernelci.org bot

stable-rc/linux-5.2.y boot: 134 boots: 0 failed, 114 passed with 18 offline, 1 untried/unknown, 1 conflict (v5.2.9-136-g6451706234b4) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.2.y/kernel/v5.2.… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.2.y/kernel/v5.2.9-136-g… Tree: stable-rc Branch: linux-5.2.y Git Describe: v5.2.9-136-g6451706234b4 Git Commit: 6451706234b494afc737f64c0b442d6594c4ccf9 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 77 unique boards, 27 SoC families, 17 builds out of 209 Boot Regressions Detected: arm: qcom_defconfig: gcc-8: qcom-apq8064-cm-qs600: lab-baylibre-seattle: failing since 6 days (last pass: v5.2.8 - first fail: v5.2.8-145-g2440e485aeda) qcom-apq8064-ifc6410: lab-baylibre-seattle: failing since 6 days (last pass: v5.2.8 - first fail: v5.2.8-145-g2440e485aeda) Offline Platforms: mips: pistachio_defconfig: gcc-8 pistachio_marduk: 1 offline lab arm64: defconfig: gcc-8 apq8016-sbc: 1 offline lab juno-r2: 1 offline lab meson-g12a-x96-max: 1 offline lab meson-gxbb-odroidc2: 1 offline lab mt7622-rfb1: 1 offline lab arm: bcm2835_defconfig: gcc-8 bcm2835-rpi-b: 1 offline lab sama5_defconfig: gcc-8 at91-sama5d4_xplained: 1 offline lab at91-sama5d4ek: 1 offline lab multi_v7_defconfig: gcc-8 alpine-db: 1 offline lab at91-sama5d4_xplained: 1 offline lab at91-sama5d4ek: 1 offline lab qcom-apq8064-cm-qs600: 1 offline lab qcom-apq8064-ifc6410: 1 offline lab sun5i-r8-chip: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab qcom-apq8064-ifc6410: 1 offline lab sunxi_defconfig: gcc-8 sun5i-r8-chip: 1 offline lab Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: omap2plus_defconfig: omap4-panda: lab-baylibre: PASS (gcc-8) lab-baylibre-seattle: PASS (gcc-8) lab-collabora: FAIL (gcc-8) --- For more info write to <info(a)kernelci.org>

5 years, 4 months

1
0
0 0

stable-rc/linux-4.19.y boot: 122 boots: 0 failed, 106 passed with 16 offline (v4.19.67-87-gbfa969cef25a)

by kernelci.org bot

stable-rc/linux-4.19.y boot: 122 boots: 0 failed, 106 passed with 16 offline (v4.19.67-87-gbfa969cef25a) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.1… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.19.y/kernel/v4.19.67-87… Tree: stable-rc Branch: linux-4.19.y Git Describe: v4.19.67-87-gbfa969cef25a Git Commit: bfa969cef25aed1baa68fa3eeb12fe09af9b0159 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 68 unique boards, 26 SoC families, 17 builds out of 206 Boot Regressions Detected: arm: qcom_defconfig: gcc-8: qcom-apq8064-cm-qs600: lab-baylibre-seattle: failing since 6 days (last pass: v4.19.66 - first fail: v4.19.66-92-gf777613d3df0) qcom-apq8064-ifc6410: lab-baylibre-seattle: failing since 6 days (last pass: v4.19.66 - first fail: v4.19.66-92-gf777613d3df0) Offline Platforms: mips: pistachio_defconfig: gcc-8 pistachio_marduk: 1 offline lab arm64: defconfig: gcc-8 apq8016-sbc: 1 offline lab juno-r2: 1 offline lab meson-gxbb-odroidc2: 1 offline lab mt7622-rfb1: 1 offline lab arm: bcm2835_defconfig: gcc-8 bcm2835-rpi-b: 1 offline lab sama5_defconfig: gcc-8 at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: gcc-8 alpine-db: 1 offline lab at91-sama5d4_xplained: 1 offline lab qcom-apq8064-cm-qs600: 1 offline lab qcom-apq8064-ifc6410: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab qcom-apq8064-ifc6410: 1 offline lab sunxi_defconfig: gcc-8 sun5i-r8-chip: 1 offline lab --- For more info write to <info(a)kernelci.org>

5 years, 4 months

1
0
0 0

stable-rc/linux-4.9.y boot: 105 boots: 0 failed, 90 passed with 15 offline (v4.9.189-105-g9c965ba1a288)

by kernelci.org bot

stable-rc/linux-4.9.y boot: 105 boots: 0 failed, 90 passed with 15 offline (v4.9.189-105-g9c965ba1a288) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.189-105… Tree: stable-rc Branch: linux-4.9.y Git Describe: v4.9.189-105-g9c965ba1a288 Git Commit: 9c965ba1a28830bae31287b606dbb5479b7e4eed Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 51 unique boards, 21 SoC families, 15 builds out of 197 Boot Regressions Detected: arm: bcm2835_defconfig: gcc-8: bcm2835-rpi-b: lab-baylibre-seattle: failing since 1 day (last pass: v4.9.189-96-g4cd56b7fcd6f - first fail: v4.9.189-97-g6971d2d959e5) sama5_defconfig: gcc-8: at91-sama5d4_xplained: lab-baylibre-seattle: failing since 1 day (last pass: v4.9.189-96-g4cd56b7fcd6f - first fail: v4.9.189-97-g6971d2d959e5) socfpga_defconfig: gcc-8: socfpga_cyclone5_de0_sockit: lab-baylibre-seattle: failing since 1 day (last pass: v4.9.189-96-g4cd56b7fcd6f - first fail: v4.9.189-97-g6971d2d959e5) arm64: defconfig: gcc-8: apq8016-sbc: lab-baylibre-seattle: failing since 1 day (last pass: v4.9.189-96-g4cd56b7fcd6f - first fail: v4.9.189-97-g6971d2d959e5) juno-r2: lab-baylibre-seattle: failing since 1 day (last pass: v4.9.189-96-g4cd56b7fcd6f - first fail: v4.9.189-97-g6971d2d959e5) meson-gxbb-odroidc2: lab-baylibre-seattle: failing since 1 day (last pass: v4.9.189-96-g4cd56b7fcd6f - first fail: v4.9.189-97-g6971d2d959e5) Offline Platforms: arm64: defconfig: gcc-8 apq8016-sbc: 1 offline lab juno-r2: 1 offline lab meson-gxbb-odroidc2: 1 offline lab arm: sama5_defconfig: gcc-8 at91-sama5d4_xplained: 1 offline lab sunxi_defconfig: gcc-8 sun5i-r8-chip: 1 offline lab bcm2835_defconfig: gcc-8 bcm2835-rpi-b: 1 offline lab multi_v7_defconfig: gcc-8 alpine-db: 1 offline lab at91-sama5d4_xplained: 1 offline lab qcom-apq8064-cm-qs600: 1 offline lab qcom-apq8064-ifc6410: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab socfpga_defconfig: gcc-8 socfpga_cyclone5_de0_sockit: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab qcom-apq8064-ifc6410: 1 offline lab --- For more info write to <info(a)kernelci.org>

5 years, 4 months

1
0
0 0

[PATCH] drm/i915: Do not create a new max_bpc prop for MST connectors

by Ville Syrjala

From: Ville Syrjälä <ville.syrjala(a)linux.intel.com> We're not allowed to create new properties after device registration so for MST connectors we need to either create the max_bpc property earlier, or we reuse one we already have. Let's do the latter apporach since the corresponding SST connector already has the prop and its min/max are correct also for the MST connector. The problem was highlighted by commit 4f5368b5541a ("drm/kms: Catch mode_object lifetime errors") which results in the following spew: [ 1330.878941] WARNING: CPU: 2 PID: 1554 at drivers/gpu/drm/drm_mode_object.c:45 __drm_mode_object_add+0xa0/0xb0 [drm] ... [ 1330.879008] Call Trace: [ 1330.879023] drm_property_create+0xba/0x180 [drm] [ 1330.879036] drm_property_create_range+0x15/0x30 [drm] [ 1330.879048] drm_connector_attach_max_bpc_property+0x62/0x80 [drm] [ 1330.879086] intel_dp_add_mst_connector+0x11f/0x140 [i915] [ 1330.879094] drm_dp_add_port.isra.20+0x20b/0x440 [drm_kms_helper] ... Cc: stable(a)vger.kernel.org Cc: Lyude Paul <lyude(a)redhat.com> Cc: sunpeng.li(a)amd.com Cc: Daniel Vetter <daniel.vetter(a)ffwll.ch> Cc: Sean Paul <sean(a)poorly.run> Fixes: 5ca0ef8a56b8 ("drm/i915: Add max_bpc property for DP MST") Signed-off-by: Ville Syrjälä <ville.syrjala(a)linux.intel.com> --- drivers/gpu/drm/i915/display/intel_dp_mst.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c index 83faa246e361..9748581c1d62 100644 --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c @@ -536,7 +536,15 @@ static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topolo intel_attach_force_audio_property(connector); intel_attach_broadcast_rgb_property(connector); - drm_connector_attach_max_bpc_property(connector, 6, 12); + + /* + * Reuse the prop from the SST connector because we're + * not allowed to create new props after device registration. + */ + connector->max_bpc_property = + intel_dp->attached_connector->base.max_bpc_property; + if (connector->max_bpc_property) + drm_connector_attach_max_bpc_property(connector, 6, 12); return connector; -- 2.21.0

5 years, 4 months

4
3
0 0

[PATCH 1/2] drm/i915: Don't deballoon unused ggtt drm_mm_node in linux guest

by Xiong Zhang

The following call trace may exist in linux guest dmesg when guest i915 driver is unloaded. [ 90.776610] [drm:vgt_deballoon_space.isra.0 [i915]] deballoon space: range [0x0 - 0x0] 0 KiB. [ 90.776621] BUG: unable to handle kernel NULL pointer dereference at 00000000000000c0 [ 90.776691] IP: drm_mm_remove_node+0x4d/0x320 [drm] [ 90.776718] PGD 800000012c7d0067 P4D 800000012c7d0067 PUD 138e4c067 PMD 0 [ 90.777091] task: ffff9adab60f2f00 task.stack: ffffaf39c0fe0000 [ 90.777142] RIP: 0010:drm_mm_remove_node+0x4d/0x320 [drm] [ 90.777573] Call Trace: [ 90.777653] intel_vgt_deballoon+0x4c/0x60 [i915] [ 90.777729] i915_ggtt_cleanup_hw+0x121/0x190 [i915] [ 90.777792] i915_driver_unload+0x145/0x180 [i915] [ 90.777856] i915_pci_remove+0x15/0x20 [i915] [ 90.777890] pci_device_remove+0x3b/0xc0 [ 90.777916] device_release_driver_internal+0x157/0x220 [ 90.777945] driver_detach+0x39/0x70 [ 90.777967] bus_remove_driver+0x51/0xd0 [ 90.777990] pci_unregister_driver+0x23/0x90 [ 90.778019] SyS_delete_module+0x1da/0x240 [ 90.778045] entry_SYSCALL_64_fastpath+0x24/0x87 [ 90.778072] RIP: 0033:0x7f34312af067 [ 90.778092] RSP: 002b:00007ffdea3da0d8 EFLAGS: 00000206 [ 90.778297] RIP: drm_mm_remove_node+0x4d/0x320 [drm] RSP: ffffaf39c0fe3dc0 [ 90.778344] ---[ end trace f4b1bc8305fc59dd ]--- Four drm_mm_node are used to reserve guest ggtt space, but some of them may be skipped and not initialised due to space constraints in intel_vgt_balloon(). If drm_mm_remove_node() is called with uninitialized drm_mm_node, the above call trace occurs. This patch check drm_mm_node's validity before calling drm_mm_remove_node(). Fixes: ff8f797557c7("drm/i915: return the correct usable aperture size under gvt environment") Cc: stable(a)vger.kernel.org Signed-off-by: Xiong Zhang <xiong.y.zhang(a)intel.com> --- drivers/gpu/drm/i915/i915_vgpu.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/i915/i915_vgpu.c b/drivers/gpu/drm/i915/i915_vgpu.c index bf2b837..d2fd66f 100644 --- a/drivers/gpu/drm/i915/i915_vgpu.c +++ b/drivers/gpu/drm/i915/i915_vgpu.c @@ -119,6 +119,9 @@ static struct _balloon_info_ bl_info; static void vgt_deballoon_space(struct i915_ggtt *ggtt, struct drm_mm_node *node) { + if (!node->allocated) + return; + DRM_DEBUG_DRIVER("deballoon space: range [0x%llx - 0x%llx] %llu KiB.\n", node->start, node->start + node->size, -- 2.7.4

5 years, 4 months

3
2
0 0

patch "usb-storage: Add new JMS567 revision to unusual_devs" added to usb-linus

by gregkh＠linuxfoundation.org

This is a note to let you know that I've just added the patch titled usb-storage: Add new JMS567 revision to unusual_devs to my usb git tree which can be found at git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git in the usb-linus branch. The patch will show up in the next release of the linux-next tree (usually sometime within the next 24 hours during the week.) The patch will hopefully also be merged in Linus's tree for the next -rc kernel release. If you have any questions about this process, please let me know. >From 08d676d1685c2a29e4d0e1b0242324e564d4589e Mon Sep 17 00:00:00 2001 From: Henk van der Laan <opensource(a)henkvdlaan.com> Date: Fri, 16 Aug 2019 22:08:47 +0200 Subject: usb-storage: Add new JMS567 revision to unusual_devs Revision 0x0117 suffers from an identical issue to earlier revisions, therefore it should be added to the quirks list. Signed-off-by: Henk van der Laan <opensource(a)henkvdlaan.com> Cc: stable <stable(a)vger.kernel.org> Link: https://lore.kernel.org/r/20190816200847.21366-1-opensource@henkvdlaan.com Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> --- drivers/usb/storage/unusual_devs.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/storage/unusual_devs.h b/drivers/usb/storage/unusual_devs.h index ea0d27a94afe..1cd9b6305b06 100644 --- a/drivers/usb/storage/unusual_devs.h +++ b/drivers/usb/storage/unusual_devs.h @@ -2100,7 +2100,7 @@ UNUSUAL_DEV( 0x14cd, 0x6600, 0x0201, 0x0201, US_FL_IGNORE_RESIDUE ), /* Reported by Michael Büsch <m(a)bues.ch> */ -UNUSUAL_DEV( 0x152d, 0x0567, 0x0114, 0x0116, +UNUSUAL_DEV( 0x152d, 0x0567, 0x0114, 0x0117, "JMicron", "USB to ATA/ATAPI Bridge", USB_SC_DEVICE, USB_PR_DEVICE, NULL, -- 2.23.0

5 years, 4 months

1
0
0 0

patch "usb: chipidea: udc: don't do hardware access if gadget has stopped" added to usb-linus

by gregkh＠linuxfoundation.org

This is a note to let you know that I've just added the patch titled usb: chipidea: udc: don't do hardware access if gadget has stopped to my usb git tree which can be found at git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git in the usb-linus branch. The patch will show up in the next release of the linux-next tree (usually sometime within the next 24 hours during the week.) The patch will hopefully also be merged in Linus's tree for the next -rc kernel release. If you have any questions about this process, please let me know. >From cbe85c88ce80fb92956a0793518d415864dcead8 Mon Sep 17 00:00:00 2001 From: Peter Chen <peter.chen(a)nxp.com> Date: Tue, 20 Aug 2019 02:07:58 +0000 Subject: usb: chipidea: udc: don't do hardware access if gadget has stopped After _gadget_stop_activity is executed, we can consider the hardware operation for gadget has finished, and the udc can be stopped and enter low power mode. So, any later hardware operations (from usb_ep_ops APIs or usb_gadget_ops APIs) should be considered invalid, any deinitializatons has been covered at _gadget_stop_activity. I meet this problem when I plug out usb cable from PC using mass_storage gadget, my callstack like: vbus interrupt->.vbus_session-> composite_disconnect ->pm_runtime_put_sync(&_gadget->dev), the composite_disconnect will call fsg_disable, but fsg_disable calls usb_ep_disable using async way, there are register accesses for usb_ep_disable. So sometimes, I get system hang due to visit register without clock, sometimes not. The Linux Kernel USB maintainer Alan Stern suggests this kinds of solution. See: http://marc.info/?l=linux-usb&m=138541769810983&w=2. Cc: <stable(a)vger.kernel.org> #v4.9+ Signed-off-by: Peter Chen <peter.chen(a)nxp.com> Link: https://lore.kernel.org/r/20190820020503.27080-2-peter.chen@nxp.com Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> --- drivers/usb/chipidea/udc.c | 32 ++++++++++++++++++++++++-------- 1 file changed, 24 insertions(+), 8 deletions(-) diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c index 6a5ee8e6da10..67ad40b0a05b 100644 --- a/drivers/usb/chipidea/udc.c +++ b/drivers/usb/chipidea/udc.c @@ -709,12 +709,6 @@ static int _gadget_stop_activity(struct usb_gadget *gadget) struct ci_hdrc *ci = container_of(gadget, struct ci_hdrc, gadget); unsigned long flags; - spin_lock_irqsave(&ci->lock, flags); - ci->gadget.speed = USB_SPEED_UNKNOWN; - ci->remote_wakeup = 0; - ci->suspended = 0; - spin_unlock_irqrestore(&ci->lock, flags); - /* flush all endpoints */ gadget_for_each_ep(ep, gadget) { usb_ep_fifo_flush(ep); @@ -732,6 +726,12 @@ static int _gadget_stop_activity(struct usb_gadget *gadget) ci->status = NULL; } + spin_lock_irqsave(&ci->lock, flags); + ci->gadget.speed = USB_SPEED_UNKNOWN; + ci->remote_wakeup = 0; + ci->suspended = 0; + spin_unlock_irqrestore(&ci->lock, flags); + return 0; } @@ -1303,6 +1303,10 @@ static int ep_disable(struct usb_ep *ep) return -EBUSY; spin_lock_irqsave(hwep->lock, flags); + if (hwep->ci->gadget.speed == USB_SPEED_UNKNOWN) { + spin_unlock_irqrestore(hwep->lock, flags); + return 0; + } /* only internal SW should disable ctrl endpts */ @@ -1392,6 +1396,10 @@ static int ep_queue(struct usb_ep *ep, struct usb_request *req, return -EINVAL; spin_lock_irqsave(hwep->lock, flags); + if (hwep->ci->gadget.speed == USB_SPEED_UNKNOWN) { + spin_unlock_irqrestore(hwep->lock, flags); + return 0; + } retval = _ep_queue(ep, req, gfp_flags); spin_unlock_irqrestore(hwep->lock, flags); return retval; @@ -1415,8 +1423,8 @@ static int ep_dequeue(struct usb_ep *ep, struct usb_request *req) return -EINVAL; spin_lock_irqsave(hwep->lock, flags); - - hw_ep_flush(hwep->ci, hwep->num, hwep->dir); + if (hwep->ci->gadget.speed != USB_SPEED_UNKNOWN) + hw_ep_flush(hwep->ci, hwep->num, hwep->dir); list_for_each_entry_safe(node, tmpnode, &hwreq->tds, td) { dma_pool_free(hwep->td_pool, node->ptr, node->dma); @@ -1487,6 +1495,10 @@ static void ep_fifo_flush(struct usb_ep *ep) } spin_lock_irqsave(hwep->lock, flags); + if (hwep->ci->gadget.speed == USB_SPEED_UNKNOWN) { + spin_unlock_irqrestore(hwep->lock, flags); + return; + } hw_ep_flush(hwep->ci, hwep->num, hwep->dir); @@ -1559,6 +1571,10 @@ static int ci_udc_wakeup(struct usb_gadget *_gadget) int ret = 0; spin_lock_irqsave(&ci->lock, flags); + if (ci->gadget.speed == USB_SPEED_UNKNOWN) { + spin_unlock_irqrestore(&ci->lock, flags); + return 0; + } if (!ci->remote_wakeup) { ret = -EOPNOTSUPP; goto out; -- 2.23.0

5 years, 4 months

1
0
0 0

patch "usbtmc: more sanity checking for packet size" added to usb-linus

by gregkh＠linuxfoundation.org

This is a note to let you know that I've just added the patch titled usbtmc: more sanity checking for packet size to my usb git tree which can be found at git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git in the usb-linus branch. The patch will show up in the next release of the linux-next tree (usually sometime within the next 24 hours during the week.) The patch will hopefully also be merged in Linus's tree for the next -rc kernel release. If you have any questions about this process, please let me know. >From de7b9aa633b693e77942e12f1769506efae6917b Mon Sep 17 00:00:00 2001 From: Oliver Neukum <oneukum(a)suse.com> Date: Tue, 20 Aug 2019 11:28:25 +0200 Subject: usbtmc: more sanity checking for packet size A malicious device can make the driver divide ny zero with a nonsense maximum packet size. Signed-off-by: Oliver Neukum <oneukum(a)suse.com> Cc: stable <stable(a)vger.kernel.org> Link: https://lore.kernel.org/r/20190820092826.17694-1-oneukum@suse.com Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> --- drivers/usb/class/usbtmc.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/usb/class/usbtmc.c b/drivers/usb/class/usbtmc.c index 4942122b2346..36858ddd8d9b 100644 --- a/drivers/usb/class/usbtmc.c +++ b/drivers/usb/class/usbtmc.c @@ -2362,8 +2362,11 @@ static int usbtmc_probe(struct usb_interface *intf, goto err_put; } + retcode = -EINVAL; data->bulk_in = bulk_in->bEndpointAddress; data->wMaxPacketSize = usb_endpoint_maxp(bulk_in); + if (!data->wMaxPacketSize) + goto err_put; dev_dbg(&intf->dev, "Found bulk in endpoint at %u\n", data->bulk_in); data->bulk_out = bulk_out->bEndpointAddress; -- 2.23.0

5 years, 4 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror August 2019