November 2019 - Linux-stable-mirror

stable-rc/linux-4.19.y boot: 116 boots: 0 failed, 109 passed with 7 offline (v4.19.81-145-g3d8e1366ea55)

by kernelci.org bot

stable-rc/linux-4.19.y boot: 116 boots: 0 failed, 109 passed with 7 offline (v4.19.81-145-g3d8e1366ea55) 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.81-14… Tree: stable-rc Branch: linux-4.19.y Git Describe: v4.19.81-145-g3d8e1366ea55 Git Commit: 3d8e1366ea55e7033be040ed601d05b78d24d549 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 69 unique boards, 23 SoC families, 14 builds out of 206 Offline Platforms: arm: sunxi_defconfig: gcc-8 sun5i-r8-chip: 1 offline lab sun7i-a20-bananapi: 1 offline lab multi_v7_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab sun5i-r8-chip: 1 offline lab sun7i-a20-bananapi: 1 offline lab davinci_all_defconfig: gcc-8 dm365evm,legacy: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab --- For more info write to <info(a)kernelci.org>

5 years, 2 months

1
0
0 0

Re: PROBLEM: PCIe Bus Error atleast

by Jeffrin Thalakkottoor

On Mon, Nov 4, 2019 at 5:08 AM Oliver O'Halloran <oohall(a)gmail.com> wrote: > Use "uname -a" to get the current kernel version, architecture. Linux debian 5.3.8 #3 SMP Thu Oct 31 03:02:06 IST 2019 x86_64 GNU/Linux > is a laptop it might be due to buggy power management, yes this is an "asus vivobook" > Can you provide the full dmesg and the output of lspci -vv? typical dmesg and lspci -vv is attached now a typical clip from both .... --------------x---------------------x----------------------------------- $cat full-dmesg-related.txt | grep 8086 [ 0.051002] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.469327] pci 0000:00:00.0: [8086:5904] type 00 class 0x060000 [ 0.469694] pci 0000:00:02.0: [8086:5921] type 00 class 0x030000 [ 0.469873] pci 0000:00:04.0: [8086:1903] type 00 class 0x118000 [ 0.470111] pci 0000:00:14.0: [8086:9d2f] type 00 class 0x0c0330 [ 0.470435] pci 0000:00:14.2: [8086:9d31] type 00 class 0x118000 [ 0.470727] pci 0000:00:15.0: [8086:9d60] type 00 class 0x118000 [ 0.472058] pci 0000:00:15.1: [8086:9d61] type 00 class 0x118000 [ 0.473308] pci 0000:00:16.0: [8086:9d3a] type 00 class 0x078000 [ 0.473614] pci 0000:00:17.0: [8086:282a] type 00 class 0x010400 [ 0.473878] pci 0000:00:1c.0: [8086:9d10] type 01 class 0x060400 [ 0.474226] pci 0000:00:1c.5: [8086:9d15] type 01 class 0x060400 [ 0.474598] pci 0000:00:1e.0: [8086:9d27] type 00 class 0x118000 [ 0.475930] pci 0000:00:1e.2: [8086:9d29] type 00 class 0x118000 [ 0.477172] pci 0000:00:1e.6: [8086:9d2d] type 00 class 0x080501 [ 0.477401] pci 0000:00:1f.0: [8086:9d4e] type 00 class 0x060100 [ 0.477651] pci 0000:00:1f.2: [8086:9d21] type 00 class 0x058000 [ 0.477843] pci 0000:00:1f.3: [8086:9d71] type 00 class 0x040300 [ 0.478206] pci 0000:00:1f.4: [8086:9d23] type 00 class 0x0c0500 [ 2.072098] sdhci-pci 0000:00:1e.6: SDHCI controller found [8086:9d2d] (rev 21) -------------------------------x---------------------x---------------------- $lspci -vv | grep "00:1c.5" 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) (prog-if 00 [Normal decode]) $ -----------------x---------------------x------------------------------------- -- software engineer rajagiri school of engineering and technology

5 years, 2 months

1
1
0 0

Re: usb-storage: Set virt_boundary_mask to avoid SG overflows

by Daniel Walker

Hi, This is a stable defect report. We're tracking v4.9 stable for some of our products (i.e. Cisco Systems, Inc.) We noticed a speed degradation of roughly %30 on writes to a /dev/sdaX device over USB (no file system). We bisected the issue to this commit from Alan Stern. We also found a prior report of speed degradation on NTFS, https://lore.kernel.org/linux-usb/Pine.LNX.4.44L0.1908291030400.1306-100000… We have the patch reverted in our v4.9 tree on top of stable. It seems Alan was planning to remove these lines. If the lines are planned to be removed is there an reason why they haven't been ? Thanks, Daniel

5 years, 2 months

2
2
0 0

stable-rc/linux-4.4.y boot: 80 boots: 0 failed, 72 passed with 7 offline, 1 conflict (v4.4.198-47-g3849b8fee3c3)

by kernelci.org bot

stable-rc/linux-4.4.y boot: 80 boots: 0 failed, 72 passed with 7 offline, 1 conflict (v4.4.198-47-g3849b8fee3c3) 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.198-47-… Tree: stable-rc Branch: linux-4.4.y Git Describe: v4.4.198-47-g3849b8fee3c3 Git Commit: 3849b8fee3c31ec2cfef806e0e369ccbd50d0f1e Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 41 unique boards, 17 SoC families, 13 builds out of 190 Offline Platforms: arm: sunxi_defconfig: gcc-8 sun5i-r8-chip: 1 offline lab sun7i-a20-bananapi: 1 offline lab multi_v7_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab sun5i-r8-chip: 1 offline lab sun7i-a20-bananapi: 1 offline lab davinci_all_defconfig: gcc-8 dm365evm,legacy: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 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_x86_64: lab-collabora: PASS (gcc-8) lab-baylibre: FAIL (gcc-8) --- For more info write to <info(a)kernelci.org>

5 years, 2 months

1
0
0 0

stable-rc/linux-4.14.y boot: 11 boots: 0 failed, 8 passed with 3 offline (v4.14.151-95-g3f14236a3fe8)

by kernelci.org bot

stable-rc/linux-4.14.y boot: 11 boots: 0 failed, 8 passed with 3 offline (v4.14.151-95-g3f14236a3fe8) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.1… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.151-9… Tree: stable-rc Branch: linux-4.14.y Git Describe: v4.14.151-95-g3f14236a3fe8 Git Commit: 3f14236a3fe8cfb5c238b250eee737f9c78c402d Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 10 unique boards, 2 SoC families, 2 builds out of 201 Offline Platforms: arm: sunxi_defconfig: gcc-8 sun5i-r8-chip: 1 offline lab sun7i-a20-bananapi: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab --- For more info write to <info(a)kernelci.org>

5 years, 2 months

1
0
0 0

✅ PASS: Stable queue: queue-5.3

by CKI Project

Hello, We ran automated tests on a patchset that was proposed for merging into this kernel tree. The patches were applied to: Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Commit: 95180e47e77a - Linux 5.3.8 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/263536 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 `-' ______________________________________________________________________________ Merge testing ------------- We cloned this repository and checked out the following commit: Repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Commit: 95180e47e77a - Linux 5.3.8 We grabbed the 4cf9952ed574 commit of the stable queue repository. We then merged the patchset with `git am`: io_uring-fix-up-o_nonblock-handling-for-sockets.patch dm-snapshot-introduce-account_start_copy-and-account.patch dm-snapshot-rework-cow-throttling-to-fix-deadlock.patch btrfs-fix-inode-cache-block-reserve-leak-on-failure-.patch btrfs-qgroup-always-free-prealloc-meta-reserve-in-bt.patch iio-adc-meson_saradc-fix-memory-allocation-order.patch iio-fix-center-temperature-of-bmc150-accel-core.patch libsubcmd-make-_fortify_source-defines-dependent-on-.patch perf-tests-avoid-raising-segv-using-an-obvious-null-.patch perf-map-fix-overlapped-map-handling.patch perf-script-brstackinsn-fix-recovery-from-lbr-binary.patch perf-jevents-fix-period-for-intel-fixed-counters.patch perf-tools-propagate-get_cpuid-error.patch perf-annotate-propagate-perf_env__arch-error.patch perf-annotate-fix-the-signedness-of-failure-returns.patch perf-annotate-propagate-the-symbol__annotate-error-r.patch perf-annotate-fix-arch-specific-init-failure-errors.patch perf-annotate-return-appropriate-error-code-for-allo.patch perf-annotate-don-t-return-1-for-error-when-doing-bp.patch staging-rtl8188eu-fix-null-dereference-when-kzalloc-.patch rdma-siw-fix-serialization-issue-in-write_space.patch rdma-hfi1-prevent-memory-leak-in-sdma_init.patch rdma-iw_cxgb4-fix-srq-access-from-dump_qp.patch rdma-iwcm-fix-a-lock-inversion-issue.patch hid-hyperv-use-in-place-iterator-api-in-the-channel-.patch kselftest-exclude-failed-targets-from-runlist.patch selftests-kselftest-runner.sh-add-45-second-timeout-.patch nfs-fix-nfsi-nrequests-count-error-on-nfs_inode_remo.patch arm64-cpufeature-effectively-expose-frint-capability.patch arm64-fix-incorrect-irqflag-restore-for-priority-mas.patch arm64-ftrace-ensure-synchronisation-in-plt-setup-for.patch tty-serial-owl-fix-the-link-time-qualifier-of-owl_ua.patch tty-serial-rda-fix-the-link-time-qualifier-of-rda_ua.patch serial-sifive-select-serial_earlycon.patch tty-n_hdlc-fix-build-on-sparc.patch misc-fastrpc-prevent-memory-leak-in-fastrpc_dma_buf_.patch rdma-core-fix-an-error-handling-path-in-res_get_comm.patch rdma-cm-fix-memory-leak-in-cm_add-remove_one.patch rdma-nldev-reshuffle-the-code-to-avoid-need-to-rebin.patch rdma-mlx5-do-not-allow-rereg-of-a-odp-mr.patch rdma-mlx5-order-num_pending_prefetch-properly-with-s.patch rdma-mlx5-add-missing-synchronize_srcu-for-mw-cases.patch gpio-max77620-use-correct-unit-for-debounce-times.patch fs-cifs-mute-wunused-const-variable-message.patch arm64-vdso32-fix-broken-compat-vdso-build-warnings.patch arm64-vdso32-detect-binutils-support-for-dmb-ishld.patch serial-mctrl_gpio-check-for-null-pointer.patch serial-8250_omap-fix-gpio-check-for-auto-rts-cts.patch arm64-default-to-building-compat-vdso-with-clang-whe.patch arm64-vdso32-don-t-use-kbuild_cppflags-unconditional.patch efi-cper-fix-endianness-of-pcie-class-code.patch efi-x86-do-not-clean-dummy-variable-in-kexec-path.patch mips-include-mark-__cmpxchg-as-__always_inline.patch riscv-avoid-kernel-hangs-when-trapped-in-bug.patch riscv-avoid-sending-a-sigtrap-to-a-user-thread-trapp.patch riscv-correct-the-handling-of-unexpected-ebreak-in-d.patch x86-xen-return-from-panic-notifier.patch ocfs2-clear-zero-in-unaligned-direct-io.patch fs-ocfs2-fix-possible-null-pointer-dereferences-in-o.patch fs-ocfs2-fix-a-possible-null-pointer-dereference-in-.patch fs-ocfs2-fix-a-possible-null-pointer-dereference-in-.patch btrfs-silence-maybe-uninitialized-warning-in-clone_r.patch arm64-armv8_deprecated-checking-return-value-for-mem.patch x86-cpu-add-comet-lake-to-the-intel-cpu-models-heade.patch sched-fair-scale-bandwidth-quota-and-period-without-.patch sched-vtime-fix-guest-system-mis-accounting-on-task-.patch perf-core-rework-memory-accounting-in-perf_mmap.patch perf-core-fix-corner-case-in-perf_rotate_context.patch perf-x86-amd-change-fix-nmi-latency-mitigation-to-us.patch drm-amdgpu-fix-memory-leak.patch iio-imu-adis16400-release-allocated-memory-on-failur.patch iio-imu-adis16400-fix-memory-leak.patch iio-imu-st_lsm6dsx-fix-waitime-for-st_lsm6dsx-i2c-co.patch mips-include-mark-__xchg-as-__always_inline.patch mips-fw-sni-fix-out-of-bounds-init-of-o32-stack.patch s390-cio-fix-virtio-ccw-dma-without-pv.patch virt-vbox-fix-memory-leak-in-hgcm_call_preprocess_li.patch nbd-fix-possible-sysfs-duplicate-warning.patch nfsv4-fix-leak-of-clp-cl_acceptor-string.patch sunrpc-fix-race-to-sk_err-after-xs_error_report.patch s390-uaccess-avoid-false-positive-compiler-warnings.patch tracing-initialize-iter-seq-after-zeroing-in-tracing.patch perf-annotate-fix-multiple-memory-and-file-descripto.patch perf-aux-fix-tracking-of-auxiliary-trace-buffer-allo.patch usb-legousbtower-fix-a-signedness-bug-in-tower_probe.patch nbd-verify-socket-is-supported-during-setup.patch arm64-dts-qcom-add-lenovo-miix-630.patch arm64-dts-qcom-add-hp-envy-x2.patch arm64-dts-qcom-add-asus-novago-tp370ql.patch rtw88-fix-misuse-of-genmask-macro.patch s390-pci-fix-msi-message-data.patch thunderbolt-correct-path-indices-for-pcie-tunnel.patch thunderbolt-use-32-bit-writes-when-writing-ring-prod.patch ath6kl-fix-a-null-ptr-deref-bug-in-ath6kl_usb_alloc_.patch fuse-flush-dirty-data-metadata-before-non-truncate-setattr.patch fuse-truncate-pending-writes-on-o_trunc.patch alsa-bebob-fix-prototype-of-helper-function-to-return-negative-value.patch alsa-timer-fix-mutex-deadlock-at-releasing-card.patch alsa-hda-realtek-fix-2-front-mics-of-codec-0x623.patch alsa-hda-realtek-add-support-for-alc623.patch ath10k-fix-latency-issue-for-qca988x.patch uas-revert-commit-3ae62a42090f-uas-fix-alignment-of-scatter-gather-segments.patch nl80211-fix-validation-of-mesh-path-nexthop.patch usb-gadget-reject-endpoints-with-0-maxpacket-value.patch usb-storage-revert-commit-747668dbc061-usb-storage-set-virt_boundary_mask-to-avoid-sg-overflows.patch usb-ldusb-fix-ring-buffer-locking.patch usb-ldusb-fix-control-message-timeout.patch usb-xhci-fix-immediate-data-transfer-endianness.patch usb-xhci-fix-__le32-__le64-accessors-in-debugfs-code.patch usb-serial-whiteheat-fix-potential-slab-corruption.patch usb-serial-whiteheat-fix-line-speed-endianness.patch xhci-fix-use-after-free-regression-in-xhci-clear-hub-tt-implementation.patch scsi-qla2xxx-fix-partial-flash-write-of-mbi.patch scsi-target-cxgbit-fix-cxgbit_fw4_ack.patch hid-i2c-hid-add-trekstor-primebook-c11b-to-descriptor-override.patch hid-fix-assumption-that-devices-have-inputs.patch hid-fix-error-message-in-hid_open_report.patch 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 ✅ Podman system integration test (as root) ✅ Podman system integration test (as user) ✅ LTP lite ✅ Loopdev Sanity ✅ jvm test suite ✅ AMTU (Abstract Machine Test Utility) ✅ LTP: openposix test suite ✅ Ethernet drivers sanity ✅ Networking socket: fuzz ✅ audit: audit testsuite test ✅ httpd: mod_ssl smoke sanity ✅ iotop: sanity ✅ tuned: tune-processes-through-perf ✅ ALSA PCM loopback test ✅ ALSA Control (mixer) Userspace Element test ✅ Usex - version 1.9-29 ✅ storage: SCSI VPD ✅ trace: ftrace/tracer 🚧 ✅ CIFS Connectathon 🚧 ✅ POSIX pjd-fstest suites 🚧 ✅ storage: dm/common Host 2: ✅ Boot test ✅ xfstests: xfs ✅ selinux-policy: serge-testsuite ✅ storage: software RAID testing 🚧 ✅ Storage blktests ppc64le: Host 1: ✅ Boot test ✅ Podman system integration test (as root) ✅ Podman system integration test (as user) ✅ LTP lite ✅ Loopdev Sanity ✅ jvm test suite ✅ AMTU (Abstract Machine Test Utility) ✅ LTP: openposix test suite ✅ Ethernet drivers sanity ✅ Networking socket: fuzz ✅ audit: audit testsuite test ✅ httpd: mod_ssl smoke sanity ✅ iotop: sanity ✅ tuned: tune-processes-through-perf ✅ ALSA PCM loopback test ✅ ALSA Control (mixer) Userspace Element test ✅ Usex - version 1.9-29 ✅ trace: ftrace/tracer 🚧 ✅ CIFS Connectathon 🚧 ✅ POSIX pjd-fstest suites 🚧 ✅ storage: dm/common Host 2: ✅ Boot test ✅ xfstests: xfs ✅ selinux-policy: serge-testsuite ✅ storage: software RAID testing 🚧 ✅ Storage blktests x86_64: Host 1: ✅ Boot test ✅ xfstests: xfs ✅ selinux-policy: serge-testsuite ✅ storage: software RAID testing 🚧 ✅ Storage blktests Host 2: ✅ Boot test ✅ Podman system integration test (as root) ✅ Podman system integration test (as user) ✅ LTP lite ✅ Loopdev Sanity ✅ jvm test suite ✅ AMTU (Abstract Machine Test Utility) ✅ LTP: openposix test suite ✅ Ethernet drivers sanity ✅ Networking socket: fuzz ✅ audit: audit testsuite test ✅ httpd: mod_ssl smoke sanity ✅ iotop: sanity ✅ tuned: tune-processes-through-perf ✅ pciutils: sanity smoke test ✅ ALSA PCM loopback test ✅ ALSA Control (mixer) Userspace Element test ✅ Usex - version 1.9-29 ✅ storage: SCSI VPD ✅ stress: stress-ng ✅ trace: ftrace/tracer 🚧 ✅ CIFS Connectathon 🚧 ✅ POSIX pjd-fstest suites 🚧 ✅ storage: dm/common Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test 🚧 ⚡⚡⚡ /kernel/infiniband/env_setup 🚧 ⚡⚡⚡ /kernel/infiniband/sanity Host 4: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test 🚧 ⚡⚡⚡ /kernel/infiniband/env_setup 🚧 ⚡⚡⚡ /kernel/infiniband/sanity Host 5: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test 🚧 ⚡⚡⚡ /kernel/infiniband/env_setup 🚧 ⚡⚡⚡ /kernel/infiniband/sanity Host 6: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test 🚧 ⚡⚡⚡ /kernel/infiniband/env_setup 🚧 ⚡⚡⚡ /kernel/infiniband/sanity Test sources: https://github.com/CKI-project/tests-beaker 💚 Pull requests are welcome for new tests or improvements to existing tests! 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. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running are marked with ⏱. Reports for non-upstream kernels have a Beaker recipe linked to next to each host.

5 years, 2 months

1
0
0 0

stable-rc/linux-4.19.y boot: 10 boots: 0 failed, 6 passed with 3 offline, 1 untried/unknown (v4.19.81-145-g7d816e1d91b0)

by kernelci.org bot

stable-rc/linux-4.19.y boot: 10 boots: 0 failed, 6 passed with 3 offline, 1 untried/unknown (v4.19.81-145-g7d816e1d91b0) 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.81-14… Tree: stable-rc Branch: linux-4.19.y Git Describe: v4.19.81-145-g7d816e1d91b0 Git Commit: 7d816e1d91b01911392b7f8f93a4a153b9af60d3 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 10 unique boards, 2 SoC families, 2 builds out of 206 Boot Regressions Detected: arm: sunxi_defconfig: gcc-8: sun8i-h2-plus-orangepi-r1: lab-baylibre: new failure (last pass: v4.19.81-114-g7db85d223311) Offline Platforms: arm: sunxi_defconfig: gcc-8 sun5i-r8-chip: 1 offline lab sun7i-a20-bananapi: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab --- For more info write to <info(a)kernelci.org>

5 years, 2 months

1
0
0 0

FAILED: patch "[PATCH] dmaengine: qcom: bam_dma: Fix resource leak" failed to apply to 4.14-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 4.14-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. thanks, greg k-h ------------------ original commit in Linus's tree ------------------ >From 7667819385457b4aeb5fac94f67f52ab52cc10d5 Mon Sep 17 00:00:00 2001 From: Jeffrey Hugo <jeffrey.l.hugo(a)gmail.com> Date: Thu, 17 Oct 2019 08:26:06 -0700 Subject: [PATCH] dmaengine: qcom: bam_dma: Fix resource leak bam_dma_terminate_all() will leak resources if any of the transactions are committed to the hardware (present in the desc fifo), and not complete. Since bam_dma_terminate_all() does not cause the hardware to be updated, the hardware will still operate on any previously committed transactions. This can cause memory corruption if the memory for the transaction has been reassigned, and will cause a sync issue between the BAM and its client(s). Fix this by properly updating the hardware in bam_dma_terminate_all(). Fixes: e7c0fe2a5c84 ("dmaengine: add Qualcomm BAM dma driver") Signed-off-by: Jeffrey Hugo <jeffrey.l.hugo(a)gmail.com> Cc: stable(a)vger.kernel.org Link: https://lore.kernel.org/r/20191017152606.34120-1-jeffrey.l.hugo@gmail.com Signed-off-by: Vinod Koul <vkoul(a)kernel.org> diff --git a/drivers/dma/qcom/bam_dma.c b/drivers/dma/qcom/bam_dma.c index 8e90a405939d..ef73f65224b1 100644 --- a/drivers/dma/qcom/bam_dma.c +++ b/drivers/dma/qcom/bam_dma.c @@ -694,6 +694,25 @@ static int bam_dma_terminate_all(struct dma_chan *chan) /* remove all transactions, including active transaction */ spin_lock_irqsave(&bchan->vc.lock, flag); + /* + * If we have transactions queued, then some might be committed to the + * hardware in the desc fifo. The only way to reset the desc fifo is + * to do a hardware reset (either by pipe or the entire block). + * bam_chan_init_hw() will trigger a pipe reset, and also reinit the + * pipe. If the pipe is left disabled (default state after pipe reset) + * and is accessed by a connected hardware engine, a fatal error in + * the BAM will occur. There is a small window where this could happen + * with bam_chan_init_hw(), but it is assumed that the caller has + * stopped activity on any attached hardware engine. Make sure to do + * this first so that the BAM hardware doesn't cause memory corruption + * by accessing freed resources. + */ + if (!list_empty(&bchan->desc_list)) { + async_desc = list_first_entry(&bchan->desc_list, + struct bam_async_desc, desc_node); + bam_chan_init_hw(bchan, async_desc->dir); + } + list_for_each_entry_safe(async_desc, tmp, &bchan->desc_list, desc_node) { list_add(&async_desc->vd.node, &bchan->vc.desc_issued);

5 years, 2 months

3
4
0 0

stable-rc/linux-4.9.y boot: 93 boots: 0 failed, 86 passed with 7 offline (v4.9.198-59-g4e59c9878a95)

by kernelci.org bot

stable-rc/linux-4.9.y boot: 93 boots: 0 failed, 86 passed with 7 offline (v4.9.198-59-g4e59c9878a95) 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.198-59-… Tree: stable-rc Branch: linux-4.9.y Git Describe: v4.9.198-59-g4e59c9878a95 Git Commit: 4e59c9878a95af67c72f21d9bad59ec22c67d935 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 49 unique boards, 20 SoC families, 14 builds out of 197 Offline Platforms: arm: sunxi_defconfig: gcc-8 sun5i-r8-chip: 1 offline lab sun7i-a20-bananapi: 1 offline lab multi_v7_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab sun5i-r8-chip: 1 offline lab sun7i-a20-bananapi: 1 offline lab davinci_all_defconfig: gcc-8 dm365evm,legacy: 1 offline lab qcom_defconfig: gcc-8 qcom-apq8064-cm-qs600: 1 offline lab --- For more info write to <info(a)kernelci.org>

5 years, 2 months

1
0
0 0

patch "serial: 8250-mtk: Use platform_get_irq_optional() for optional irq" added to tty-testing

by gregkh＠linuxfoundation.org

This is a note to let you know that I've just added the patch titled serial: 8250-mtk: Use platform_get_irq_optional() for optional irq to my tty git tree which can be found at git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git in the tty-testing 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 be merged to the tty-next branch sometime soon, after it passes testing, and the merge window is open. If you have any questions about this process, please let me know. >From eb9c1a41ea1234907615fe47d6e47db8352d744b Mon Sep 17 00:00:00 2001 From: Frank Wunderlich <frank-w(a)public-files.de> Date: Sun, 27 Oct 2019 07:21:17 +0100 Subject: serial: 8250-mtk: Use platform_get_irq_optional() for optional irq As platform_get_irq() now prints an error when the interrupt does not exist, this warnings are printed on bananapi-r2: [ 4.935780] mt6577-uart 11004000.serial: IRQ index 1 not found [ 4.962589] 11002000.serial: ttyS1 at MMIO 0x11002000 (irq = 202, base_baud = 1625000) is a ST16650V2 [ 4.972127] mt6577-uart 11002000.serial: IRQ index 1 not found [ 4.998927] 11003000.serial: ttyS2 at MMIO 0x11003000 (irq = 203, base_baud = 1625000) is a ST16650V2 [ 5.008474] mt6577-uart 11003000.serial: IRQ index 1 not found Fix this by calling platform_get_irq_optional() instead. now it looks like this: [ 4.872751] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled Fixes: 7723f4c5ecdb8d83 ("driver core: platform: Add an error message to platform_get_irq*()") Signed-off-by: Frank Wunderlich <frank-w(a)public-files.de> Cc: stable <stable(a)vger.kernel.org> Link: https://lore.kernel.org/r/20191027062117.20389-1-frank-w@public-files.de Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> --- drivers/tty/serial/8250/8250_mtk.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/serial/8250/8250_mtk.c b/drivers/tty/serial/8250/8250_mtk.c index b411ba4eb5e9..4d067f515f74 100644 --- a/drivers/tty/serial/8250/8250_mtk.c +++ b/drivers/tty/serial/8250/8250_mtk.c @@ -544,7 +544,7 @@ static int mtk8250_probe(struct platform_device *pdev) pm_runtime_set_active(&pdev->dev); pm_runtime_enable(&pdev->dev); - data->rx_wakeup_irq = platform_get_irq(pdev, 1); + data->rx_wakeup_irq = platform_get_irq_optional(pdev, 1); return 0; } -- 2.23.0

5 years, 2 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror November 2019