Re: [PATCH 4.4 00/85] 4.4.238-rc1 review
On Tue, Sep 29, 2020 at 12:59:27PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.238 release. > There are 85 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Tested-by: Linux Kernel Functional Testing Summary kernel: 4.4.238-rc1 git repo: ['https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git', 'https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc'] git branch: linux-4.4.y git commit: 0d240bae7702c50af56209b177e48d81d371b555 git describe: v4.4.237-86-g0d240bae7702 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.4.y/build/v4.4.237-86-g0d240bae7702 No regressions (compared to build v4.4.237) No fixes (compared to build v4.4.237) Ran 5245 total tests in the following environments and test suites. Environments -- - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 - x86-kasan Test Suites --- * build * linux-log-parser * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-controllers-tests * ltp-cpuhotplug-tests * ltp-crypto-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-tracing-tests * v4l2-compliance * ltp-syscalls-tests * install-android-platform-tools-r2600 * network-basic-tests * perf Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Tested-by: Linux Kernel Functional Testing Summary kernel: 4.4.238-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.238-rc1-hikey-20200929-822 git commit: 1e94ff9d5cbda806b493b89b01eb99c67ec9ed4c git describe: 4.4.238-rc1-hikey-20200929-822 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.238-rc1-hikey-20200929-822 No regressions (compared to build 4.4.238-rc1-hikey-20200928-820) No fixes (compared to build 4.4.238-rc1-hikey-20200928-820) Ran 1686 total tests in the following environments and test suites. Environments -- - hi6220-hikey - arm64 Test Suites --- * build * install-android-platform-tools-r2600 * libhugetlbfs * linux-log-parser * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * perf * spectre-meltdown-checker-test * v4l2-compliance -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.9 000/121] 4.9.238-rc1 review
On Tue, Sep 29, 2020 at 12:59:04PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.238 release. > There are 121 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Tested-by: Linux Kernel Functional Testing Summary kernel: 4.9.238-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: 054f04eb3d5d58da303f70d141cf2ff1fddcbd71 git describe: v4.9.237-122-g054f04eb3d5d Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.9.y/build/v4.9.237-122-g054f04eb3d5d No regressions (compared to build v4.9.237) No fixes (compared to build v4.9.237) Ran 21423 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 - x86-kasan Test Suites --- * build * install-android-platform-tools-r2600 * linux-log-parser * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-controllers-tests * ltp-cpuhotplug-tests * ltp-crypto-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * perf * v4l2-compliance * network-basic-tests * libhugetlbfs * ltp-open-posix-tests * ltp-syscalls-tests * ltp-tracing-tests * ssuite -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 000/166] 4.14.200-rc1 review
On Tue, Sep 29, 2020 at 12:58:32PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.200 release. > There are 166 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Tested-by: Linux Kernel Functional Testing Summary kernel: 4.14.200-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: 7b80cb61f2b2cf4f291246ded2d1c29e3797c095 git describe: v4.14.199-167-g7b80cb61f2b2 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.14.y/build/v4.14.199-167-g7b80cb61f2b2 No regressions (compared to build v4.14.199) No fixes (compared to build v4.14.199) Ran 29427 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - juno-r2-compat - juno-r2-kasan - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 - x86-kasan Test Suites --- * build * install-android-platform-tools-r2600 * linux-log-parser * ltp-containers-tests * ltp-cve-tests * ltp-hugetlb-tests * ltp-math-tests * ltp-mm-tests * ltp-sched-tests * ltp-tracing-tests * v4l2-compliance * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-cpuhotplug-tests * ltp-crypto-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-syscalls-tests * network-basic-tests * perf * ltp-controllers-tests * ltp-dio-tests * ltp-io-tests * ltp-ipc-tests * ltp-nptl-tests * ltp-open-posix-tests * ltp-pty-tests * ltp-securebits-tests * ssuite -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.4 000/130] 5.4.66-rc2 review
On Tue, Sep 15, 2020 at 08:31:17PM -0400, Sasha Levin wrote:
> On Tue, Sep 15, 2020 at 03:17:32PM -0500, Dan Rue wrote:
> > On Tue, Sep 15, 2020 at 06:45:55PM +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.4.66 release.
> > > There are 130 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Thu, 17 Sep 2020 16:44:19 +.
> > > Anything received after that time might be too late.
> > >
> > > The whole patch series can be found in one patch at:
> > >
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.66-rc2.gz
> > > or in the git tree and branch at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > linux-5.4.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> > >
> > > -
> > > Pseudo-Shortlog of commits:
> > >
> > > Greg Kroah-Hartman
> > > Linux 5.4.66-rc2
> > >
> > > Jordan Crouse
> > > drm/msm: Disable the RPTR shadow
> > >
> > > Jonathan Marek
> > > drm/msm/a6xx: update a6xx_hw_init for A640 and A650
> >
> > This one ("drm/msm/a6xx: update a6xx_hw_init for A640 and A650") is
> > still causing builds to fail on arm and arm64.
>
> I've dropped it, thanks!
Could you push it?
Dan
--
Linaro LKFT
https://lkft.linaro.org
Re: [PATCH 5.4 000/130] 5.4.66-rc2 review
On Tue, Sep 15, 2020 at 06:45:55PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.66 release.
> There are 130 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu, 17 Sep 2020 16:44:19 +.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
>
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.66-rc2.gz
> or in the git tree and branch at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> linux-5.4.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
> -
> Pseudo-Shortlog of commits:
>
> Greg Kroah-Hartman
> Linux 5.4.66-rc2
>
> Jordan Crouse
> drm/msm: Disable the RPTR shadow
>
> Jonathan Marek
> drm/msm/a6xx: update a6xx_hw_init for A640 and A650
This one ("drm/msm/a6xx: update a6xx_hw_init for A640 and A650") is
still causing builds to fail on arm and arm64.
#
# make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j16 ARCH=arm64
CROSS_COMPILE=aarch64-linux-gnu- HOSTCC=gcc CC="sccache aarch64-linux-gnu-gcc"
O=build modules
#
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c: In function ‘a6xx_hw_init’:
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:414:6: error: implicit declaration of
function ‘adreno_is_a640’; did you mean ‘adreno_is_a540’?
[-Werror=implicit-function-declaration]
414 | if (adreno_is_a640(adreno_gpu) || adreno_is_a650(adreno_gpu)) {
| ^~
| adreno_is_a540
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:414:36: error: implicit declaration of
function ‘adreno_is_a650’; did you mean ‘adreno_is_a540’?
[-Werror=implicit-function-declaration]
414 | if (adreno_is_a640(adreno_gpu) || adreno_is_a650(adreno_gpu)) {
|^~
|adreno_is_a540
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:415:18: error:
‘REG_A6XX_GBIF_QSB_SIDE0’ undeclared (first use in this function)
415 | gpu_write(gpu, REG_A6XX_GBIF_QSB_SIDE0, 0x00071620);
| ^~~
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:415:18: note: each undeclared
identifier is reported only once for each function it appears in
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:416:18: error:
‘REG_A6XX_GBIF_QSB_SIDE1’ undeclared (first use in this function)
416 | gpu_write(gpu, REG_A6XX_GBIF_QSB_SIDE1, 0x00071620);
| ^~~
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:417:18: error:
‘REG_A6XX_GBIF_QSB_SIDE2’ undeclared (first use in this function)
417 | gpu_write(gpu, REG_A6XX_GBIF_QSB_SIDE2, 0x00071620);
| ^~~
../drivers/gpu/drm/msm/adreno/a6xx_gpu.c:418:18: error:
‘REG_A6XX_GBIF_QSB_SIDE3’ undeclared (first use in this function)
418 | gpu_write(gpu, REG_A6XX_GBIF_QSB_SIDE3, 0x00071620);
| ^~~
cc1: some warnings being treated as errors
make[5]: *** [../scripts/Makefile.build:266:
drivers/gpu/drm/msm/adreno/a6xx_gpu.o] Error 1
make[5]: Target '__build' not remade because of errors.
make[4]: *** [../scripts/Makefile.build:500: drivers/gpu/drm/msm] Error 2
make[4]: Target '__build' not remade because of errors.
make[3]: *** [../scripts/Makefile.build:500: drivers/gpu/drm] Error 2
make[3]: Target '__build' not remade because of errors.
make[2]: *** [../scripts/Makefile.build:500: drivers/gpu] Error 2
make[2]: Target '__build' not remade because of errors.
make[1]: *** [/linux/Makefile:1729: drivers] Error 2
make[1]: Target 'modules' not remade because of errors.
make: *** [Makefile:179: sub-make] Error 2
make: Target 'modules' not remade because of errors.
Dan
>
> Rob Clark
> drm/msm/gpu: make ringbuffer readonly
>
> Heikki Krogerus
> usb: typec: ucsi: acpi: Check the _DEP dependencies
>
> Mathias Nyman
> usb: Fix out of sync data toggle if a configured device is reconfigured
>
> Aleksander Morgado
> USB: serial: option: add support for SIM7070/SIM7080/SIM7090 modules
>
> Bjørn Mork
> USB: serial: option: support dynamic Quectel USB compositions
>
> Patrick Riphagen
> USB: serial: ftdi_sio: add IDs for Xsens Mti USB converter
>
> Zeng Tao
> usb: core: fix slab-out-of-bounds Read in read_descriptors
>
> Sivaprakash Murugesan
> phy: qcom-qmp: Use correct values for ipq8074 PCIe Gen2 PHY init
>
> Vaibhav Agarwal
> staging: greybus: audio: fix uninitialized value issue
>
> Tetsuo Handa
> video: fbdev: fix OOB read in vga_8planes_imageblit()
>
> Chris Healy
> ARM: dts: vfxxx: Add syscon compatible with OCOTP
>
> Vladis Dronov
> debugfs: Fix module state check condition
>
> Rustam Kovhaev
> KVM: fix memory leak in kvm_io_bus_unregister_dev()
>
> Marc Zyngier
> KVM:
Re: [PATCH 5.8 00/17] 5.8.7-rc1 review
On Fri, Sep 04, 2020 at 03:29:59PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.8.7 release. > There are 17 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Tested-by: Linux Kernel Functional Testing Summary kernel: 5.8.7-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.8.y git commit: 072d7559faf2a3b9f3c93e5cc96b276c6f02adec git describe: v5.8.5-272-g072d7559faf2 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.8-oe/build/v5.8.5-272-g072d7559faf2 No regressions (compared to build v5.8.5) No fixes (compared to build v5.8.5) Ran 35624 total tests in the following environments and test suites. Environments -- - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - juno-r2-compat - juno-r2-kasan - nxp-ls2088 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - x86 - x86-kasan Test Suites --- * igt-gpu-tools * libhugetlbfs * linux-log-parser * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-controllers-tests * ltp-cpuhotplug-tests * ltp-crypto-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-tracing-tests * ltp-cve-tests * ltp-sched-tests * v4l2-compliance * ltp-open-posix-tests * network-basic-tests -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.4 00/16] 5.4.63-rc1 review
On Fri, Sep 04, 2020 at 03:29:53PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.4.63 release. > There are 16 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. Sorry for the delay - we are short handed this weekend and I got confused looking at results yesterday and thought we had a systems problem. In fact, the problem was that tags/releases weren't pushed to stable-rc which split-brains our results and I just forgot about that possibility. Is it possible on your side to automate updating the stable-rc repo when you publish a stable release? Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Tested-by: Linux Kernel Functional Testing Summary kernel: 5.4.63-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.4.y git commit: ef2051e79e05700a5c8814fe4d5b7a8a93503251 git describe: v5.4.61-231-gef2051e79e05 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.4-oe/build/v5.4.61-231-gef2051e79e05 No regressions (compared to build v5.4.61) No fixes (compared to build v5.4.61) Ran 34712 total tests in the following environments and test suites. Environments -- - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - juno-r2-compat - juno-r2-kasan - nxp-ls2088 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - x86 - x86-kasan Test Suites --- * libhugetlbfs * linux-log-parser * ltp-commands-tests * ltp-containers-tests * ltp-controllers-tests * ltp-cve-tests * ltp-dio-tests * ltp-fs-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-securebits-tests * ltp-syscalls-tests * v4l2-compliance * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-sched-tests * ltp-cap_bounds-tests * ltp-cpuhotplug-tests * ltp-crypto-tests * ltp-ipc-tests * ltp-mm-tests * ltp-open-posix-tests * ltp-tracing-tests * network-basic-tests * igt-gpu-tools -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 000/185] 4.14.147-stable review
On Thu, Oct 03, 2019 at 05:51:18PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.147 release. > There are 185 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. > Anything received after that time might be too late. There's a regression listed below that happened while running 'modprobe vivid' on db410c. We've investigated it and are unable to reliably reproduce it. It happens less than 1% of the time, so it is very unlikely to be a regression. The detailed log can be found at https://lkft.validation.linaro.org/scheduler/job/950199#L1545 and we will continue to investigate and try to narrow down the problem so that we can report it coherently. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.14.147-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: b99061374089a66c2dd55bbea3299a602a4f0891 git describe: v4.14.146-186-gb99061374089 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.146-186-gb99061374089 Regressions (compared to build v4.14.146-18-gf0e4f7af6713) dragonboard-410c - arm64: v4l2-compliance: * modprobe-vivid No fixes (compared to build v4.14.146-18-gf0e4f7af6713) Ran 22696 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * ltp-fs-tests * ltp-syscalls-tests * network-basic-tests * ltp-open-posix-tests * kvm-unit-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * ssuite -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.3 000/344] 5.3.4-stable review
On Thu, Oct 03, 2019 at 05:49:25PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.3.4 release. > There are 344 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 5.3.4-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.3.y git commit: c9adc631ac5f1d6ac4ead2332f2a82c4e199852d git describe: v5.3.2-346-gc9adc631ac5f Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.3-oe/build/v5.3.2-346-gc9adc631ac5f No regressions (compared to build v5.3.1-26-g5910f7ae1729) No fixes (compared to build v5.3.1-26-g5910f7ae1729) Ran 25592 total tests in the following environments and test suites. Environments -- - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - x86 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libgpiod * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * network-basic-tests * ltp-open-posix-tests * kvm-unit-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * ssuite -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.2 000/313] 5.2.19-stable review
On Thu, Oct 03, 2019 at 05:49:38PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.2.19 release. > There are 313 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 5.2.19-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.2.y git commit: 2c8369f13ff8c1375690964c79ffdc0e41ab4f97 git describe: v5.2.18-314-g2c8369f13ff8 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.2-oe/build/v5.2.18-314-g2c8369f13ff8 No regressions (compared to build v5.2.18) No fixes (compared to build v5.2.18) Ran 24453 total tests in the following environments and test suites. Environments -- - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - x86 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libgpiod * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * ltp-dio-tests * ltp-io-tests * ltp-syscalls-tests * network-basic-tests * ltp-open-posix-tests * kvm-unit-tests * ssuite * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.19 000/211] 4.19.77-stable review
On Thu, Oct 03, 2019 at 05:51:06PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.19.77 release. > There are 211 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.19.77-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.19.y git commit: 319532606385c7221dfbfba6f857bd03e97e20d0 git describe: v4.19.76-212-g319532606385 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.76-212-g319532606385 No regressions (compared to build v4.19.76) No fixes (compared to build v4.19.76) Ran 22570 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * ltp-fs-tests * ltp-open-posix-tests * network-basic-tests * kvm-unit-tests * ssuite * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.9 000/129] 4.9.195-stable review
On Thu, Oct 03, 2019 at 05:52:03PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.195 release. > There are 129 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.9.195-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: c1fc114556201dc059e2c202e99eac038af8495e git describe: v4.9.194-130-gc1fc11455620 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.194-130-gc1fc11455620 No regressions (compared to build v4.9.194) No fixes (compared to build v4.9.194) Ran 23331 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * ltp-fs-tests * network-basic-tests * ltp-open-posix-tests * prep-tmp-disk * kvm-unit-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * ssuite -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.4 00/99] 4.4.195-stable review
On Thu, Oct 03, 2019 at 05:52:23PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.195 release. > There are 99 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.4.195-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: 9a8d8139a7e557ce81c19f467a2a873371e3deba git describe: v4.4.194-100-g9a8d8139a7e5 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.194-100-g9a8d8139a7e5 No regressions (compared to build v4.4.194) No fixes (compared to build v4.4.194) Ran 18728 total tests in the following environments and test suites. Environments -- - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * build * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-open-posix-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * network-basic-tests * perf * prep-tmp-disk * spectre-meltdown-checker-test * kvm-unit-tests * v4l2-compliance * install-android-platform-tools-r2600 * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * ssuite Summary kernel: 4.4.195-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.195-rc1-hikey-20191003-572 git commit: 3f7eeb94b05eb384e0c0cee76d6446f60aba646f git describe: 4.4.195-rc1-hikey-20191003-572 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.195-rc1-hikey-20191003-572 No regressions (compared to build 4.4.195-rc1-hikey-20191001-571) No fixes (compared to build 4.4.195-rc1-hikey-20191001-571) Ran 1523 total tests in the following environments and test suites. Environments -- - hi6220-hikey - arm64 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.3 00/25] 5.3.2-stable review
On Sun, Sep 29, 2019 at 03:56:03PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.3.2 release. > There are 25 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Tue 01 Oct 2019 01:47:47 PM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 5.3.2-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.3.y git commit: 5910f7ae17298c45fce24a2f314573bcb7a86284 git describe: v5.3.1-26-g5910f7ae1729 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.3-oe/build/v5.3.1-26-g5910f7ae1729 No regressions (compared to build v5.3.1) No fixes (compared to build v5.3.1) Ran 23295 total tests in the following environments and test suites. Environments -- - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - x86 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libgpiod * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * ltp-open-posix-tests * network-basic-tests * kvm-unit-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * ssuite -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.2 00/45] 5.2.18-stable review
On Sun, Sep 29, 2019 at 03:55:28PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.2.18 release. > There are 45 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Tue 01 Oct 2019 01:47:47 PM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 5.2.18-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.2.y git commit: 70cc0b99b90f823b81175b1f15f73ced86135c5b git describe: v5.2.17-46-g70cc0b99b90f Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.2-oe/build/v5.2.17-46-g70cc0b99b90f No regressions (compared to build v5.2.17) No fixes (compared to build v5.2.17) Ran 22166 total tests in the following environments and test suites. Environments -- - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - x86 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libgpiod * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-open-posix-tests * network-basic-tests * kvm-unit-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * ssuite -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.19 00/63] 4.19.76-stable review
On Sun, Sep 29, 2019 at 03:53:33PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.19.76 release. > There are 63 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Tue 01 Oct 2019 01:47:47 PM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.19.76-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.19.y git commit: b52c75f7b9785d0d0e6bf145787ed2fc99f5483c git describe: v4.19.75-64-gb52c75f7b978 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.75-64-gb52c75f7b978 No regressions (compared to build v4.19.75) No fixes (compared to build v4.19.75) Ran 23641 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * ltp-fs-tests * network-basic-tests * ltp-open-posix-tests * kvm-unit-tests * ssuite * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.2 000/162] 5.2.11-stable review
On Wed, Aug 28, 2019 at 05:52:52PM +0200, Greg Kroah-Hartman wrote: > On Wed, Aug 28, 2019 at 10:47:18AM -0500, Dan Rue wrote: > > On Wed, Aug 28, 2019 at 05:16:08PM +0200, Greg Kroah-Hartman wrote: > > > On Wed, Aug 28, 2019 at 10:30:09AM +0530, Naresh Kamboju wrote: > > > > On Tue, 27 Aug 2019 at 13:30, Greg Kroah-Hartman > > > > wrote: > > > > > > > > > > This is the start of the stable review cycle for the 5.2.11 release. > > > > > There are 162 patches in this series, all will be posted as a response > > > > > to this one. If anyone has any issues with these being applied, > > > > > please > > > > > let me know. > > > > > > > > > > Responses should be made by Thu 29 Aug 2019 07:25:02 AM UTC. > > > > > Anything received after that time might be too late. > > > > > > > > > > The whole patch series can be found in one patch at: > > > > > > > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.2.11-rc1.gz > > > > > or in the git tree and branch at: > > > > > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > > > > linux-5.2.y > > > > > and the diffstat can be found below. > > > > > > > > > > thanks, > > > > > > > > > > greg k-h > > > > > > > > Results from Linaro’s test farm. > > > > No regressions on arm64, arm, x86_64, and i386. > > > > > > Thanks for testing all of these and letting us know. > > > > > > Also, how did you all not catch the things that the redhat ci system was > > > catching that caused us to add another networking aptch? > > > > Hi Greg - > > > > I'll follow up with them off list. That said, I expect different CI > > setups to find different issues - that's the point, after all. It would > > be bad if we all ran the exact same things, and found the exact same > > things, because then we'd also miss the exact same things. In the macro > > sense, there is a lot to test, and I would rather see CI teams go after > > areas that are weak, rather than areas that are well covered. > > I totally agree, but here we actually have a known failure (for once!) > so it would be nice to see why the very large test suite that you all > run missed this. OK, so it seems the following two tests failed for them[0]: > ❌ Networking socket: fuzz [9] > ❌ Networking sctp-auth: sockopts test [10] fuzz[1] seems to be a redhat test that was added to tests-beaker on May 20th this year. Similarly, sockopts[2] was added on May 7th. We don't run tests-beaker. Maybe we should? Major is coming to Linaro Connect in a few weeks to talk about CKI[3]. Topics such as test coverage and test suites are on our agenda to discuss. Hope that helps, Dan [0] https://lore.kernel.org/stable/291770ce-273a-68aa-a4a2-7655cbea2...@mhtx.net [1] https://github.com/CKI-project/tests-beaker/commit/a454fdeaada71f7f193ae00e505621bf4a8ed8c6 [2] https://github.com/CKI-project/tests-beaker/commit/4ebc85dae5042cc2b70c98a868f3b3501eec1e08 [3] https://linaroconnectsandiego.sched.com/event/Suco/san19-416-transforming-kernel-developer-workflows-with-cicd > > thanks, > > greg k-h -- Linaro - Kernel Validation
Re: [PATCH 5.2 000/162] 5.2.11-stable review
On Wed, Aug 28, 2019 at 05:16:08PM +0200, Greg Kroah-Hartman wrote: > On Wed, Aug 28, 2019 at 10:30:09AM +0530, Naresh Kamboju wrote: > > On Tue, 27 Aug 2019 at 13:30, Greg Kroah-Hartman > > wrote: > > > > > > This is the start of the stable review cycle for the 5.2.11 release. > > > There are 162 patches in this series, all will be posted as a response > > > to this one. If anyone has any issues with these being applied, please > > > let me know. > > > > > > Responses should be made by Thu 29 Aug 2019 07:25:02 AM UTC. > > > Anything received after that time might be too late. > > > > > > The whole patch series can be found in one patch at: > > > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.2.11-rc1.gz > > > or in the git tree and branch at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > > linux-5.2.y > > > and the diffstat can be found below. > > > > > > thanks, > > > > > > greg k-h > > > > Results from Linaro’s test farm. > > No regressions on arm64, arm, x86_64, and i386. > > Thanks for testing all of these and letting us know. > > Also, how did you all not catch the things that the redhat ci system was > catching that caused us to add another networking aptch? Hi Greg - I'll follow up with them off list. That said, I expect different CI setups to find different issues - that's the point, after all. It would be bad if we all ran the exact same things, and found the exact same things, because then we'd also miss the exact same things. In the macro sense, there is a lot to test, and I would rather see CI teams go after areas that are weak, rather than areas that are well covered. Dan > > thanks, > > greg k-h -- Linaro - Kernel Validation
Re: [PATCH 4.4 00/21] 4.4.189-stable review
On Fri, Aug 09, 2019 at 03:45:04PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.189 release. > There are 21 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sun 11 Aug 2019 01:42:28 PM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Note that test counts are a bit lower than previous because we are having some infrastructure/lab issue with our qemu/x86 environments. There is no evidence that it's kernel related. Summary kernel: 4.4.189-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: ab9a14a0618d99ad7e0b7e589a97f3421ac4d662 git describe: v4.4.187-45-gab9a14a0618d Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.187-45-gab9a14a0618d No regressions (compared to build v4.4.187) No fixes (compared to build v4.4.187) Ran 16774 total tests in the following environments and test suites. Environments -- - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * build * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-open-posix-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * network-basic-tests * perf * prep-tmp-disk * spectre-meltdown-checker-test * kvm-unit-tests * v4l2-compliance * install-android-platform-tools-r2600 * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * ssuite Summary kernel: 4.4.189-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.189-rc1-hikey-20190809-523 git commit: ffbfd13890f25f989c107e0a79063ff644d02753 git describe: 4.4.189-rc1-hikey-20190809-523 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.189-rc1-hikey-20190809-523 No regressions (compared to build 4.4.189-rc1-hikey-20190809-522) No fixes (compared to build 4.4.189-rc1-hikey-20190809-522) Ran 1550 total tests in the following environments and test suites. Environments -- - hi6220-hikey - arm64 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.2 000/413] 5.2.3-stable review
On Thu, Jul 25, 2019 at 07:06:19PM +0200, Paolo Bonzini wrote: > On 25/07/19 18:39, Dan Rue wrote: > > To your point Paolo - reporting 'fail' because of a missing kernel > > feature is a generic problem we see across test suites, and causes tons > > of pain and misery for CI people. As a general rule, I'd avoid > > submodules, and even branches that track specific kernels. Rather, and I > > don't know if it's possible in this case, but the best way to manage it > > from both a test author and a test runner POV is to wrap the test in > > kernel feature checks, kernel version checks, kernel config checks, etc. > > Report 'skip' if the environment in which the test is running isn't > > sufficient to run the test. Then, you only have to maintain one version > > of the test suite, users can always use the latest, and critically: all > > failures are actual failures. > > Note that kvm-unit-tests are not really testing new kernel features; > those are covered by tools/testing/selftests/kvm. For some of these > kvm-unit-tests there are some CPU features that we can check from the > virtual machine, but those are easy to handle and they produce SKIP > results just fine. > > The problematic ones are tests that cover emulation accuracy. These are > effectively bugfixes, so the failures you see _are_ actual failures. At > the same time, the bugs are usually inoffensive(*), while the fixes are > invasive and a bad source of cause conflicts in older Linux versions. > This combines so that backporting to stable is not feasible. In this case, a fail result seems correct then. The thing we're doing that we need to fix is to run against a pinned version of kvm-unit-tests and upgrade it independently so that we can identify such failures and mark them as known issues. > > Passing the host kernel version would be really ugly because 1) the > tests can run on other hypervisor or emulators or even bare metal, and > of course the host kernel version has no bearing if you're using > userspace emulation 2) there are thousands of tests that would be > littered with kernel version checks of little significance. > > So this is why I suggested a submodule: using a submodule effectively > ignores all tests that were added after a given Linus release, and thus > all the failures for which backports are just not going to happen. > However, if Sean's idea of creating a linux-M.N branch in > kvm-unit-tests.git works for you, we can also do that as a stopgap > measure to ease your testing. I would still prefer to run the latest tests against all kernel versions (but better control when we upgrade it). Like I said, we can handle expected failures, and it would even help to validate backports for fixes that do get backported. I'm afraid on your behalf that snapping (and maintaining) branches per kernel branch is going to be a lot to manage. In any case, _thank you so much_ for jumping on this and helping us run these tests. Is there anything else we can do to make this better for you? Dan > > Thanks, > > Paolo > > (*) if they aren't, we *do* mark them for backport! -- Linaro - Kernel Validation
Re: [PATCH 5.2 000/413] 5.2.3-stable review
On Thu, Jul 25, 2019 at 06:30:10PM +0200, Paolo Bonzini wrote: > On 25/07/19 18:20, Sean Christopherson wrote: > > On Thu, Jul 25, 2019 at 06:10:37PM +0200, Paolo Bonzini wrote: > >> On 25/07/19 18:09, Sean Christopherson wrote: > This investigation confirms it is a new test code failure on stable-rc > 5.2.3 > >>> No, it only confirms that kvm-unit-tests/master fails on 5.2.*. To > >>> confirm > >>> a new failure in 5.2.3 you would need to show a test that passes on 5.2.2 > >>> and fails on 5.2.3. > >> > >> I think he meant "a failure in new test code". :) > > > > Ah, that does appear to be the case. So just to be clear, we're good, > > right? > > Yes. I'm happy to gather ideas on how to avoid this (i.e. 1) if a > submodule would be useful; 2) where to stick it). Hi! First, to be clear: from LKFT perspective there are no kernel regressions here. To your point Paolo - reporting 'fail' because of a missing kernel feature is a generic problem we see across test suites, and causes tons of pain and misery for CI people. As a general rule, I'd avoid submodules, and even branches that track specific kernels. Rather, and I don't know if it's possible in this case, but the best way to manage it from both a test author and a test runner POV is to wrap the test in kernel feature checks, kernel version checks, kernel config checks, etc. Report 'skip' if the environment in which the test is running isn't sufficient to run the test. Then, you only have to maintain one version of the test suite, users can always use the latest, and critically: all failures are actual failures. Dan > > Paolo -- Linaro - Kernel Validation
Re: selftests: bpf: test_libbpf.sh failed at file test_l4lb.o
On Mon, Jun 24, 2019 at 12:58:15PM -0700, Alexei Starovoitov wrote: > On Mon, Jun 24, 2019 at 12:53 PM Dan Rue wrote: > > > > I would say if it's not possible to check at runtime, and it requires > > clang 9.0, that this test should not be enabled by default. > > The latest clang is the requirement. > If environment has old clang or no clang at all these tests will be failing. Hi Alexei! I'm not certain if I'm interpreting you as you intended, but it sounds like you're telling me that if the test build environment does not use 'latest clang' (i guess latest as of today?), that these tests will fail, and that is how it is going to be. If I have that wrong, please correct me and disregard the rest of my message. Please understand where we are coming from. We (and many others) run thousands of tests from a lot of test frameworks, and so our environment often has mutually exclusive requirements when it comes to things like toolchain selection. We believe, strongly, that a test should not emit a "fail" for a missing requirement. Fail is a serious thing, and should be reserved for an actual issue that needs to be investigated, reported, and fixed. This is how we treat test failures - we investigate, report, and fix them when possible. When they're not real failures, we waste our time (and yours, in this case). By adding the tests to TEST_GEN_PROGS, you're adding them to the general test set that those of us running test farms try to run continuously across a wide range of hardware environments and kernel branches. My suggestion is that if you do not want us running them, don't add them to TEST_GEN_PROGS. I thought the suggestion of testing for adequate clang support and adding them conditionally at build-time was an idea worth consideration. Thanks, Dan -- Linaro - Kernel Validation
Re: selftests: bpf: test_libbpf.sh failed at file test_l4lb.o
On Mon, Jun 24, 2019 at 11:32:25AM -0700, Andrii Nakryiko wrote: > On Fri, Jun 21, 2019 at 9:17 AM Dan Rue wrote: > > > > On Thu, Jun 20, 2019 at 10:17:04PM -0700, Andrii Nakryiko wrote: > > > On Thu, Jun 20, 2019 at 1:08 AM Naresh Kamboju > > > wrote: > > > > > > > > selftests: bpf test_libbpf.sh failed running Linux -next kernel > > > > 20190618 and 20190619. > > > > > > > > Here is the log from x86_64, > > > > # selftests bpf test_libbpf.sh > > > > bpf: test_libbpf.sh_ # > > > > # [0] libbpf BTF is required, but is missing or corrupted. > > > > > > You need at least clang-9.0.0 (not yet released) to run some of these > > > tests successfully, as they rely on Clang's support for > > > BTF_KIND_VAR/BTF_KIND_DATASEC. > > > > Can there be a runtime check for BTF that emits a skip instead of a fail > > in such a case? > > I'm not sure how to do this simply and minimally intrusively. The best > I can come up with is setting some envvar from Makefile and checking > for that in each inidividual test, which honestly sounds a bit gross. > > How hard is it for you guys to upgrade compiler used to run these test? We should be able to run kselftest with any compiler that Linux supports, so that we can test with the toolchain that users actually run with. I would say if it's not possible to check at runtime, and it requires clang 9.0, that this test should not be enabled by default. Maybe something could be done in Makefile for that? Only add it to TEST_GEN_PROGS if the toolchain feature exists, otherwise add it to TEST_GEN_PROGS_EXTENDED. I don't know if this is a good idea.. but from kselftest.rst: TEST_PROGS, TEST_GEN_PROGS mean it is the executable tested by default. ... TEST_PROGS_EXTENDED, TEST_GEN_PROGS_EXTENDED mean it is the executable which is not tested by default. Dan > > > > > Thanks, > > Dan > > > > > > > > > libbpf: BTF_is # > > > > # test_libbpf failed at file test_l4lb.o > > > > failed: at_file # > > > > # selftests test_libbpf [FAILED] > > > > test_libbpf: [FAILED]_ # > > > > [FAIL] 29 selftests bpf test_libbpf.sh > > > > selftests: bpf_test_libbpf.sh [FAIL] > > > > > > > > Full test log, > > > > https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190619/testrun/781777/log > > > > > > > > Test results comparison, > > > > https://qa-reports.linaro.org/lkft/linux-next-oe/tests/kselftest/bpf_test_libbpf.sh > > > > > > > > Good linux -next tag: next-20190617 > > > > Bad linux -next tag: next-20190618 > > > > git branch master > > > > git commit1c6b40509daf5190b1fd2c758649f7df1da4827b > > > > git repo > > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > > > > > > > > Best regards > > > > Naresh Kamboju > > > > -- > > Linaro - Kernel Validation -- Linaro - Kernel Validation
Re: selftests: bpf: test_libbpf.sh failed at file test_l4lb.o
On Thu, Jun 20, 2019 at 10:17:04PM -0700, Andrii Nakryiko wrote: > On Thu, Jun 20, 2019 at 1:08 AM Naresh Kamboju > wrote: > > > > selftests: bpf test_libbpf.sh failed running Linux -next kernel > > 20190618 and 20190619. > > > > Here is the log from x86_64, > > # selftests bpf test_libbpf.sh > > bpf: test_libbpf.sh_ # > > # [0] libbpf BTF is required, but is missing or corrupted. > > You need at least clang-9.0.0 (not yet released) to run some of these > tests successfully, as they rely on Clang's support for > BTF_KIND_VAR/BTF_KIND_DATASEC. Can there be a runtime check for BTF that emits a skip instead of a fail in such a case? Thanks, Dan > > > libbpf: BTF_is # > > # test_libbpf failed at file test_l4lb.o > > failed: at_file # > > # selftests test_libbpf [FAILED] > > test_libbpf: [FAILED]_ # > > [FAIL] 29 selftests bpf test_libbpf.sh > > selftests: bpf_test_libbpf.sh [FAIL] > > > > Full test log, > > https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190619/testrun/781777/log > > > > Test results comparison, > > https://qa-reports.linaro.org/lkft/linux-next-oe/tests/kselftest/bpf_test_libbpf.sh > > > > Good linux -next tag: next-20190617 > > Bad linux -next tag: next-20190618 > > git branch master > > git commit1c6b40509daf5190b1fd2c758649f7df1da4827b > > git repo > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > > > > Best regards > > Naresh Kamboju -- Linaro - Kernel Validation
Re: [PATCH 5.0 000/346] 5.0.20-stable review
On Fri, May 31, 2019 at 06:20:43AM -0700, Greg Kroah-Hartman wrote: > On Thu, May 30, 2019 at 09:53:33PM +0530, Naresh Kamboju wrote: > > On Thu, 30 May 2019 at 08:48, Greg Kroah-Hartman > > wrote: > > > > > > This is the start of the stable review cycle for the 5.0.20 release. > > > There are 346 patches in this series, all will be posted as a response > > > to this one. If anyone has any issues with these being applied, please > > > let me know. > > > > > > Responses should be made by Sat 01 Jun 2019 03:02:10 AM UTC. > > > Anything received after that time might be too late. > > > > > > The whole patch series can be found in one patch at: > > > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.0.20-rc1.gz > > > or in the git tree and branch at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > > linux-5.0.y > > > and the diffstat can be found below. > > > > > > thanks, > > > > > > greg k-h > > > > Results from Linaro’s test farm. > > No regressions on arm64, arm, x86_64, and i386. > > Thanks for testing 4 of these and letting me know. 5.1 sent out now. We were just waiting for the remaining test jobs to finish before sending it. Dan > > greg k-h -- Linaro - Kernel Validation
Re: [PATCH 5.1 000/405] 5.1.6-stable review
On Wed, May 29, 2019 at 07:59:58PM -0700, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.1.6 release. > There are 405 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat 01 Jun 2019 03:01:59 AM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 5.1.6-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.1.y git commit: 6df8e06907e10b03bfeb68d794def0a11133a8a3 git describe: v5.1.5-406-g6df8e06907e1 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.1-oe/build/v5.1.5-406-g6df8e06907e1 No regressions (compared to build v5.1.5) No fixes (compared to build v5.1.5) Ran 23969 total tests in the following environments and test suites. Environments -- - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - x86 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libgpiod * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * network-basic-tests * ltp-fs-tests * ltp-open-posix-tests * kvm-unit-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * ssuite -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH] kbuild: teach kselftest-merge to find nested config files
On Mon, May 20, 2019 at 07:56:41PM +0200, Greg KH wrote: > On Mon, May 20, 2019 at 10:16:14AM -0500, Dan Rue wrote: > > Current implementation of kselftest-merge only finds config files that > > are one level deep using `$(srctree)/tools/testing/selftests/*/config`. > > > > Often, config files are added in nested directories, and do not get > > picked up by kselftest-merge. > > > > Use `find` to catch all config files under > > `$(srctree)/tools/testing/selftests` instead. > > > > Signed-off-by: Dan Rue > > --- > > Makefile | 5 ++--- > > 1 file changed, 2 insertions(+), 3 deletions(-) > > To be more specific here, the binderfs test is not catching the config > entry, so it would be nice to get this into the stable trees as well :) > > > diff --git a/Makefile b/Makefile > > index a45f84a7e811..e99e7f9484af 100644 > > --- a/Makefile > > +++ b/Makefile > > @@ -1228,9 +1228,8 @@ kselftest-clean: > > PHONY += kselftest-merge > > kselftest-merge: > > $(if $(wildcard $(objtree)/.config),, $(error No .config exists, config > > your kernel first!)) > > - $(Q)$(CONFIG_SHELL) $(srctree)/scripts/kconfig/merge_config.sh \ > > - -m $(objtree)/.config \ > > - $(srctree)/tools/testing/selftests/*/config > > + $(Q)find $(srctree)/tools/testing/selftests -name config | \ > > + xargs $(srctree)/scripts/kconfig/merge_config.sh -m > > $(objtree)/.config > > +$(Q)$(MAKE) -f $(srctree)/Makefile olddefconfig > > > > # > > --- > > is find run with $(Q)? It isn't with other instances in the Makefile. I'm not entirely sure all the ways that $(Q) is used (it looks like it just gets set to @), but if i run 'KBUILD_VERBOSE=1 make kselftest-merge' I do see the find command printed before running: find ./tools/testing/selftests -name config | \ xargs ./scripts/kconfig/merge_config.sh -m ./.config I noticed find used inconsistently (sometimes with @, sometimes with $(Q), sometimes with neither), so I picked the usage that seemed most correct to me. Dan > > thanks, > > greg k-h -- Linaro - Kernel Validation
Re: ext4 regression (was Re: [PATCH 4.19 000/105] 4.19.45-stable review)
On Tue, May 21, 2019 at 11:38:49AM +0200, Greg Kroah-Hartman wrote:
> On Tue, May 21, 2019 at 02:58:58PM +0530, Naresh Kamboju wrote:
> > On Tue, 21 May 2019 at 14:30, Greg Kroah-Hartman
> > wrote:
> > >
> > > On Mon, May 20, 2019 at 05:23:42PM -0500, Dan Rue wrote:
> > > > On Mon, May 20, 2019 at 02:13:06PM +0200, Greg Kroah-Hartman wrote:
> > > > > This is the start of the stable review cycle for the 4.19.45 release.
> > > > > There are 105 patches in this series, all will be posted as a response
> > > > > to this one. If anyone has any issues with these being applied,
> > > > > please
> > > > > let me know.
> > > > >
> > > > > Responses should be made by Wed 22 May 2019 11:50:49 AM UTC.
> > > > > Anything received after that time might be too late.
> > > >
> > > > We're seeing an ext4 issue previously reported at
> > > > https://lore.kernel.org/lkml/20190514092054.GA6949@osiris.
> > > >
> > > > [ 1916.032087] EXT4-fs error (device sda): ext4_find_extent:909: inode
> > > > #8: comm jbd2/sda-8: pblk 121667583 bad header/extent: invalid extent
> > > > entries - magic f30a, entries 8, max 340(340), depth 0(0)
> > > > [ 1916.073840] jbd2_journal_bmap: journal block not found at offset
> > > > 4455 on sda-8
> > > > [ 1916.081071] Aborting journal on device sda-8.
> > > > [ 1916.348652] EXT4-fs error (device sda): ext4_journal_check_start:61:
> > > > Detected aborted journal
> > > > [ 1916.357222] EXT4-fs (sda): Remounting filesystem read-only
> > > >
> > > > This is seen on 4.19-rc, 5.0-rc, mainline, and next. We don't have data
> > > > for 5.1-rc yet, which is presumably also affected in this RC round.
> > > >
> > > > We only see this on x86_64 and i386 devices - though our hardware setups
> > > > vary so it could be coincidence.
> > > >
> > > > I have to run out now, but I'll come back and work on a reproducer and
> > > > bisection later tonight and tomorrow.
> > > >
> > > > Here is an example test run; link goes to the spot in the ltp syscalls
> > > > test where the disk goes into read-only mode.
> > > > https://lkft.validation.linaro.org/scheduler/job/735468#L8081
> > >
> > > Odd, I keep hearing rumors of ext4 issues right now, but nothing
> > > actually solid that I can point to. Any help you can provide here would
> > > be great.
> > >
> >
> > git bisect helped me to land on this commit,
> >
> > # git bisect bad
> > e8fd3c9a5415f9199e3fc5279e0f1dfcc0a80ab2 is the first bad commit
> > commit e8fd3c9a5415f9199e3fc5279e0f1dfcc0a80ab2
> > Author: Theodore Ts'o
> > Date: Tue Apr 9 23:37:08 2019 -0400
> >
> > ext4: protect journal inode's blocks using block_validity
> >
> > commit 345c0dbf3a30872d9b204db96b5857cd00808cae upstream.
> >
> > Add the blocks which belong to the journal inode to block_validity's
> > system zone so attempts to deallocate or overwrite the journal due a
> > corrupted file system where the journal blocks are also claimed by
> > another inode.
> >
> > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=202879
> > Signed-off-by: Theodore Ts'o
> > Cc: sta...@kernel.org
> > Signed-off-by: Greg Kroah-Hartman
> >
> > :04 04 b8b6ce2577d60c65021e5cc1c3a38b32e0cbb2ff
> > 747c67b159b33e4e1da414b1d33567a5da9ae125 M fs
>
> Ah, many thanks for this bisection.
>
> Ted, any ideas here? Should I drop this from the stable trees, and you
> revert it from Linus's? Or something else?
>
> Note, I do also have 170417c8c7bb ("ext4: fix block validity checks for
> journal inodes using indirect blocks") in the trees, which was supposed
> to fix the problem with this patch, am I missing another one as well?
>
> (side note, it was mean not to mark 170417c8c7bb for stable, when the
> patch it was fixing was marked for stable, I'm lucky I caught it...)
My independent bisection agrees that e8fd3c9a5415 ("ext4: protect
journal inode's blocks using block_validity") is the root cause. I was
able to revert it along with 18b3c1c2827c ("ext4: unsigned int compared
against zero") on 4.19 and then the issue went away.
I tested the same revert on mainline v5.2-rc1 and it fixed the issue
there as well (git revert fd2f28ae 345c0dbf3a30).
The problem reproduces in our environment 100% of the time, but creating
a reproducer is troublesome; it happens while running LTP syscalls, and
requires some combination of syscall tests to happen. So far, we've been
able to reduce it to the following ltp runfile:
https://gist.github.com/danrue/61c663e1dc50dc7c13a232f0a062bdc6
LTP is run using '/opt/ltp/runltp -d /scratch -f syscalls', where the
syscalls file has been replaced with the version in the gist, and
/scratch is an ext4 SATA drive. /scratch is created using 'mkfs -t ext4
/dev/disk/by-id/ata-TOSHIBA_MG03ACA100_37O9KGKWF' and mounted to
/scratch.
I'll update the gist as we reduce it further.
Dan
--
Linaro - Kernel Validation
Re: [PATCH 4.19 000/105] 4.19.45-stable review
On Mon, May 20, 2019 at 02:13:06PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.19.45 release. > There are 105 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed 22 May 2019 11:50:49 AM UTC. > Anything received after that time might be too late. We're seeing an ext4 issue previously reported at https://lore.kernel.org/lkml/20190514092054.GA6949@osiris. [ 1916.032087] EXT4-fs error (device sda): ext4_find_extent:909: inode #8: comm jbd2/sda-8: pblk 121667583 bad header/extent: invalid extent entries - magic f30a, entries 8, max 340(340), depth 0(0) [ 1916.073840] jbd2_journal_bmap: journal block not found at offset 4455 on sda-8 [ 1916.081071] Aborting journal on device sda-8. [ 1916.348652] EXT4-fs error (device sda): ext4_journal_check_start:61: Detected aborted journal [ 1916.357222] EXT4-fs (sda): Remounting filesystem read-only This is seen on 4.19-rc, 5.0-rc, mainline, and next. We don't have data for 5.1-rc yet, which is presumably also affected in this RC round. We only see this on x86_64 and i386 devices - though our hardware setups vary so it could be coincidence. I have to run out now, but I'll come back and work on a reproducer and bisection later tonight and tomorrow. Here is an example test run; link goes to the spot in the ltp syscalls test where the disk goes into read-only mode. https://lkft.validation.linaro.org/scheduler/job/735468#L8081 Dan -- Linaro - Kernel Validation
[PATCH] kbuild: teach kselftest-merge to find nested config files
Current implementation of kselftest-merge only finds config files that are one level deep using `$(srctree)/tools/testing/selftests/*/config`. Often, config files are added in nested directories, and do not get picked up by kselftest-merge. Use `find` to catch all config files under `$(srctree)/tools/testing/selftests` instead. Signed-off-by: Dan Rue --- Makefile | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Makefile b/Makefile index a45f84a7e811..e99e7f9484af 100644 --- a/Makefile +++ b/Makefile @@ -1228,9 +1228,8 @@ kselftest-clean: PHONY += kselftest-merge kselftest-merge: $(if $(wildcard $(objtree)/.config),, $(error No .config exists, config your kernel first!)) - $(Q)$(CONFIG_SHELL) $(srctree)/scripts/kconfig/merge_config.sh \ - -m $(objtree)/.config \ - $(srctree)/tools/testing/selftests/*/config + $(Q)find $(srctree)/tools/testing/selftests -name config | \ + xargs $(srctree)/scripts/kconfig/merge_config.sh -m $(objtree)/.config +$(Q)$(MAKE) -f $(srctree)/Makefile olddefconfig # --- -- 2.21.0
Re: [PATCH 5.1 00/30] 5.1.1-stable review
On Thu, May 09, 2019 at 08:42:32PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.1.1 release. > There are 30 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat 11 May 2019 06:11:35 PM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 5.1.1-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.1.y git commit: e4f05f7add176a1379bcd3e582b0ca615cf58000 git describe: v5.1-31-ge4f05f7add17 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.1-oe/build/v5.1-31-ge4f05f7add17 No regressions (compared to build v5.1) No fixes (compared to build v5.1) Ran 23855 total tests in the following environments and test suites. Environments -- - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - x86 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libgpiod * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * ltp-fs-tests * ltp-open-posix-tests * kvm-unit-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.19 00/23] 4.19.40-stable review
On Sun, May 05, 2019 at 11:02:36AM +0200, Greg Kroah-Hartman wrote: > On Sun, May 05, 2019 at 02:23:22PM +0530, Naresh Kamboju wrote: > > On Sun, 5 May 2019 at 12:38, Greg Kroah-Hartman > > wrote: > > > > > > On Sat, May 04, 2019 at 10:00:44PM -0500, Dan Rue wrote: > > > > On Sat, May 04, 2019 at 12:25:02PM +0200, Greg Kroah-Hartman wrote: > > > > > This is the start of the stable review cycle for the 4.19.40 release. > > > > > There are 23 patches in this series, all will be posted as a response > > > > > to this one. If anyone has any issues with these being applied, > > > > > please > > > > > let me know. > > > > > > > > > > Responses should be made by Mon 06 May 2019 10:24:19 AM UTC. > > > > > Anything received after that time might be too late. > > > > > > > > > > > > Results from Linaro’s test farm. > > > > Regressions detected. > > > > > > Really? Where? > > > > Not really. > > selftest: net: msg_zerocopy.sh is an intermittent failure on qemu_i386 > > device. > > Is that a test problem, or a qemu problem? > > > We could ignore this failure as known issues. > > It wasn't listed in the report, or did I miss it? It needs further investigation, but it's unrelated to this RC. It's an intermittent failure that we see sometimes but only ever on qemu. With the amount of tests that we run, this is common - our process is to investigate the failure and determine if the failure is a regression or not. In this case, I determined that it was not a real regression, but I did not run the right command to generate the report accordingly. No regressions on arm64, arm, x86_64, and i386. Dan
Re: [PATCH 5.0 00/32] 5.0.13-stable review
On Sat, May 04, 2019 at 08:31:36PM -0700, Guenter Roeck wrote: > On 5/4/19 8:05 PM, Dan Rue wrote: > > On Sat, May 04, 2019 at 12:24:45PM +0200, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 5.0.13 release. > > > There are 32 patches in this series, all will be posted as a response > > > to this one. If anyone has any issues with these being applied, please > > > let me know. > > > > > > Responses should be made by Mon 06 May 2019 10:24:23 AM UTC. > > > Anything received after that time might be too late. > > > > Results from Linaro’s test farm. > > Regressions detected. > > > > Confusing. What are the regressions ? Below it says that there are none. My mistake for dashing it off too quickly. No regressions on arm64, arm, x86_64, and i386. Dan > > Guenter > > > Summary > > > > > > kernel: 5.0.13-rc1 > > git repo: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > git branch: linux-5.0.y > > git commit: c6bd3efdcefd68cc590853c50594a9fc971d93cd > > git describe: v5.0.12-33-gc6bd3efdcefd > > Test details: > > https://qa-reports.linaro.org/lkft/linux-stable-rc-5.0-oe/build/v5.0.12-33-gc6bd3efdcefd > > > > No regressions (compared to build v5.0.11-102-g17f93022a8c9) > > > > No fixes (compared to build v5.0.11-102-g17f93022a8c9) > > > > Ran 25060 total tests in the following environments and test suites. > > > > Environments > > -- > > - dragonboard-410c > > - hi6220-hikey > > - i386 > > - juno-r2 > > - qemu_arm > > - qemu_arm64 > > - qemu_i386 > > - qemu_x86_64 > > - x15 > > - x86 > > > > Test Suites > > --- > > * build > > * install-android-platform-tools-r2600 > > * kselftest > > * libgpiod > > * libhugetlbfs > > * ltp-cap_bounds-tests > > * ltp-commands-tests > > * ltp-containers-tests > > * ltp-cpuhotplug-tests > > * ltp-cve-tests > > * ltp-dio-tests > > * ltp-fcntl-locktests-tests > > * ltp-filecaps-tests > > * ltp-fs_bind-tests > > * ltp-fs_perms_simple-tests > > * ltp-fsx-tests > > * ltp-hugetlb-tests > > * ltp-io-tests > > * ltp-ipc-tests > > * ltp-math-tests > > * ltp-mm-tests > > * ltp-nptl-tests > > * ltp-pty-tests > > * ltp-sched-tests > > * ltp-securebits-tests > > * ltp-syscalls-tests > > * ltp-timers-tests > > * perf > > * spectre-meltdown-checker-test > > * v4l2-compliance > > * kvm-unit-tests > > * ltp-fs-tests > > * ltp-open-posix-tests > > * kselftest-vsyscall-mode-native > > * kselftest-vsyscall-mode-none > > > -- Linaro - Kernel Validation
Re: [PATCH 5.0 00/32] 5.0.13-stable review
On Sat, May 04, 2019 at 12:24:45PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.0.13 release. > There are 32 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Mon 06 May 2019 10:24:23 AM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. Regressions detected. Summary kernel: 5.0.13-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.0.y git commit: c6bd3efdcefd68cc590853c50594a9fc971d93cd git describe: v5.0.12-33-gc6bd3efdcefd Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.0-oe/build/v5.0.12-33-gc6bd3efdcefd No regressions (compared to build v5.0.11-102-g17f93022a8c9) No fixes (compared to build v5.0.11-102-g17f93022a8c9) Ran 25060 total tests in the following environments and test suites. Environments -- - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - x86 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libgpiod * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * kvm-unit-tests * ltp-fs-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.19 00/23] 4.19.40-stable review
On Sat, May 04, 2019 at 12:25:02PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.19.40 release. > There are 23 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Mon 06 May 2019 10:24:19 AM UTC. > Anything received after that time might be too late. Results from Linaro’s test farm. Regressions detected. Summary kernel: 4.19.40-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.19.y git commit: b0d6421bd85515e878edcf33121a818666df7749 git describe: v4.19.39-24-gb0d6421bd855 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.39-24-gb0d6421bd855 No regressions (compared to build v4.19.38-73-gdb2d00a74567) No fixes (compared to build v4.19.38-73-gdb2d00a74567) Ran 25058 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * build * install-android-platform-tools-r2600 * kselftest * libgpiod * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * perf * spectre-meltdown-checker-test * v4l2-compliance * kvm-unit-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.0 39/93] perf top: Delete the evlist before perf_session, fixing heap-use-after-free issue
On Thu, Apr 18, 2019 at 07:57:17PM +0200, Greg Kroah-Hartman wrote: > [ Upstream commit 0dba9e4be95b59e77060645ca8e37ca3231061f5 ] > > The evlist should be destroyed before the perf session. > > Detected with gcc's ASan: > > = > ==27350==ERROR: AddressSanitizer: heap-use-after-free on address > 0x62b02e38 at pc 0x5611da276999 bp 0x7ffce8f1d1a0 sp 0x7ffce8f1d190 > WRITE of size 8 at 0x62b02e38 thread T0 > #0 0x5611da276998 in __list_del > /home/work/linux/tools/include/linux/list.h:89 > #1 0x5611da276d4a in __list_del_entry > /home/work/linux/tools/include/linux/list.h:102 > #2 0x5611da276e77 in list_del_init > /home/work/linux/tools/include/linux/list.h:145 > #3 0x5611da2781cd in thread__put util/thread.c:130 > #4 0x5611da2cc0a8 in __thread__zput util/thread.h:68 > #5 0x5611da2d2dcb in hist_entry__delete util/hist.c:1148 > #6 0x5611da2cdf91 in hists__delete_entry util/hist.c:337 > #7 0x5611da2ce19e in hists__delete_entries util/hist.c:365 > #8 0x5611da2db2ab in hists__delete_all_entries util/hist.c:2639 > #9 0x5611da2db325 in hists_evsel__exit util/hist.c:2651 > #10 0x5611da1c5352 in perf_evsel__exit util/evsel.c:1304 > #11 0x5611da1c5390 in perf_evsel__delete util/evsel.c:1309 > #12 0x5611da1b35f0 in perf_evlist__purge util/evlist.c:124 > #13 0x5611da1b38e2 in perf_evlist__delete util/evlist.c:148 > #14 0x5611da069781 in cmd_top > /home/changbin/work/linux/tools/perf/builtin-top.c:1645 > #15 0x5611da17d038 in run_builtin > /home/changbin/work/linux/tools/perf/perf.c:302 > #16 0x5611da17d577 in handle_internal_command > /home/changbin/work/linux/tools/perf/perf.c:354 > #17 0x5611da17d97b in run_argv > /home/changbin/work/linux/tools/perf/perf.c:398 > #18 0x5611da17e0e9 in main > /home/changbin/work/linux/tools/perf/perf.c:520 > #19 0x7fdcc970f09a in __libc_start_main > (/lib/x86_64-linux-gnu/libc.so.6+0x2409a) > #20 0x5611d9ff35c9 in _start (/home/work/linux/tools/perf/perf+0x3e95c9) > > 0x62b02e38 is located 11320 bytes inside of 27448-byte region > [0x62b00200,0x62b06d38) > freed by thread T0 here: > #0 0x7fdccb04ab70 in free > (/usr/lib/x86_64-linux-gnu/libasan.so.5+0xedb70) > #1 0x5611da260df4 in perf_session__delete util/session.c:201 > #2 0x5611da063de5 in __cmd_top > /home/changbin/work/linux/tools/perf/builtin-top.c:1300 > #3 0x5611da06973c in cmd_top > /home/changbin/work/linux/tools/perf/builtin-top.c:1642 > #4 0x5611da17d038 in run_builtin > /home/changbin/work/linux/tools/perf/perf.c:302 > #5 0x5611da17d577 in handle_internal_command > /home/changbin/work/linux/tools/perf/perf.c:354 > #6 0x5611da17d97b in run_argv > /home/changbin/work/linux/tools/perf/perf.c:398 > #7 0x5611da17e0e9 in main > /home/changbin/work/linux/tools/perf/perf.c:520 > #8 0x7fdcc970f09a in __libc_start_main > (/lib/x86_64-linux-gnu/libc.so.6+0x2409a) > > previously allocated by thread T0 here: > #0 0x7fdccb04b138 in calloc > (/usr/lib/x86_64-linux-gnu/libasan.so.5+0xee138) > #1 0x5611da26010c in zalloc util/util.h:23 > #2 0x5611da260824 in perf_session__new util/session.c:118 > #3 0x5611da0633a6 in __cmd_top > /home/changbin/work/linux/tools/perf/builtin-top.c:1192 > #4 0x5611da06973c in cmd_top > /home/changbin/work/linux/tools/perf/builtin-top.c:1642 > #5 0x5611da17d038 in run_builtin > /home/changbin/work/linux/tools/perf/perf.c:302 > #6 0x5611da17d577 in handle_internal_command > /home/changbin/work/linux/tools/perf/perf.c:354 > #7 0x5611da17d97b in run_argv > /home/changbin/work/linux/tools/perf/perf.c:398 > #8 0x5611da17e0e9 in main > /home/changbin/work/linux/tools/perf/perf.c:520 > #9 0x7fdcc970f09a in __libc_start_main > (/lib/x86_64-linux-gnu/libc.so.6+0x2409a) > > SUMMARY: AddressSanitizer: heap-use-after-free > /home/work/linux/tools/include/linux/list.h:89 in __list_del > Shadow bytes around the buggy address: > 0x0c567fff8570: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd > 0x0c567fff8580: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd > 0x0c567fff8590: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd > 0x0c567fff85a0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd > 0x0c567fff85b0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd > =>0x0c567fff85c0: fd fd fd fd fd fd fd[fd]fd fd fd fd fd fd fd fd > 0x0c567fff85d0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd > 0x0c567fff85e0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd > 0x0c567fff85f0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd > 0x0c567fff8600: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd > 0x0c567fff8610: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd > Shadow byte legend (one shadow byte represents 8 application bytes): >
Re: [PATCH 5.0 05/93] perf data: Dont store auxtrace index for directory data file
On Thu, Apr 18, 2019 at 07:56:43PM +0200, Greg Kroah-Hartman wrote:
> [ Upstream commit cd3dd8dd8ff62374d90cb3f2e54b8c94106c7810 ]
>
> We can't store the auxtrace index when we store into multiple files,
> because we keep only offset for it, not the file.
>
> The auxtrace data will be processed correctly in the 'pipe' mode.
>
> Signed-off-by: Jiri Olsa
> Cc: Adrian Hunter
> Cc: Alexander Shishkin
> Cc: Alexey Budankov
> Cc: Andi Kleen
> Cc: Namhyung Kim
> Cc: Peter Zijlstra
> Cc: Stephane Eranian
> Link: http://lkml.kernel.org/r/20190308134745.5057-3-jo...@kernel.org
> Signed-off-by: Arnaldo Carvalho de Melo
> Signed-off-by: Sasha Levin
> ---
> tools/perf/builtin-record.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 882285fb9f64..3fd154f1701b 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -386,7 +386,7 @@ static int record__process_auxtrace(struct perf_tool
> *tool,
> size_t padding;
> u8 pad[8] = {0};
>
> - if (!perf_data__is_pipe(data)) {
> + if (!perf_data__is_pipe(data) && !perf_data__is_dir(data)) {
This causes the following build error on 5.0:
builtin-top.c: In function ‘__cmd_top’:
builtin-top.c:1241:3: error: label ‘out_delete’ used but not defined
goto out_delete;
^~~~
builtin-record.c: In function ‘record__process_auxtrace’:
builtin-record.c:389:36: error: implicit declaration of function
‘perf_data__is_dir’; did you mean ‘perf_data__is_pipe’?
[-Werror=implicit-function-declaration]
if (!perf_data__is_pipe(data) && !perf_data__is_dir(data)) {
^
perf_data__is_pipe
builtin-record.c:389:36: error: nested extern declaration of
‘perf_data__is_dir’ [-Werror=nested-externs]
Dropping the patch solves this error, though there is a second perf
related build error in this RC caused by 2c0bd03b5d20 ("perf top: Delete
the evlist before perf_session, fixing heap-use-after-free issue").
> off_t file_offset;
> int fd = perf_data__fd(data);
> int err;
> --
> 2.19.1
>
>
>
--
Linaro - Kernel Validation
Re: [PATCH 4.19 005/110] perf data: Dont store auxtrace index for directory data file
On Thu, Apr 18, 2019 at 07:55:54PM +0200, Greg Kroah-Hartman wrote:
> [ Upstream commit cd3dd8dd8ff62374d90cb3f2e54b8c94106c7810 ]
>
> We can't store the auxtrace index when we store into multiple files,
> because we keep only offset for it, not the file.
>
> The auxtrace data will be processed correctly in the 'pipe' mode.
>
> Signed-off-by: Jiri Olsa
> Cc: Adrian Hunter
> Cc: Alexander Shishkin
> Cc: Alexey Budankov
> Cc: Andi Kleen
> Cc: Namhyung Kim
> Cc: Peter Zijlstra
> Cc: Stephane Eranian
> Link: http://lkml.kernel.org/r/20190308134745.5057-3-jo...@kernel.org
> Signed-off-by: Arnaldo Carvalho de Melo
> Signed-off-by: Sasha Levin
> ---
> tools/perf/builtin-record.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 22ebeb92ac51..f5b438486a64 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -178,7 +178,7 @@ static int record__process_auxtrace(struct perf_tool
> *tool,
> size_t padding;
> u8 pad[8] = {0};
>
> - if (!perf_data__is_pipe(data)) {
> + if (!perf_data__is_pipe(data) && !perf_data__is_dir(data)) {
This one causes a build failure when building perf:
builtin-record.c: In function ‘record__process_auxtrace’:
builtin-record.c:181:36: error: implicit declaration of function
‘perf_data__is_dir’; did you mean ‘perf_data__is_pipe’?
[-Werror=implicit-function-declaration]
if (!perf_data__is_pipe(data) && !perf_data__is_dir(data)) {
^
perf_data__is_pipe
builtin-record.c:181:36: error: nested extern declaration of
‘perf_data__is_dir’ [-Werror=nested-externs]
It seems to require 258031c017c3 ("perf header: Add DIR_FORMAT feature
to describe directory data"), which doesn't backport cleanly. Dropping
f54f24d0f19a ("perf data: Don't store auxtrace index for directory data
file") does seem to fix the issue.
> off_t file_offset;
> int fd = perf_data__fd(data);
> int err;
> --
> 2.19.1
>
>
>
--
Linaro - Kernel Validation
Re: [PATCH 4.20 00/50] 4.20.9-stable review
On Wed, Feb 13, 2019 at 07:38:05PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.20.9 release. > There are 50 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Fri Feb 15 18:36:30 UTC 2019. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.20.9-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.20.y git commit: f4a86d6d2a0bdead7cf98d552481367e6356ef28 git describe: v4.20.8-51-gf4a86d6d2a0b Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.20-oe/build/v4.20.8-51-gf4a86d6d2a0b No regressions (compared to build v4.20.8) No fixes (compared to build v4.20.8) Ran 21515 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * ltp-fs-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.19 00/44] 4.19.22-stable review
On Wed, Feb 13, 2019 at 07:38:01PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.19.22 release. > There are 44 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Fri Feb 15 18:36:28 UTC 2019. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.19.22-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.19.y git commit: 6d76e59d5015e936ba1fc9a9d9369ed133475530 git describe: v4.19.21-45-g6d76e59d5015 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.21-45-g6d76e59d5015 No regressions (compared to build v4.19.21) No fixes (compared to build v4.19.21) Ran 21399 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 00/35] 4.14.100-stable review
On Wed, Feb 13, 2019 at 07:37:55PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.100 release. > There are 35 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Fri Feb 15 18:36:47 UTC 2019. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.14.100-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: b27110a485424c7a5b570a05e692e7c21cb3f768 git describe: v4.14.99-36-gb27110a48542 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.99-36-gb27110a48542 No regressions (compared to build v4.14.99) No fixes (compared to build v4.14.99) Ran 22415 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.9 00/24] 4.9.157-stable review
On Wed, Feb 13, 2019 at 07:37:57PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.157 release. > There are 24 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Fri Feb 15 18:36:26 UTC 2019. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.9.157-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: faa3b6b1ed9c5a1671bf42cf23aff7c202b7d360 git describe: v4.9.156-25-gfaa3b6b1ed9c Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.156-25-gfaa3b6b1ed9c No regressions (compared to build v4.9.156) No Fixes (compared to build v4.9.156) Ran 22192 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 2/2] selftests: firmware: add CONFIG_FW_LOADER_USER_HELPER_FALLBACK to config
On Mon, Feb 04, 2019 at 05:39:57PM -0600, Luis Chamberlain wrote:
> On Thu, Nov 29, 2018 at 8:31 PM Luis Chamberlain wrote:
> >
> > On Mon, Nov 26, 2018 at 09:12:16PM -0600, Dan Rue wrote:
> > > CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y is required for fw_fallback.sh.
> > > Without it, fw_fallback.sh fails with 'usermode helper disabled so
> > > ignoring test'. Enable the config in selftest so that it gets built by
> > > default.
> > >
> > > Signed-off-by: Dan Rue
> > > ---
> > > tools/testing/selftests/firmware/config | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/tools/testing/selftests/firmware/config
> > > b/tools/testing/selftests/firmware/config
> > > index bf634dda0720..913a25a4a32b 100644
> > > --- a/tools/testing/selftests/firmware/config
> > > +++ b/tools/testing/selftests/firmware/config
> > > @@ -1,5 +1,6 @@
> > > CONFIG_TEST_FIRMWARE=y
> > > CONFIG_FW_LOADER=y
> > > CONFIG_FW_LOADER_USER_HELPER=y
> > > +CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y
> > > CONFIG_IKCONFIG=y
> > > CONFIG_IKCONFIG_PROC=y
> >
> > NACK -- the point of the changes was to *allow* us to mimic such
> > configuration through a proc sysctl knob.
> >
> > You aren forcing CONFIG_FW_LOADER_USER_HELPER_FALLBACK but just having
> > CONFIG_FW_LOADER_USER_HELPER suffices to emulate the_FALLBACK
> > functionality.
>
> Dan, again, you broke the whole point to the amount of work that went
> into emulating testing. As such anyone testing their changes would
> yield incorrect results.
>
> > The issue here seems to be that *all* tests fail once a configuration is
> > found which is not suitable a tests. With the shiny new proc sysctls we
> > can test all 3 kernel configurations in one shot. Since we test 3
> > different kernel configurations naturally some of these won't have the
> > features needed, so that failure should be treated as non-fatal to allow
> > the chain of other tests to continue.
> >
> > This issue was a regression due to commit a6a9be9270c87 ("selftests:
> > firmware: return Kselftest Skip code for skipped tests") by Shuah for
> > the verify_reqs(). We need to treat this as a non-fatal / don't skip
> > return value.
> >
> > The following would fix this chaining issue:
> >
> > diff --git a/tools/testing/selftests/firmware/fw_lib.sh
> > b/tools/testing/selftests/firmware/fw_lib.sh
> > index 6c5f1b2ffb74..1cbb12e284a6 100755
> > --- a/tools/testing/selftests/firmware/fw_lib.sh
> > +++ b/tools/testing/selftests/firmware/fw_lib.sh
> > @@ -91,7 +91,7 @@ verify_reqs()
> > if [ "$TEST_REQS_FW_SYSFS_FALLBACK" = "yes" ]; then
> > if [ ! "$HAS_FW_LOADER_USER_HELPER" = "yes" ]; then
> > echo "usermode helper disabled so ignoring test"
> > - exit $ksft_skip
> > + exit 0
> > fi
> > fi
> > }
> >
> > However its not clear to me if instead we want some new special return
> > value for selftests so that the framework can detect an that an error
> > is non-fatal, and can continue. This is a tricky situation given the
> > script, existing upstream kernel module, are aware of such emulation
> > hacks via sysctl, but knowledge of this is not obvious to selftests.
> >
> > Shuah, how do you suggest we handle this corner case? If you are OK
> > with the above hunk for now I can send a fix for it. In either case
> > this commit was added on v4.18, so the fix would be a stable fix.
>
> In lieu of any suggestion I'm going to request we revert this commit
> and send the above fix.
Sorry, I didn't realize this was waiting on me. I agree with all of your
feedback. Please revert 7492902e8d22 ("selftests: firmware: add
CONFIG_FW_LOADER_USER_HELPER_FALLBACK to config") and add my Acked-by to
the proposed fix above.
Shuah, do I need to send a patch for that revert?
It would be nice if there were a way (maybe there is?) to let each of
the individual tests be exposed and run by run_kselftest.sh so that each
test gets its own proper pass/skip/fail. It could be done in this case
by making fw_run_tests.sh look more like run_kselftest.sh (running each
test in a subshell and capturing its exit code), but that starts to get
a bit fragile and ugly, too.
Dan
>
> Luis
Re: [PATCH 4.9 00/22] 4.9.148-stable review
On Fri, Dec 28, 2018 at 12:52:37PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.148 release. > There are 22 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.9.148-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: 90e2ba75f3b479bb8fb03958c1882389aeb50c45 git describe: v4.9.147-23-g90e2ba75f3b4 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.147-23-g90e2ba75f3b4 No regressions (compared to build v4.9.146-62-gbbfc30f29cb3) No fixes (compared to build v4.9.146-62-gbbfc30f29cb3) Ran 21367 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.19 00/46] 4.19.13-stable review
On Fri, Dec 28, 2018 at 12:51:54PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.19.13 release. > There are 46 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.19.13-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.19.y git commit: 08ae917b140b0fdd38906cfd569014b030a0f60e git describe: v4.19.12-47-g08ae917b140b Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.12-47-g08ae917b140b No regressions (compared to build v4.19.11-68-g2a7cb228d29c) No fixes (compared to build v4.19.11-68-g2a7cb228d29c) Ran 20389 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 00/36] 4.14.91-stable review
On Fri, Dec 28, 2018 at 12:52:16PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.91 release. > There are 36 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.14.91-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: 4554bd6c9c0c321f2e9d6603b687afc95fb0253b git describe: v4.14.90-37-g4554bd6c9c0c Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.90-37-g4554bd6c9c0c No regressions (compared to build v4.14.89-73-g592f5569e184) No fixes (compared to build v4.14.89-73-g592f5569e184) Ran 21636 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * ltp-math-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.19 00/44] 4.19.11-stable review
On Tue, Dec 18, 2018 at 05:39:12PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.19.11 release. > There are 44 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Dec 20 16:39:02 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.19.11-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.19.y git commit: 75803dcafdb3171314d8767b002143fc031611e9 git describe: v4.19.10-45-g75803dcafdb3 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.10-45-g75803dcafdb3 No regressions (compared to build v4.19.10) No fixes (compared to build v4.19.10) Ran 20521 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.19 000/142] 4.19.10-stable review
On Sat, Dec 15, 2018 at 06:11:45PM +0100, Greg Kroah-Hartman wrote: > On Sat, Dec 15, 2018 at 11:01:02AM -0600, Dan Rue wrote: > > On Fri, Dec 14, 2018 at 12:58:05PM +0100, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 4.19.10 release. > > > There are 142 patches in this series, all will be posted as a response > > > to this one. If anyone has any issues with these being applied, please > > > let me know. > > > > > > Responses should be made by Sun Dec 16 11:57:12 UTC 2018. > > > Anything received after that time might be too late. > > > > Results from Linaro’s test farm. > > Regressions detected. > > They were? My mistake. There were some false regressions that showed up and I was a bit distracted when sending the reports and missed that. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. > > > > > Summary > > > > > > kernel: 4.19.10-rc1 > > git repo: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > git branch: linux-4.19.y > > git commit: 4875bf1f86d7bdc8dbf3222ab4028239446fab3f > > git describe: v4.19.9-143-g4875bf1f86d7 > > Test details: > > https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.9-143-g4875bf1f86d7 > > > > No regressions (compared to build v4.19.9) > > > > No fixes (compared to build v4.19.9) > > > > Ran 18346 total tests in the following environments and test suites. > > This said there were no regressions. > > confused, > > greg k-h
Re: [PATCH 4.19 000/142] 4.19.10-stable review
On Fri, Dec 14, 2018 at 12:58:05PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.19.10 release. > There are 142 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sun Dec 16 11:57:12 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. Regressions detected. Summary kernel: 4.19.10-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.19.y git commit: 4875bf1f86d7bdc8dbf3222ab4028239446fab3f git describe: v4.19.9-143-g4875bf1f86d7 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.9-143-g4875bf1f86d7 No regressions (compared to build v4.19.9) No fixes (compared to build v4.19.9) Ran 18346 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-containers-tests * ltp-cve-tests * ltp-fs-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * spectre-meltdown-checker-test * ltp-cap_bounds-tests * ltp-cpuhotplug-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-timers-tests * ltp-open-posix-tests * ltp-syscalls-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 00/89] 4.14.89-stable review
On Fri, Dec 14, 2018 at 12:59:13PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.89 release. > There are 89 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sun Dec 16 11:57:01 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.14.89-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: 159976987c2f89308c6293a31e8fa9543549b94b git describe: v4.14.88-90-g159976987c2f Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.88-90-g159976987c2f No regressions (compared to build v4.14.88) No fixes (compared to build v4.14.88) Ran 21597 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.9 00/51] 4.9.146-stable review
On Fri, Dec 14, 2018 at 01:00:02PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.146 release. > There are 51 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sun Dec 16 11:56:52 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.9.146-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: 88d902c956b8078676b83e964db1f896bb548134 git describe: v4.9.145-52-g88d902c956b8 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.145-52-g88d902c956b8 No regressions (compared to build v4.9.145) No fixes (compared to build v4.9.145) Ran 21461 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.4 00/88] 4.4.168-stable review
On Fri, Dec 14, 2018 at 12:59:34PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.168 release. > There are 88 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sun Dec 16 11:56:41 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.4.168-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: 9c558d7fe359a962e214e426ffeb338e012bba39 git describe: v4.4.167-89-g9c558d7fe359 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.167-89-g9c558d7fe359 No regressions (compared to build v4.4.167-40-g840a97100a76) No fixes (compared to build v4.4.167-40-g840a97100a76) Ran 17023 total tests in the following environments and test suites. Environments -- - i386 - juno-r2 - arm64 - qemu_arm - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-open-posix-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test * install-android-platform-tools-r2600 * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none Summary kernel: 4.4.168-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.168-rc1-hikey-20181214-340 git commit: adb4d07253946d647c9afde07d2002b28b3c0ec0 git describe: 4.4.168-rc1-hikey-20181214-340 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.168-rc1-hikey-20181214-340 No regressions (compared to build 4.4.167-rc1-hikey-20181211-336) No fixes (compared to build 4.4.167-rc1-hikey-20181211-336) Ran 2756 total tests in the following environments and test suites. Environments -- - hi6220-hikey - arm64 - qemu_arm64 Test Suites --- * boot * install-android-platform-tools-r2600 * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * spectre-meltdown-checker-test -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 1/2] selftests: firmware: remove use of non-standard diff -Z option
On Thu, Nov 29, 2018 at 06:37:32PM -0800, Luis Chamberlain wrote: > On Mon, Nov 26, 2018 at 09:12:15PM -0600, Dan Rue wrote: > > diff -Z is used to trim the trailing whitespace when comparing the > > loaded firmware file with the source firmware file. However, per the > > comment in the source code, -Z should not be necessary. In testing, the > > input and output files are identical. > > > > Additionally, -Z is not a standard option and is not available in > > environments such as busybox. When -Z is not supported, diff fails with > > a usage error, which is suppressed, but then causes read_firmwares() to > > exit with a false failure message. > > NACK -- this breaks testing on debian: > > Testing with the file present... > Batched request_firmware() try #1: Files > /tmp/tmp.8GWkoSo5jZ/test-firmware.bin and > /sys/devices/virtual/misc/test_firmware/read_firmware differ > request #0: firmware was not loaded > > Please add a quirks check, enable it by default, and remove it for > Busybox. Thanks for the review. Shuah, can you please drop this one? Dan -- Linaro - Kernel Validation
Re: [PATCH 1/2] selftests: firmware: remove use of non-standard diff -Z option
On Thu, Nov 29, 2018 at 06:37:32PM -0800, Luis Chamberlain wrote: > On Mon, Nov 26, 2018 at 09:12:15PM -0600, Dan Rue wrote: > > diff -Z is used to trim the trailing whitespace when comparing the > > loaded firmware file with the source firmware file. However, per the > > comment in the source code, -Z should not be necessary. In testing, the > > input and output files are identical. > > > > Additionally, -Z is not a standard option and is not available in > > environments such as busybox. When -Z is not supported, diff fails with > > a usage error, which is suppressed, but then causes read_firmwares() to > > exit with a false failure message. > > NACK -- this breaks testing on debian: > > Testing with the file present... > Batched request_firmware() try #1: Files > /tmp/tmp.8GWkoSo5jZ/test-firmware.bin and > /sys/devices/virtual/misc/test_firmware/read_firmware differ > request #0: firmware was not loaded > > Please add a quirks check, enable it by default, and remove it for > Busybox. Thanks for the review. Shuah, can you please drop this one? Dan -- Linaro - Kernel Validation
Re: [PATCH 4.19 000/139] 4.19.7-stable review
On Wed, Dec 05, 2018 at 02:44:59PM -0200, Rafael David Tinoco wrote: > On 12/4/18 8:48 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.19.7 release. > > There are 139 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Thu Dec 6 10:36:22 UTC 2018. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.7-rc1.gz > > or in the git tree and branch at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > linux-4.19.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > > Note: As a consequence of the retpoline backport, we upgraded our > toolchain that is used to build the kernel and userspace from 7.0 to > 7.3 (containing retpoline support). Specifically, we went from Linaro's gcc version 7.1.1 20170707 (Linaro GCC 7.1-2017.08) to upstream's gcc version 7.3.0 (GCC). > > Results from Linaro’s test farm. > No regressions on arm64, arm, x86_64, and i386. > > Summary > > > kernel: 4.19.7-rc1 > git repo: > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > git branch: linux-4.19.y > git commit: 987a6da5152c29e37cc11de9a2d10a23a48015c9 > git describe: v4.19.6-140-g987a6da5152c > Test details: > https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.6-140-g987a6da5152c > > > No Regressions (compared to build v4.19.6) > > > No Fixes (compared to build v4.19.6) > > > Ran 20285 total tests in the following environments and test suites. > > Environments > -- > - dragonboard-410c - arm64 > - hi6220-hikey - arm64 > - i386 > - juno-r2 - arm64 > - qemu_arm > - qemu_arm64 > - qemu_i386 > - qemu_x86_64 > - x15 - arm > - x86_64 > > Test Suites > --- > * boot > * install-android-platform-tools-r2600 > * kselftest > * libhugetlbfs > * ltp-cap_bounds-tests > * ltp-containers-tests > * ltp-cve-tests > * ltp-fcntl-locktests-tests > * ltp-filecaps-tests > * ltp-fs-tests > * ltp-fs_bind-tests > * ltp-fs_perms_simple-tests > * ltp-fsx-tests > * ltp-hugetlb-tests > * ltp-io-tests > * ltp-ipc-tests > * ltp-math-tests > * ltp-nptl-tests > * ltp-pty-tests > * ltp-sched-tests > * ltp-securebits-tests > * ltp-syscalls-tests > * ltp-timers-tests > * ltp-open-posix-tests > * kselftest-vsyscall-mode-native > * kselftest-vsyscall-mode-none > > -- > Linaro LKFT > https://lkft.linaro.org
Re: [PATCH 4.19 000/139] 4.19.7-stable review
On Wed, Dec 05, 2018 at 02:44:59PM -0200, Rafael David Tinoco wrote: > On 12/4/18 8:48 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.19.7 release. > > There are 139 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Thu Dec 6 10:36:22 UTC 2018. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.7-rc1.gz > > or in the git tree and branch at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > linux-4.19.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > > Note: As a consequence of the retpoline backport, we upgraded our > toolchain that is used to build the kernel and userspace from 7.0 to > 7.3 (containing retpoline support). Specifically, we went from Linaro's gcc version 7.1.1 20170707 (Linaro GCC 7.1-2017.08) to upstream's gcc version 7.3.0 (GCC). > > Results from Linaro’s test farm. > No regressions on arm64, arm, x86_64, and i386. > > Summary > > > kernel: 4.19.7-rc1 > git repo: > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > git branch: linux-4.19.y > git commit: 987a6da5152c29e37cc11de9a2d10a23a48015c9 > git describe: v4.19.6-140-g987a6da5152c > Test details: > https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.6-140-g987a6da5152c > > > No Regressions (compared to build v4.19.6) > > > No Fixes (compared to build v4.19.6) > > > Ran 20285 total tests in the following environments and test suites. > > Environments > -- > - dragonboard-410c - arm64 > - hi6220-hikey - arm64 > - i386 > - juno-r2 - arm64 > - qemu_arm > - qemu_arm64 > - qemu_i386 > - qemu_x86_64 > - x15 - arm > - x86_64 > > Test Suites > --- > * boot > * install-android-platform-tools-r2600 > * kselftest > * libhugetlbfs > * ltp-cap_bounds-tests > * ltp-containers-tests > * ltp-cve-tests > * ltp-fcntl-locktests-tests > * ltp-filecaps-tests > * ltp-fs-tests > * ltp-fs_bind-tests > * ltp-fs_perms_simple-tests > * ltp-fsx-tests > * ltp-hugetlb-tests > * ltp-io-tests > * ltp-ipc-tests > * ltp-math-tests > * ltp-nptl-tests > * ltp-pty-tests > * ltp-sched-tests > * ltp-securebits-tests > * ltp-syscalls-tests > * ltp-timers-tests > * ltp-open-posix-tests > * kselftest-vsyscall-mode-native > * kselftest-vsyscall-mode-none > > -- > Linaro LKFT > https://lkft.linaro.org
[PATCH 1/2] selftests: firmware: remove use of non-standard diff -Z option
diff -Z is used to trim the trailing whitespace when comparing the
loaded firmware file with the source firmware file. However, per the
comment in the source code, -Z should not be necessary. In testing, the
input and output files are identical.
Additionally, -Z is not a standard option and is not available in
environments such as busybox. When -Z is not supported, diff fails with
a usage error, which is suppressed, but then causes read_firmwares() to
exit with a false failure message.
Signed-off-by: Dan Rue
---
tools/testing/selftests/firmware/fw_filesystem.sh | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/tools/testing/selftests/firmware/fw_filesystem.sh
b/tools/testing/selftests/firmware/fw_filesystem.sh
index a4320c4b44dc..466cf2f91ba0 100755
--- a/tools/testing/selftests/firmware/fw_filesystem.sh
+++ b/tools/testing/selftests/firmware/fw_filesystem.sh
@@ -155,11 +155,8 @@ read_firmwares()
{
for i in $(seq 0 3); do
config_set_read_fw_idx $i
- # Verify the contents are what we expect.
- # -Z required for now -- check for yourself, md5sum
- # on $FW and DIR/read_firmware will yield the same. Even
- # cmp agrees, so something is off.
- if ! diff -q -Z "$FW" $DIR/read_firmware 2>/dev/null ; then
+ # Verify the contents match
+ if ! diff -q "$FW" $DIR/read_firmware 2>/dev/null ; then
echo "request #$i: firmware was not loaded" >&2
exit 1
fi
@@ -171,7 +168,7 @@ read_firmwares_expect_nofile()
for i in $(seq 0 3); do
config_set_read_fw_idx $i
# Ensures contents differ
- if diff -q -Z "$FW" $DIR/read_firmware 2>/dev/null ; then
+ if diff -q "$FW" $DIR/read_firmware 2>/dev/null ; then
echo "request $i: file was not expected to match" >&2
exit 1
fi
--
2.19.1
[PATCH 1/2] selftests: firmware: remove use of non-standard diff -Z option
diff -Z is used to trim the trailing whitespace when comparing the
loaded firmware file with the source firmware file. However, per the
comment in the source code, -Z should not be necessary. In testing, the
input and output files are identical.
Additionally, -Z is not a standard option and is not available in
environments such as busybox. When -Z is not supported, diff fails with
a usage error, which is suppressed, but then causes read_firmwares() to
exit with a false failure message.
Signed-off-by: Dan Rue
---
tools/testing/selftests/firmware/fw_filesystem.sh | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/tools/testing/selftests/firmware/fw_filesystem.sh
b/tools/testing/selftests/firmware/fw_filesystem.sh
index a4320c4b44dc..466cf2f91ba0 100755
--- a/tools/testing/selftests/firmware/fw_filesystem.sh
+++ b/tools/testing/selftests/firmware/fw_filesystem.sh
@@ -155,11 +155,8 @@ read_firmwares()
{
for i in $(seq 0 3); do
config_set_read_fw_idx $i
- # Verify the contents are what we expect.
- # -Z required for now -- check for yourself, md5sum
- # on $FW and DIR/read_firmware will yield the same. Even
- # cmp agrees, so something is off.
- if ! diff -q -Z "$FW" $DIR/read_firmware 2>/dev/null ; then
+ # Verify the contents match
+ if ! diff -q "$FW" $DIR/read_firmware 2>/dev/null ; then
echo "request #$i: firmware was not loaded" >&2
exit 1
fi
@@ -171,7 +168,7 @@ read_firmwares_expect_nofile()
for i in $(seq 0 3); do
config_set_read_fw_idx $i
# Ensures contents differ
- if diff -q -Z "$FW" $DIR/read_firmware 2>/dev/null ; then
+ if diff -q "$FW" $DIR/read_firmware 2>/dev/null ; then
echo "request $i: file was not expected to match" >&2
exit 1
fi
--
2.19.1
[PATCH 0/2] selftests: firmware: fw_filesystem fix for busybox
Fix fw_filesystem.sh to run in an automated environment under busybox. After this change, fw_run_tests.sh still fails at some point in fw_fallback.sh, with error "usermode helper disabled so ignoring test". This is coming from fw_lib.sh:verify_reqs() because $HAS_FW_LOADER_USER_HELPER is set to no. Dan Rue (2): selftests: firmware: remove use of non-standard diff -Z option selftests: firmware: add CONFIG_FW_LOADER_USER_HELPER_FALLBACK to config tools/testing/selftests/firmware/config | 1 + tools/testing/selftests/firmware/fw_filesystem.sh | 9 +++-- 2 files changed, 4 insertions(+), 6 deletions(-) -- 2.19.1
[PATCH 2/2] selftests: firmware: add CONFIG_FW_LOADER_USER_HELPER_FALLBACK to config
CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y is required for fw_fallback.sh. Without it, fw_fallback.sh fails with 'usermode helper disabled so ignoring test'. Enable the config in selftest so that it gets built by default. Signed-off-by: Dan Rue --- tools/testing/selftests/firmware/config | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/testing/selftests/firmware/config b/tools/testing/selftests/firmware/config index bf634dda0720..913a25a4a32b 100644 --- a/tools/testing/selftests/firmware/config +++ b/tools/testing/selftests/firmware/config @@ -1,5 +1,6 @@ CONFIG_TEST_FIRMWARE=y CONFIG_FW_LOADER=y CONFIG_FW_LOADER_USER_HELPER=y +CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y -- 2.19.1
[PATCH 0/2] selftests: firmware: fw_filesystem fix for busybox
Fix fw_filesystem.sh to run in an automated environment under busybox. After this change, fw_run_tests.sh still fails at some point in fw_fallback.sh, with error "usermode helper disabled so ignoring test". This is coming from fw_lib.sh:verify_reqs() because $HAS_FW_LOADER_USER_HELPER is set to no. Dan Rue (2): selftests: firmware: remove use of non-standard diff -Z option selftests: firmware: add CONFIG_FW_LOADER_USER_HELPER_FALLBACK to config tools/testing/selftests/firmware/config | 1 + tools/testing/selftests/firmware/fw_filesystem.sh | 9 +++-- 2 files changed, 4 insertions(+), 6 deletions(-) -- 2.19.1
[PATCH 2/2] selftests: firmware: add CONFIG_FW_LOADER_USER_HELPER_FALLBACK to config
CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y is required for fw_fallback.sh. Without it, fw_fallback.sh fails with 'usermode helper disabled so ignoring test'. Enable the config in selftest so that it gets built by default. Signed-off-by: Dan Rue --- tools/testing/selftests/firmware/config | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/testing/selftests/firmware/config b/tools/testing/selftests/firmware/config index bf634dda0720..913a25a4a32b 100644 --- a/tools/testing/selftests/firmware/config +++ b/tools/testing/selftests/firmware/config @@ -1,5 +1,6 @@ CONFIG_TEST_FIRMWARE=y CONFIG_FW_LOADER=y CONFIG_FW_LOADER_USER_HELPER=y +CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y -- 2.19.1
Re: [PATCH 4.9 000/171] 4.9.136-stable review
On Thu, Nov 08, 2018 at 01:49:30PM -0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.136 release. > There are 171 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat Nov 10 21:50:40 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.9.136-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: cc46a1dedc8bc44d1f238a21ee2848ff2ca6f6d4 git describe: v4.9.135-172-gcc46a1dedc8b Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.135-172-gcc46a1dedc8b No regressions (compared to build v4.9.135) No fixes (compared to build v4.9.135) -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.4 000/114] 4.4.163-stable review
On Thu, Nov 08, 2018 at 01:50:15PM -0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.163 release. > There are 114 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat Nov 10 21:50:28 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.4.163-rc2 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: b63fc4e232dfad182f129c0a55afeb860ea0ce54 git describe: v4.4.162-116-gb63fc4e232df Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.162-116-gb63fc4e232df No regressions (compared to build v4.4.162) No fixes (compared to build v4.4.162) -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.9 000/171] 4.9.136-stable review
On Thu, Nov 08, 2018 at 01:49:30PM -0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.136 release. > There are 171 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat Nov 10 21:50:40 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.9.136-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: cc46a1dedc8bc44d1f238a21ee2848ff2ca6f6d4 git describe: v4.9.135-172-gcc46a1dedc8b Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.135-172-gcc46a1dedc8b No regressions (compared to build v4.9.135) No fixes (compared to build v4.9.135) -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.4 000/114] 4.4.163-stable review
On Thu, Nov 08, 2018 at 01:50:15PM -0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.163 release. > There are 114 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Sat Nov 10 21:50:28 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.4.163-rc2 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: b63fc4e232dfad182f129c0a55afeb860ea0ce54 git describe: v4.4.162-116-gb63fc4e232df Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.162-116-gb63fc4e232df No regressions (compared to build v4.4.162) No fixes (compared to build v4.4.162) -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.18 000/135] 4.18.15-stable review
On Tue, Oct 16, 2018 at 07:03:50PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.18.15 release. > There are 135 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Oct 18 17:04:43 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.18.15-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.18.y git commit: 62569d12d9372bc0c50a04fe8923c47fd89435fc git describe: v4.18.14-136-g62569d12d937 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.18-oe/build/v4.18.14-136-g62569d12d937 No regressions (compared to build v4.18.14) No fixes (compared to build v4.18.14) Ran 21140 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.18 000/135] 4.18.15-stable review
On Tue, Oct 16, 2018 at 07:03:50PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.18.15 release. > There are 135 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Oct 18 17:04:43 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.18.15-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.18.y git commit: 62569d12d9372bc0c50a04fe8923c47fd89435fc git describe: v4.18.14-136-g62569d12d937 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.18-oe/build/v4.18.14-136-g62569d12d937 No regressions (compared to build v4.18.14) No fixes (compared to build v4.18.14) Ran 21140 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 000/109] 4.14.77-stable review
On Tue, Oct 16, 2018 at 07:04:28PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.77 release. > There are 109 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Oct 18 17:04:58 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.14.77-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: 3dbba66c8671a97270f35e072c54f74ddca6954e git describe: v4.14.76-110-g3dbba66c8671 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.76-110-g3dbba66c8671 No regressions (compared to build v4.14.76) No fixes (compared to build v4.14.76) Ran 21021 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * libhugetlbfs * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * kselftest * ltp-cap_bounds-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 000/109] 4.14.77-stable review
On Tue, Oct 16, 2018 at 07:04:28PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.77 release. > There are 109 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Oct 18 17:04:58 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.14.77-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: 3dbba66c8671a97270f35e072c54f74ddca6954e git describe: v4.14.76-110-g3dbba66c8671 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.76-110-g3dbba66c8671 No regressions (compared to build v4.14.76) No fixes (compared to build v4.14.76) Ran 21021 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * libhugetlbfs * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * kselftest * ltp-cap_bounds-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: Linux 4.19-rc8
On Mon, Oct 15, 2018 at 08:49:15AM +0200, Greg KH wrote: > Hi all, > > As mentioned last week, here's a -rc8 release as it seems needed. > > There were a lot of "little" pull requests this week, semi-normal for > this late in the cycle, but a lot of them were "fix up the previous fix > I just sent" which implies that people are having a few issues still. > > I also know of at least one "bad" bug that finally has a proposed fix, > so that should hopefully get merged this week. And there are some > outstanding USB fixes I know of that have not yet landed in the tree (I > blame me for that...) > > Anyway, the full shortlog is below, lots of tiny things all over the > tree. Please go and test and ensure that all works well for you. > Hopefully this should be the last -rc release. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.19.0-rc8 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git branch: master git commit: 35a7f35ad1b150ddf59a41dcac7b2fa32982be0e git describe: v4.19-rc8 Test details: https://qa-reports.linaro.org/lkft/linux-mainline-oe/build/v4.19-rc8 No regressions (compared to build v4.19-rc7) No fixes (compared to build v4.19-rc7) Ran 19898 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: Linux 4.19-rc8
On Mon, Oct 15, 2018 at 08:49:15AM +0200, Greg KH wrote: > Hi all, > > As mentioned last week, here's a -rc8 release as it seems needed. > > There were a lot of "little" pull requests this week, semi-normal for > this late in the cycle, but a lot of them were "fix up the previous fix > I just sent" which implies that people are having a few issues still. > > I also know of at least one "bad" bug that finally has a proposed fix, > so that should hopefully get merged this week. And there are some > outstanding USB fixes I know of that have not yet landed in the tree (I > blame me for that...) > > Anyway, the full shortlog is below, lots of tiny things all over the > tree. Please go and test and ensure that all works well for you. > Hopefully this should be the last -rc release. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.19.0-rc8 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git branch: master git commit: 35a7f35ad1b150ddf59a41dcac7b2fa32982be0e git describe: v4.19-rc8 Test details: https://qa-reports.linaro.org/lkft/linux-mainline-oe/build/v4.19-rc8 No regressions (compared to build v4.19-rc7) No fixes (compared to build v4.19-rc7) Ran 19898 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 000/137] 4.14.74-stable review
On Tue, Oct 02, 2018 at 06:23:21AM -0700, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.74 release. > There are 137 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Oct 4 13:24:18 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.14.74-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: 34a960c72ac4156519f59391bcab9b0677e46bc9 git describe: v4.14.73-139-g34a960c72ac4 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.73-139-g34a960c72ac4 No regressions (compared to build v4.14.73) Ran 21220 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 000/137] 4.14.74-stable review
On Tue, Oct 02, 2018 at 06:23:21AM -0700, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.74 release. > There are 137 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Oct 4 13:24:18 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.14.74-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: 34a960c72ac4156519f59391bcab9b0677e46bc9 git describe: v4.14.73-139-g34a960c72ac4 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.73-139-g34a960c72ac4 No regressions (compared to build v4.14.73) Ran 21220 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.18 000/228] 4.18.12-stable review
On Tue, Oct 02, 2018 at 06:21:37AM -0700, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.18.12 release. > There are 228 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Oct 4 13:24:08 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.18.12-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.18.y git commit: e894b754af73d0948e34f61e6070f2d9407a4f98 git describe: v4.18.11-230-ge894b754af73 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.18-oe/build/v4.18.11-230-ge894b754af73 No regressions (compared to build v4.18.11) Ran 20361 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-math-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.18 000/228] 4.18.12-stable review
On Tue, Oct 02, 2018 at 06:21:37AM -0700, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.18.12 release. > There are 228 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Oct 4 13:24:08 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.18.12-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.18.y git commit: e894b754af73d0948e34f61e6070f2d9407a4f98 git describe: v4.18.11-230-ge894b754af73 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.18-oe/build/v4.18.11-230-ge894b754af73 No regressions (compared to build v4.18.11) Ran 20361 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-math-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.9 00/94] 4.9.131-stable review
On Tue, Oct 02, 2018 at 06:24:14AM -0700, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.131 release. > There are 94 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Oct 4 13:24:37 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.9.131-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: f80dcfd9c7f99eda914bb380a43af8c56dc0e4cd git describe: v4.9.130-95-gf80dcfd9c7f9 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.130-95-gf80dcfd9c7f9 No regressions (compared to build v4.9.130) Ran 21282 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.9 00/94] 4.9.131-stable review
On Tue, Oct 02, 2018 at 06:24:14AM -0700, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.131 release. > There are 94 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Oct 4 13:24:37 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.9.131-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: f80dcfd9c7f99eda914bb380a43af8c56dc0e4cd git describe: v4.9.130-95-gf80dcfd9c7f9 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.130-95-gf80dcfd9c7f9 No regressions (compared to build v4.9.130) Ran 21282 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 000/173] 4.14.72-stable review
On Tue, Sep 25, 2018 at 11:07:33AM +0200, Greg Kroah-Hartman wrote: > On Mon, Sep 24, 2018 at 01:50:34PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.72 release. > > There are 173 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Sep 26 11:30:10 UTC 2018. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.72-rc1.gz > > or in the git tree and branch at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > linux-4.14.y > > and the diffstat can be found below. > > -rc2 is out to resolve some reported problems: > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.72-rc2.gz -rc2 looks good. There is a problem on dragonboard during boot that was introduced in v4.14.71 that I didn't notice last week. We'll bisect it and report back later this week. dragonboard on the other branches (4.9, 4.18, mainline) looks fine. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.14.72-rc2 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: a514b8f4ac33c076ad63ba833cdc3325d8c2e7fc git describe: v4.14.71-171-ga514b8f4ac33 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.71-171-ga514b8f4ac33 No regressions (compared to build v4.14.71) Ran 18749 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-filecaps-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 000/173] 4.14.72-stable review
On Tue, Sep 25, 2018 at 11:07:33AM +0200, Greg Kroah-Hartman wrote: > On Mon, Sep 24, 2018 at 01:50:34PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.72 release. > > There are 173 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Sep 26 11:30:10 UTC 2018. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.72-rc1.gz > > or in the git tree and branch at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > linux-4.14.y > > and the diffstat can be found below. > > -rc2 is out to resolve some reported problems: > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.72-rc2.gz -rc2 looks good. There is a problem on dragonboard during boot that was introduced in v4.14.71 that I didn't notice last week. We'll bisect it and report back later this week. dragonboard on the other branches (4.9, 4.18, mainline) looks fine. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.14.72-rc2 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: a514b8f4ac33c076ad63ba833cdc3325d8c2e7fc git describe: v4.14.71-171-ga514b8f4ac33 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.71-171-ga514b8f4ac33 No regressions (compared to build v4.14.71) Ran 18749 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-filecaps-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.18 000/235] 4.18.10-stable review
On Tue, Sep 25, 2018 at 11:07:11AM +0200, Greg Kroah-Hartman wrote: > On Mon, Sep 24, 2018 at 01:49:46PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.18.10 release. > > There are 235 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Sep 26 11:30:01 UTC 2018. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.18.10-rc1.gz > > or in the git tree and branch at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > linux-4.18.y > > and the diffstat can be found below. > > -rc2 is out to resolve some reported problems: > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.18.10-rc2.gz Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.18.10-rc2 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.18.y git commit: a728cc9e2683aba1752aa9a0aacae4bbfc1066d2 git describe: v4.18.9-232-ga728cc9e2683 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.18-oe/build/v4.18.9-232-ga728cc9e2683 No regressions (compared to build v4.18.9) Ran 16243 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-timers-tests * ltp-syscalls-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.18 000/235] 4.18.10-stable review
On Tue, Sep 25, 2018 at 11:07:11AM +0200, Greg Kroah-Hartman wrote: > On Mon, Sep 24, 2018 at 01:49:46PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.18.10 release. > > There are 235 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Sep 26 11:30:01 UTC 2018. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.18.10-rc1.gz > > or in the git tree and branch at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > linux-4.18.y > > and the diffstat can be found below. > > -rc2 is out to resolve some reported problems: > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.18.10-rc2.gz Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.18.10-rc2 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.18.y git commit: a728cc9e2683aba1752aa9a0aacae4bbfc1066d2 git describe: v4.18.9-232-ga728cc9e2683 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.18-oe/build/v4.18.9-232-ga728cc9e2683 No regressions (compared to build v4.18.9) Ran 16243 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-timers-tests * ltp-syscalls-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.18 164/235] pinctrl: pinmux: Return selector to the pinctrl driver
On Mon, Sep 24, 2018 at 06:07:10PM -0500, Dan Rue wrote:
> On Mon, Sep 24, 2018 at 01:52:30PM +0200, Greg Kroah-Hartman wrote:
> > 4.18-stable review patch. If anyone has any objections, please let me know.
>
> I bisected a boot failure on an x15 (arm) board to this commit on
> 4.18.10-rc1. I'm also seeing issues on 4.14 and 4.18 with arm64 boards
> hikey and dragonboard 410c, but I have not investigated them yet (they
> could be unrelated).
>
> I see there are fixes to this commit that have not been backported.
> Namely:
>
> 823dd71f58eb ("pinctrl: ingenic: Fix group & function error checking")
> a203728ac6bb ("pinctrl: core: Return selector to the pinctrl driver")
>
> However, I tried adding those two in but I still see the boot failure on
> x15.
Dropping 9c5cd7b6ca4e ("pinctrl: pinmux: Return selector to the pinctrl
driver") does appear to fix the boot issues I'm seeing on x15 and hikey.
Dan
>
> Dan
>
> >
> > --
> >
> > From: Tony Lindgren
> >
> > [ Upstream commit f913cfce4ee49a3382a9ff95696f49a46e56e974 ]
> >
> > We must return the selector from pinmux_generic_add_function() so
> > pin controller device drivers can remove the right group if needed
> > for deferred probe for example. And we now must make sure that a
> > proper name is passed so we can use it to check if the entry already
> > exists.
> >
> > Note that fixes are also needed for the pin controller drivers to
> > use the selector value.
> >
> > Fixes: a76edc89b100 ("pinctrl: core: Add generic pinctrl functions for
> > managing groups")
> > Reported-by: H. Nikolaus Schaller
> > Cc: Christ van Willegen
> > Cc: Haojian Zhuang
> > Cc: Jacopo Mondi
> > Cc: Paul Cercueil
> > Cc: Sean Wang
> > Signed-off-by: Tony Lindgren
> > Tested-By: H. Nikolaus Schaller
> > Reviewed-by: Andy Shevchenko
> > Signed-off-by: Linus Walleij
> > Signed-off-by: Sasha Levin
> > Signed-off-by: Greg Kroah-Hartman
> > ---
> > drivers/pinctrl/pinmux.c | 16
> > 1 file changed, 12 insertions(+), 4 deletions(-)
> >
> > --- a/drivers/pinctrl/pinmux.c
> > +++ b/drivers/pinctrl/pinmux.c
> > @@ -308,7 +308,6 @@ static int pinmux_func_name_to_selector(
> > selector++;
> > }
> >
> > - dev_err(pctldev->dev, "function '%s' not supported\n", function);
> > return -EINVAL;
> > }
> >
> > @@ -775,6 +774,16 @@ int pinmux_generic_add_function(struct p
> > void *data)
> > {
> > struct function_desc *function;
> > + int selector;
> > +
> > + if (!name)
> > + return -EINVAL;
> > +
> > + selector = pinmux_func_name_to_selector(pctldev, name);
> > + if (selector >= 0)
> > + return selector;
> > +
> > + selector = pctldev->num_functions;
> >
> > function = devm_kzalloc(pctldev->dev, sizeof(*function), GFP_KERNEL);
> > if (!function)
> > @@ -785,12 +794,11 @@ int pinmux_generic_add_function(struct p
> > function->num_group_names = num_groups;
> > function->data = data;
> >
> > - radix_tree_insert(>pin_function_tree, pctldev->num_functions,
> > - function);
> > + radix_tree_insert(>pin_function_tree, selector, function);
> >
> > pctldev->num_functions++;
> >
> > - return 0;
> > + return selector;
> > }
> > EXPORT_SYMBOL_GPL(pinmux_generic_add_function);
> >
> >
> >
Re: [PATCH 4.18 164/235] pinctrl: pinmux: Return selector to the pinctrl driver
On Mon, Sep 24, 2018 at 06:07:10PM -0500, Dan Rue wrote:
> On Mon, Sep 24, 2018 at 01:52:30PM +0200, Greg Kroah-Hartman wrote:
> > 4.18-stable review patch. If anyone has any objections, please let me know.
>
> I bisected a boot failure on an x15 (arm) board to this commit on
> 4.18.10-rc1. I'm also seeing issues on 4.14 and 4.18 with arm64 boards
> hikey and dragonboard 410c, but I have not investigated them yet (they
> could be unrelated).
>
> I see there are fixes to this commit that have not been backported.
> Namely:
>
> 823dd71f58eb ("pinctrl: ingenic: Fix group & function error checking")
> a203728ac6bb ("pinctrl: core: Return selector to the pinctrl driver")
>
> However, I tried adding those two in but I still see the boot failure on
> x15.
Dropping 9c5cd7b6ca4e ("pinctrl: pinmux: Return selector to the pinctrl
driver") does appear to fix the boot issues I'm seeing on x15 and hikey.
Dan
>
> Dan
>
> >
> > --
> >
> > From: Tony Lindgren
> >
> > [ Upstream commit f913cfce4ee49a3382a9ff95696f49a46e56e974 ]
> >
> > We must return the selector from pinmux_generic_add_function() so
> > pin controller device drivers can remove the right group if needed
> > for deferred probe for example. And we now must make sure that a
> > proper name is passed so we can use it to check if the entry already
> > exists.
> >
> > Note that fixes are also needed for the pin controller drivers to
> > use the selector value.
> >
> > Fixes: a76edc89b100 ("pinctrl: core: Add generic pinctrl functions for
> > managing groups")
> > Reported-by: H. Nikolaus Schaller
> > Cc: Christ van Willegen
> > Cc: Haojian Zhuang
> > Cc: Jacopo Mondi
> > Cc: Paul Cercueil
> > Cc: Sean Wang
> > Signed-off-by: Tony Lindgren
> > Tested-By: H. Nikolaus Schaller
> > Reviewed-by: Andy Shevchenko
> > Signed-off-by: Linus Walleij
> > Signed-off-by: Sasha Levin
> > Signed-off-by: Greg Kroah-Hartman
> > ---
> > drivers/pinctrl/pinmux.c | 16
> > 1 file changed, 12 insertions(+), 4 deletions(-)
> >
> > --- a/drivers/pinctrl/pinmux.c
> > +++ b/drivers/pinctrl/pinmux.c
> > @@ -308,7 +308,6 @@ static int pinmux_func_name_to_selector(
> > selector++;
> > }
> >
> > - dev_err(pctldev->dev, "function '%s' not supported\n", function);
> > return -EINVAL;
> > }
> >
> > @@ -775,6 +774,16 @@ int pinmux_generic_add_function(struct p
> > void *data)
> > {
> > struct function_desc *function;
> > + int selector;
> > +
> > + if (!name)
> > + return -EINVAL;
> > +
> > + selector = pinmux_func_name_to_selector(pctldev, name);
> > + if (selector >= 0)
> > + return selector;
> > +
> > + selector = pctldev->num_functions;
> >
> > function = devm_kzalloc(pctldev->dev, sizeof(*function), GFP_KERNEL);
> > if (!function)
> > @@ -785,12 +794,11 @@ int pinmux_generic_add_function(struct p
> > function->num_group_names = num_groups;
> > function->data = data;
> >
> > - radix_tree_insert(>pin_function_tree, pctldev->num_functions,
> > - function);
> > + radix_tree_insert(>pin_function_tree, selector, function);
> >
> > pctldev->num_functions++;
> >
> > - return 0;
> > + return selector;
> > }
> > EXPORT_SYMBOL_GPL(pinmux_generic_add_function);
> >
> >
> >
Re: [PATCH 4.18 164/235] pinctrl: pinmux: Return selector to the pinctrl driver
On Mon, Sep 24, 2018 at 01:52:30PM +0200, Greg Kroah-Hartman wrote:
> 4.18-stable review patch. If anyone has any objections, please let me know.
I bisected a boot failure on an x15 (arm) board to this commit on
4.18.10-rc1. I'm also seeing issues on 4.14 and 4.18 with arm64 boards
hikey and dragonboard 410c, but I have not investigated them yet (they
could be unrelated).
I see there are fixes to this commit that have not been backported.
Namely:
823dd71f58eb ("pinctrl: ingenic: Fix group & function error checking")
a203728ac6bb ("pinctrl: core: Return selector to the pinctrl driver")
However, I tried adding those two in but I still see the boot failure on
x15.
Dan
>
> --
>
> From: Tony Lindgren
>
> [ Upstream commit f913cfce4ee49a3382a9ff95696f49a46e56e974 ]
>
> We must return the selector from pinmux_generic_add_function() so
> pin controller device drivers can remove the right group if needed
> for deferred probe for example. And we now must make sure that a
> proper name is passed so we can use it to check if the entry already
> exists.
>
> Note that fixes are also needed for the pin controller drivers to
> use the selector value.
>
> Fixes: a76edc89b100 ("pinctrl: core: Add generic pinctrl functions for
> managing groups")
> Reported-by: H. Nikolaus Schaller
> Cc: Christ van Willegen
> Cc: Haojian Zhuang
> Cc: Jacopo Mondi
> Cc: Paul Cercueil
> Cc: Sean Wang
> Signed-off-by: Tony Lindgren
> Tested-By: H. Nikolaus Schaller
> Reviewed-by: Andy Shevchenko
> Signed-off-by: Linus Walleij
> Signed-off-by: Sasha Levin
> Signed-off-by: Greg Kroah-Hartman
> ---
> drivers/pinctrl/pinmux.c | 16
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> --- a/drivers/pinctrl/pinmux.c
> +++ b/drivers/pinctrl/pinmux.c
> @@ -308,7 +308,6 @@ static int pinmux_func_name_to_selector(
> selector++;
> }
>
> - dev_err(pctldev->dev, "function '%s' not supported\n", function);
> return -EINVAL;
> }
>
> @@ -775,6 +774,16 @@ int pinmux_generic_add_function(struct p
> void *data)
> {
> struct function_desc *function;
> + int selector;
> +
> + if (!name)
> + return -EINVAL;
> +
> + selector = pinmux_func_name_to_selector(pctldev, name);
> + if (selector >= 0)
> + return selector;
> +
> + selector = pctldev->num_functions;
>
> function = devm_kzalloc(pctldev->dev, sizeof(*function), GFP_KERNEL);
> if (!function)
> @@ -785,12 +794,11 @@ int pinmux_generic_add_function(struct p
> function->num_group_names = num_groups;
> function->data = data;
>
> - radix_tree_insert(>pin_function_tree, pctldev->num_functions,
> - function);
> + radix_tree_insert(>pin_function_tree, selector, function);
>
> pctldev->num_functions++;
>
> - return 0;
> + return selector;
> }
> EXPORT_SYMBOL_GPL(pinmux_generic_add_function);
>
>
>
Re: [PATCH 4.18 164/235] pinctrl: pinmux: Return selector to the pinctrl driver
On Mon, Sep 24, 2018 at 01:52:30PM +0200, Greg Kroah-Hartman wrote:
> 4.18-stable review patch. If anyone has any objections, please let me know.
I bisected a boot failure on an x15 (arm) board to this commit on
4.18.10-rc1. I'm also seeing issues on 4.14 and 4.18 with arm64 boards
hikey and dragonboard 410c, but I have not investigated them yet (they
could be unrelated).
I see there are fixes to this commit that have not been backported.
Namely:
823dd71f58eb ("pinctrl: ingenic: Fix group & function error checking")
a203728ac6bb ("pinctrl: core: Return selector to the pinctrl driver")
However, I tried adding those two in but I still see the boot failure on
x15.
Dan
>
> --
>
> From: Tony Lindgren
>
> [ Upstream commit f913cfce4ee49a3382a9ff95696f49a46e56e974 ]
>
> We must return the selector from pinmux_generic_add_function() so
> pin controller device drivers can remove the right group if needed
> for deferred probe for example. And we now must make sure that a
> proper name is passed so we can use it to check if the entry already
> exists.
>
> Note that fixes are also needed for the pin controller drivers to
> use the selector value.
>
> Fixes: a76edc89b100 ("pinctrl: core: Add generic pinctrl functions for
> managing groups")
> Reported-by: H. Nikolaus Schaller
> Cc: Christ van Willegen
> Cc: Haojian Zhuang
> Cc: Jacopo Mondi
> Cc: Paul Cercueil
> Cc: Sean Wang
> Signed-off-by: Tony Lindgren
> Tested-By: H. Nikolaus Schaller
> Reviewed-by: Andy Shevchenko
> Signed-off-by: Linus Walleij
> Signed-off-by: Sasha Levin
> Signed-off-by: Greg Kroah-Hartman
> ---
> drivers/pinctrl/pinmux.c | 16
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> --- a/drivers/pinctrl/pinmux.c
> +++ b/drivers/pinctrl/pinmux.c
> @@ -308,7 +308,6 @@ static int pinmux_func_name_to_selector(
> selector++;
> }
>
> - dev_err(pctldev->dev, "function '%s' not supported\n", function);
> return -EINVAL;
> }
>
> @@ -775,6 +774,16 @@ int pinmux_generic_add_function(struct p
> void *data)
> {
> struct function_desc *function;
> + int selector;
> +
> + if (!name)
> + return -EINVAL;
> +
> + selector = pinmux_func_name_to_selector(pctldev, name);
> + if (selector >= 0)
> + return selector;
> +
> + selector = pctldev->num_functions;
>
> function = devm_kzalloc(pctldev->dev, sizeof(*function), GFP_KERNEL);
> if (!function)
> @@ -785,12 +794,11 @@ int pinmux_generic_add_function(struct p
> function->num_group_names = num_groups;
> function->data = data;
>
> - radix_tree_insert(>pin_function_tree, pctldev->num_functions,
> - function);
> + radix_tree_insert(>pin_function_tree, selector, function);
>
> pctldev->num_functions++;
>
> - return 0;
> + return selector;
> }
> EXPORT_SYMBOL_GPL(pinmux_generic_add_function);
>
>
>
Re: [PATCH 4.9 000/111] 4.9.129-stable review
On Mon, Sep 24, 2018 at 01:51:27PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.129 release. > There are 111 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Sep 26 11:30:16 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.9.129-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: fa7826f765a24004014c272daf1a64462966c5ed git describe: v4.9.128-112-gfa7826f765a2 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.128-112-gfa7826f765a2 No regressions (compared to build v4.9.128) Ran 20268 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.9 000/111] 4.9.129-stable review
On Mon, Sep 24, 2018 at 01:51:27PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.129 release. > There are 111 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Sep 26 11:30:16 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.9.129-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: fa7826f765a24004014c272daf1a64462966c5ed git describe: v4.9.128-112-gfa7826f765a2 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.128-112-gfa7826f765a2 No regressions (compared to build v4.9.128) Ran 20268 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.4 00/70] 4.4.158-stable review
On Mon, Sep 24, 2018 at 01:51:59PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.158 release. > There are 70 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Sep 26 11:30:25 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.4.158-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: caf273efe9e5a0544c24dfcbc3e887af5aa56657 git describe: v4.4.157-71-gcaf273efe9e5 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.157-71-gcaf273efe9e5 No regressions (compared to build v4.4.157) Ran 16823 total tests in the following environments and test suites. Environments -- - i386 - juno-r2 - arm64 - qemu_arm - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-open-posix-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none Summary kernel: 4.4.158-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.158-rc1-hikey-20180924-290 git commit: 14bb2972eaf3d110a491622f3a3330c440afcb82 git describe: 4.4.158-rc1-hikey-20180924-290 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.158-rc1-hikey-20180924-290 No regressions (compared to build 4.4.158-rc1-hikey-20180923-289) Ran 2725 total tests in the following environments and test suites. Environments -- - hi6220-hikey - arm64 - qemu_arm64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.4 00/70] 4.4.158-stable review
On Mon, Sep 24, 2018 at 01:51:59PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.158 release. > There are 70 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Sep 26 11:30:25 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.4.158-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: caf273efe9e5a0544c24dfcbc3e887af5aa56657 git describe: v4.4.157-71-gcaf273efe9e5 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.157-71-gcaf273efe9e5 No regressions (compared to build v4.4.157) Ran 16823 total tests in the following environments and test suites. Environments -- - i386 - juno-r2 - arm64 - qemu_arm - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-open-posix-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none Summary kernel: 4.4.158-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.158-rc1-hikey-20180924-290 git commit: 14bb2972eaf3d110a491622f3a3330c440afcb82 git describe: 4.4.158-rc1-hikey-20180924-290 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.158-rc1-hikey-20180924-290 No regressions (compared to build 4.4.158-rc1-hikey-20180923-289) Ran 2725 total tests in the following environments and test suites. Environments -- - hi6220-hikey - arm64 - qemu_arm64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.4 00/47] 4.4.155-stable review
On Sun, Sep 09, 2018 at 11:17:03AM +0200, Greg Kroah-Hartman wrote: > On Sun, Sep 09, 2018 at 10:22:27AM +0530, Naresh Kamboju wrote: > > On 8 September 2018 at 02:39, Greg Kroah-Hartman > > wrote: > > > This is the start of the stable review cycle for the 4.4.155 release. > > > There are 47 patches in this series, all will be posted as a response > > > to this one. If anyone has any issues with these being applied, please > > > let me know. > > > > > > Responses should be made by Sun Sep 9 21:08:44 UTC 2018. > > > Anything received after that time might be too late. > > > > > > The whole patch series can be found in one patch at: > > > > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.155-rc1.gz > > > or in the git tree and branch at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > > linux-4.4.y > > > and the diffstat can be found below. > > > > > > thanks, > > > > > > greg k-h > > > > > > - > > > Pseudo-Shortlog of commits: > > > > > > Jann Horn > > > userns: move user access out of the mutex > > > > Results from Linaro’s test farm. > > Regressions on arm64, arm, x86_64 and i386. > > LTP containers tests > > > > Test cases: userns02/03/06/07 failed on all devices. > > > > LTP: user_namespace2 1 TBROK : safe_macros.c:452: userns02.c:95: > > write(6,0x7ffc133113d0,18446744073709551615) failed: errno=EFAULT(14): > > Bad address > > > > Other bug from kernel selftests, > > mount_run_tests.sh bugs needs to be investigated. > > > > selftests: mount_run_tests.sh [FAIL] > > write to /proc/self/uid_map failed: Bad address > > -rc3 is pushed out now with, hopefully, the fix for this. Looks good. The issues we saw in -rc1 in kselftest/mount_run_tests.sh and ltp/userns* have been resolved in -rc3. The "regressions" flagged below in the report are known intermittent failures, unrelated to the content of this release. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.4.155-rc3 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: f4777549b6b8529d14ec8d0735ae16a75a576d0c git describe: v4.4.154-48-gf4777549b6b8 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.154-48-gf4777549b6b8 Regressions (compared to build v4.4.153-81-gc9eed05cd5dd) i386: ltp-open-posix-tests: * clock_settime_8-1 * test src: git://github.com/linux-test-project/ltp.git ltp-syscalls-tests: * fcntl36 * runltp_syscalls * test src: git://github.com/linux-test-project/ltp.git Ran 16810 total tests in the following environments and test suites. Environments -- - i386 - juno-r2 - arm64 - qemu_arm - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-open-posix-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none Summary kernel: 4.4.155-rc3 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.155-rc3-hikey-20180909-278 git commit: 5cfd2cd505263e1e94e7d97e3b348dcd9f5e893b git describe: 4.4.155-rc3-hikey-20180909-278 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.155-rc3-hikey-20180909-278 No regressions (compared to build v4.4.153-81-gc9eed05cd5dd) Ran 2724 total tests in the following environments and test suites. Environments -- - hi6220-hikey - arm64 - qemu_arm64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.4 00/47] 4.4.155-stable review
On Sun, Sep 09, 2018 at 11:17:03AM +0200, Greg Kroah-Hartman wrote: > On Sun, Sep 09, 2018 at 10:22:27AM +0530, Naresh Kamboju wrote: > > On 8 September 2018 at 02:39, Greg Kroah-Hartman > > wrote: > > > This is the start of the stable review cycle for the 4.4.155 release. > > > There are 47 patches in this series, all will be posted as a response > > > to this one. If anyone has any issues with these being applied, please > > > let me know. > > > > > > Responses should be made by Sun Sep 9 21:08:44 UTC 2018. > > > Anything received after that time might be too late. > > > > > > The whole patch series can be found in one patch at: > > > > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.155-rc1.gz > > > or in the git tree and branch at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > > linux-4.4.y > > > and the diffstat can be found below. > > > > > > thanks, > > > > > > greg k-h > > > > > > - > > > Pseudo-Shortlog of commits: > > > > > > Jann Horn > > > userns: move user access out of the mutex > > > > Results from Linaro’s test farm. > > Regressions on arm64, arm, x86_64 and i386. > > LTP containers tests > > > > Test cases: userns02/03/06/07 failed on all devices. > > > > LTP: user_namespace2 1 TBROK : safe_macros.c:452: userns02.c:95: > > write(6,0x7ffc133113d0,18446744073709551615) failed: errno=EFAULT(14): > > Bad address > > > > Other bug from kernel selftests, > > mount_run_tests.sh bugs needs to be investigated. > > > > selftests: mount_run_tests.sh [FAIL] > > write to /proc/self/uid_map failed: Bad address > > -rc3 is pushed out now with, hopefully, the fix for this. Looks good. The issues we saw in -rc1 in kselftest/mount_run_tests.sh and ltp/userns* have been resolved in -rc3. The "regressions" flagged below in the report are known intermittent failures, unrelated to the content of this release. Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 4.4.155-rc3 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: f4777549b6b8529d14ec8d0735ae16a75a576d0c git describe: v4.4.154-48-gf4777549b6b8 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.154-48-gf4777549b6b8 Regressions (compared to build v4.4.153-81-gc9eed05cd5dd) i386: ltp-open-posix-tests: * clock_settime_8-1 * test src: git://github.com/linux-test-project/ltp.git ltp-syscalls-tests: * fcntl36 * runltp_syscalls * test src: git://github.com/linux-test-project/ltp.git Ran 16810 total tests in the following environments and test suites. Environments -- - i386 - juno-r2 - arm64 - qemu_arm - qemu_i386 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-open-posix-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none Summary kernel: 4.4.155-rc3 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.155-rc3-hikey-20180909-278 git commit: 5cfd2cd505263e1e94e7d97e3b348dcd9f5e893b git describe: 4.4.155-rc3-hikey-20180909-278 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.155-rc3-hikey-20180909-278 No regressions (compared to build v4.4.153-81-gc9eed05cd5dd) Ran 2724 total tests in the following environments and test suites. Environments -- - hi6220-hikey - arm64 - qemu_arm64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.18 000/123] 4.18.6-stable review
On Wed, Sep 05, 2018 at 04:08:35PM +0530, Naresh Kamboju wrote: > On 5 September 2018 at 01:02, Greg Kroah-Hartman > wrote: > > On Mon, Sep 03, 2018 at 06:55:44PM +0200, Greg Kroah-Hartman wrote: > >> This is the start of the stable review cycle for the 4.18.6 release. > >> There are 123 patches in this series, all will be posted as a response > >> to this one. If anyone has any issues with these being applied, please > >> let me know. > >> > >> Responses should be made by Wed Sep 5 16:56:53 UTC 2018. > >> Anything received after that time might be too late. > >> > >> The whole patch series can be found in one patch at: > >> > >> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.18.6-rc1.gz > >> or in the git tree and branch at: > >> > >> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >> linux-4.18.y > >> and the diffstat can be found below. > > > > I have released -rc2 to fix a reported problem: > > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.18.6-rc2.gz > > I get to see 4.18.6-rc1 not rc2. > With the current results on given commit id are looking good. > > Results from Linaro’s test farm. > No regressions on arm64, arm and x86_64. You may have noticed i386 listed below under Environments. This was added last week, and runs functional testing on an i386 kernel under QEMU emulation, as well as on x86_64 server hardware. This also accounts for our total test count (unique tests * test environments) surpassing 20,000. We'll therefore be updating the email header to read: No regressions on arm64, arm, x86_64, and i386. Thanks, Dan > > Summary > > > kernel: 4.18.6-rc1 > git repo: > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > git branch: linux-4.18.y > git commit: a6a229cf7e7f147eb6d118815a01758749fa6e8d > git describe: v4.18.5-124-ga6a229cf7e7f > Test details: > https://qa-reports.linaro.org/lkft/linux-stable-rc-4.18-oe/build/v4.18.5-124-ga6a229cf7e7f > > > No regressions (compared to build v4.18.5) > > > Ran 21181 total tests in the following environments and test suites. > > Environments > -- > - dragonboard-410c - arm64 > - hi6220-hikey - arm64 > - i386 > - juno-r2 - arm64 > - qemu_arm > - qemu_arm64 > - qemu_i386 > - qemu_x86_64 > - x15 - arm > - x86_64 > > Test Suites > --- > * boot > * kselftest > * libhugetlbfs > * ltp-cap_bounds-tests > * ltp-containers-tests > * ltp-cve-tests > * ltp-fcntl-locktests-tests > * ltp-filecaps-tests > * ltp-fs-tests > * ltp-fs_bind-tests > * ltp-fs_perms_simple-tests > * ltp-fsx-tests > * ltp-hugetlb-tests > * ltp-io-tests > * ltp-ipc-tests > * ltp-math-tests > * ltp-nptl-tests > * ltp-pty-tests > * ltp-sched-tests > * ltp-securebits-tests > * ltp-syscalls-tests > * ltp-timers-tests > * prep-inline > * ltp-open-posix-tests > * kselftest-vsyscall-mode-native > * kselftest-vsyscall-mode-none > > -- > Linaro LKFT > https://lkft.linaro.org > > >
Re: [PATCH 4.18 000/123] 4.18.6-stable review
On Wed, Sep 05, 2018 at 04:08:35PM +0530, Naresh Kamboju wrote: > On 5 September 2018 at 01:02, Greg Kroah-Hartman > wrote: > > On Mon, Sep 03, 2018 at 06:55:44PM +0200, Greg Kroah-Hartman wrote: > >> This is the start of the stable review cycle for the 4.18.6 release. > >> There are 123 patches in this series, all will be posted as a response > >> to this one. If anyone has any issues with these being applied, please > >> let me know. > >> > >> Responses should be made by Wed Sep 5 16:56:53 UTC 2018. > >> Anything received after that time might be too late. > >> > >> The whole patch series can be found in one patch at: > >> > >> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.18.6-rc1.gz > >> or in the git tree and branch at: > >> > >> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >> linux-4.18.y > >> and the diffstat can be found below. > > > > I have released -rc2 to fix a reported problem: > > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.18.6-rc2.gz > > I get to see 4.18.6-rc1 not rc2. > With the current results on given commit id are looking good. > > Results from Linaro’s test farm. > No regressions on arm64, arm and x86_64. You may have noticed i386 listed below under Environments. This was added last week, and runs functional testing on an i386 kernel under QEMU emulation, as well as on x86_64 server hardware. This also accounts for our total test count (unique tests * test environments) surpassing 20,000. We'll therefore be updating the email header to read: No regressions on arm64, arm, x86_64, and i386. Thanks, Dan > > Summary > > > kernel: 4.18.6-rc1 > git repo: > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > git branch: linux-4.18.y > git commit: a6a229cf7e7f147eb6d118815a01758749fa6e8d > git describe: v4.18.5-124-ga6a229cf7e7f > Test details: > https://qa-reports.linaro.org/lkft/linux-stable-rc-4.18-oe/build/v4.18.5-124-ga6a229cf7e7f > > > No regressions (compared to build v4.18.5) > > > Ran 21181 total tests in the following environments and test suites. > > Environments > -- > - dragonboard-410c - arm64 > - hi6220-hikey - arm64 > - i386 > - juno-r2 - arm64 > - qemu_arm > - qemu_arm64 > - qemu_i386 > - qemu_x86_64 > - x15 - arm > - x86_64 > > Test Suites > --- > * boot > * kselftest > * libhugetlbfs > * ltp-cap_bounds-tests > * ltp-containers-tests > * ltp-cve-tests > * ltp-fcntl-locktests-tests > * ltp-filecaps-tests > * ltp-fs-tests > * ltp-fs_bind-tests > * ltp-fs_perms_simple-tests > * ltp-fsx-tests > * ltp-hugetlb-tests > * ltp-io-tests > * ltp-ipc-tests > * ltp-math-tests > * ltp-nptl-tests > * ltp-pty-tests > * ltp-sched-tests > * ltp-securebits-tests > * ltp-syscalls-tests > * ltp-timers-tests > * prep-inline > * ltp-open-posix-tests > * kselftest-vsyscall-mode-native > * kselftest-vsyscall-mode-none > > -- > Linaro LKFT > https://lkft.linaro.org > > >
Re: [PATCH 4.4 00/43] 4.4.148-stable review
On Tue, Aug 14, 2018 at 07:17:36PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.148 release. > There are 43 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Aug 16 17:14:59 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.4.148-rc2 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: 41fa2bf55dc979a622e7cb367c6f815d6a508a1a git describe: v4.4.147-46-g41fa2bf55dc9 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.147-46-g41fa2bf55dc9 No regressions (compared to build v4.4.147) Ran 9270 total tests in the following environments and test suites. Environments -- - juno-r2 - arm64 - qemu_arm - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none Summary kernel: 4.4.148-rc2 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.148-rc2-hikey-20180815-258 git commit: f76c67628ea73cd7814850723fd3cf4ec681c404 git describe: 4.4.148-rc2-hikey-20180815-258 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.148-rc2-hikey-20180815-258 No regressions (compared to build 4.4.148-rc1-hikey-20180814-257) Ran 2723 total tests in the following environments and test suites. Environments -- - hi6220-hikey - arm64 - qemu_arm64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.4 00/43] 4.4.148-stable review
On Tue, Aug 14, 2018 at 07:17:36PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.148 release. > There are 43 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Aug 16 17:14:59 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.4.148-rc2 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.4.y git commit: 41fa2bf55dc979a622e7cb367c6f815d6a508a1a git describe: v4.4.147-46-g41fa2bf55dc9 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.147-46-g41fa2bf55dc9 No regressions (compared to build v4.4.147) Ran 9270 total tests in the following environments and test suites. Environments -- - juno-r2 - arm64 - qemu_arm - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none Summary kernel: 4.4.148-rc2 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.148-rc2-hikey-20180815-258 git commit: f76c67628ea73cd7814850723fd3cf4ec681c404 git describe: 4.4.148-rc2-hikey-20180815-258 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.148-rc2-hikey-20180815-258 No regressions (compared to build 4.4.148-rc1-hikey-20180814-257) Ran 2723 total tests in the following environments and test suites. Environments -- - hi6220-hikey - arm64 - qemu_arm64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.9 000/107] 4.9.120-stable review
On Tue, Aug 14, 2018 at 07:16:23PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.120 release. > There are 107 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Aug 16 17:14:53 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.9.120-rc2 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: 1a93cfe683918b90ca033d21080a2990cc25b6df git describe: v4.9.119-112-g1a93cfe68391 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.119-112-g1a93cfe68391 No regressions (compared to build v4.9.119) Ran 12080 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * ltp-open-posix-tests -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.9 000/107] 4.9.120-stable review
On Tue, Aug 14, 2018 at 07:16:23PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.120 release. > There are 107 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Aug 16 17:14:53 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.9.120-rc2 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: 1a93cfe683918b90ca033d21080a2990cc25b6df git describe: v4.9.119-112-g1a93cfe68391 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.119-112-g1a93cfe68391 No regressions (compared to build v4.9.119) Ran 12080 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - juno-r2 - arm64 - qemu_arm - qemu_arm64 - qemu_x86_64 - x15 - arm - x86_64 Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * ltp-open-posix-tests -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 000/104] 4.14.63-stable review
On Tue, Aug 14, 2018 at 07:16:14PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.63 release. > There are 104 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Aug 16 17:14:49 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.14.63-rc3 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: aff06b616b3c87631fc6a162679eab65b9685c2b git describe: v4.14.62-110-gaff06b616b3c Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.62-110-gaff06b616b3c No regressions (compared to build v4.14.62) Ran 10327 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - qemu_arm - qemu_arm64 - qemu_x86_64 - x15 - arm Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 000/104] 4.14.63-stable review
On Tue, Aug 14, 2018 at 07:16:14PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.63 release. > There are 104 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Aug 16 17:14:49 UTC 2018. > Anything received after that time might be too late. Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.14.63-rc3 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: aff06b616b3c87631fc6a162679eab65b9685c2b git describe: v4.14.62-110-gaff06b616b3c Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.62-110-gaff06b616b3c No regressions (compared to build v4.14.62) Ran 10327 total tests in the following environments and test suites. Environments -- - dragonboard-410c - arm64 - hi6220-hikey - arm64 - qemu_arm - qemu_arm64 - qemu_x86_64 - x15 - arm Test Suites --- * boot * kselftest * libhugetlbfs * ltp-cap_bounds-tests * ltp-containers-tests * ltp-cve-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-timers-tests * ltp-open-posix-tests -- Linaro LKFT https://lkft.linaro.org
