Re: [PATCH 5.2 000/313] 5.2.19-stable review

2019-10-04 Thread Guenter Roeck
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.
> 
Build results:
total: 159 pass: 159 fail: 0
Qemu test results:
total: 390 pass: 390 fail: 0

Guenter


Re: [PATCH 5.2 000/313] 5.2.19-stable review

2019-10-04 Thread Dan Rue
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 5.2 000/313] 5.2.19-stable review

2019-10-04 Thread Greg Kroah-Hartman
On Thu, Oct 03, 2019 at 04:51:34PM -0700, Kevin Hilman wrote:
> "kernelci.org bot"  writes:
> 
> > stable-rc/linux-5.2.y boot: 136 boots: 1 failed, 126 passed with 9 offline 
> > (v5.2.18-314-g2c8369f13ff8)
> >
> > Full Boot Summary: 
> > https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.2.y/kernel/v5.2.18-314-g2c8369f13ff8/
> > Full Build Summary: 
> > https://kernelci.org/build/stable-rc/branch/linux-5.2.y/kernel/v5.2.18-314-g2c8369f13ff8/
> >
> > Tree: stable-rc
> > Branch: linux-5.2.y
> > Git Describe: v5.2.18-314-g2c8369f13ff8
> > Git Commit: 2c8369f13ff8c1375690964c79ffdc0e41ab4f97
> > Git URL: 
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > Tested: 80 unique boards, 27 SoC families, 16 builds out of 209
> 
> TL;DR; all is well.
> 
> > Boot Failure Detected:
> >
> > arm64:
> > defconfig:
> > gcc-8:
> > rk3399-firefly: 1 failed lab
> 
> There's a known issue on this board I've been trying to debug with the
> mediatek maintainers, and we're not sure yet if it's a kernel issue or
> a hardware issue on my board, but for now, nothing to worry about for
> stable.

Thanks for the explaination and summary!

greg k-h


Re: [PATCH 5.2 000/313] 5.2.19-stable review

2019-10-04 Thread Jon Hunter


On 03/10/2019 16:49, 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.
> 
> 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.19-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

All tests are passing for Tegra ...

Test results for stable-v5.2:
12 builds:  12 pass, 0 fail
22 boots:   22 pass, 0 fail
38 tests:   38 pass, 0 fail

Linux version:  5.2.19-rc1-g2c8369f13ff8
Boards tested:  tegra124-jetson-tk1, tegra186-p2771-,
tegra194-p2972-, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a04

Cheers
Jon

-- 
nvpublic


Re: [PATCH 5.2 000/313] 5.2.19-stable review

2019-10-03 Thread Kevin Hilman
"kernelci.org bot"  writes:

> stable-rc/linux-5.2.y boot: 136 boots: 1 failed, 126 passed with 9 offline 
> (v5.2.18-314-g2c8369f13ff8)
>
> Full Boot Summary: 
> https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.2.y/kernel/v5.2.18-314-g2c8369f13ff8/
> Full Build Summary: 
> https://kernelci.org/build/stable-rc/branch/linux-5.2.y/kernel/v5.2.18-314-g2c8369f13ff8/
>
> Tree: stable-rc
> Branch: linux-5.2.y
> Git Describe: v5.2.18-314-g2c8369f13ff8
> Git Commit: 2c8369f13ff8c1375690964c79ffdc0e41ab4f97
> Git URL: 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> Tested: 80 unique boards, 27 SoC families, 16 builds out of 209

TL;DR; all is well.

> Boot Failure Detected:
>
> arm64:
> defconfig:
> gcc-8:
> rk3399-firefly: 1 failed lab

There's a known issue on this board I've been trying to debug with the
mediatek maintainers, and we're not sure yet if it's a kernel issue or
a hardware issue on my board, but for now, nothing to worry about for
stable.

Kevin



Re: [PATCH 5.2 000/313] 5.2.19-stable review

2019-10-03 Thread shuah

On 10/3/19 9:49 AM, 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.

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.19-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



Compiled and booted on my test system. No dmesg regressions.

thanks,
-- Shuah


Re: [PATCH 5.2 000/313] 5.2.19-stable review

2019-10-03 Thread kernelci.org bot
stable-rc/linux-5.2.y boot: 136 boots: 1 failed, 126 passed with 9 offline 
(v5.2.18-314-g2c8369f13ff8)

Full Boot Summary: 
https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.2.y/kernel/v5.2.18-314-g2c8369f13ff8/
Full Build Summary: 
https://kernelci.org/build/stable-rc/branch/linux-5.2.y/kernel/v5.2.18-314-g2c8369f13ff8/

Tree: stable-rc
Branch: linux-5.2.y
Git Describe: v5.2.18-314-g2c8369f13ff8
Git Commit: 2c8369f13ff8c1375690964c79ffdc0e41ab4f97
Git URL: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 80 unique boards, 27 SoC families, 16 builds out of 209

Boot Failure Detected:

arm64:
defconfig:
gcc-8:
rk3399-firefly: 1 failed lab

Offline Platforms:

arm:

qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab

davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab

sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab

multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
sun5i-r8-chip: 1 offline lab

arm64:

defconfig:
gcc-8
apq8016-sbc: 1 offline lab

---
For more info write to 


[PATCH 5.2 000/313] 5.2.19-stable review

2019-10-03 Thread Greg Kroah-Hartman
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.

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.19-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

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman 
Linux 5.2.19-rc1

Pi-Hsun Shih 
platform/chrome: cros_ec_rpmsg: Fix race with host command when probe failed

Lorenzo Bianconi 
mt76: mt7615: fix mt7615 firmware path definitions

Lorenzo Bianconi 
mt76: mt7615: always release sem in mt7615_load_patch

NeilBrown 
md/raid0: avoid RAID0 data corruption due to layout confusion.

Kai-Heng Feng 
drm/amd/display: Restore backlight brightness after system resume

Pavel Shilovsky 
CIFS: Fix oplock handling for SMB 2.1+ protocols

Murphy Zhou 
CIFS: fix max ea value size

Chris Brandt 
i2c: riic: Clear NACK in tend isr

Laurent Vivier 
hwrng: core - don't wait on add_early_randomness()

Chao Yu 
quota: fix wrong condition in is_quota_modification()

Theodore Ts'o 
ext4: fix punch hole for inline_data file systems

Rakesh Pandit 
ext4: fix warning inside ext4_convert_unwritten_extents_endio

Christophe Kerello 
mtd: rawnand: stm32_fmc2: avoid warnings when building with W=1 option

Tony Camuso 
ipmi: move message error checking to avoid deadlock

Jan Kara 
xfs: Fix stale data exposure when readahead races with hole punch

Jan Kara 
mm: Handle MADV_WILLNEED through vfs_fadvise()

Jan Kara 
fs: Export generic_fadvise()

Tetsuo Handa 
/dev/mem: Bail out upon SIGKILL.

Denis Kenzior 
cfg80211: Purge frame registrations on iftype change

NeilBrown 
md: only call set_in_sync() when it is expected to succeed.

NeilBrown 
md: don't report active array_state until after revalidate_disk() completes.

Xiao Ni 
md/raid6: Set R5_ReadError when there is read failure on parity disk

Jarkko Nikula 
ACPI / LPSS: Save/restore LPSS private registers also on Lynxpoint

Benjamin Coddington 
SUNRPC: Fix buffer handling of GSS MIC without slack

Trond Myklebust 
SUNRPC: Dequeue the request from the receive queue while we're re-encoding

Filipe Manana 
Btrfs: fix race setting up and completing qgroup rescan workers

Qu Wenruo 
btrfs: qgroup: Fix reserved data space leak if we have multiple reserve 
calls

Qu Wenruo 
btrfs: qgroup: Fix the wrong target io_tree when freeing reserved data space

Dennis Zhou 
btrfs: adjust dirty_metadata_bytes after writeback failure of extent buffer

Nikolay Borisov 
btrfs: Relinquish CPUs in btrfs_compare_trees

Filipe Manana 
Btrfs: fix use-after-free when using the tree modification log

Christophe Leroy 
btrfs: fix allocation of free space cache v1 bitmap pages

Mark Salyzyn 
ovl: filter of trusted xattr results in audit

Ding Xiang 
ovl: Fix dereferencing possible ERR_PTR()

Steve French 
smb3: fix leak in "open on server" perf counter

Steve French 
smb3: allow disabling requesting leases

Yufen Yu 
block: fix null pointer dereference in blk_mq_rq_timed_out()

Damien Le Moal 
block: mq-deadline: Fix queue restart handling

Stefan Assmann 
i40e: check __I40E_VF_DISABLE bit in i40e_sync_filters_subtask

Rakesh Pillai 
ath10k: fix channel info parsing for non tlv target

Jian-Hong Pan 
rtw88: pci: Use DMA sync instead of remapping in RX ISR

Jian-Hong Pan 
rtw88: pci: Rearrange the memory usage for skb in RX ISR

Roberto Sassu 
KEYS: trusted: correctly initialize digests and fix locking issue

Felix Fietkau 
mt76: round up length on mt76_wr_copy

Dave Rodgman 
lib/lzo/lzo1x_compress.c: fix alignment bug in lzo-rle

Michal Hocko 
memcg, kmem: do not fail __GFP_NOFAIL charges

Tetsuo Handa 
memcg, oom: don't require __GFP_FS when invoking memcg OOM killer

Yafang Shao 
mm/compaction.c: clear total_{migrate,free}_scanned before scanning a new 
zone

Vitaly Wool 
z3fold: fix memory leak in kmem cache

Vitaly Wool 
z3fold: fix retry mechanism in page reclaim

Bob Peterson 
gfs2: clear buf_in_tr when ending a transaction in sweep_bh_for_rgrps

Hans de Goede 
efifb: BGRT: Improve efifb_bgrt_sanity_check

Mark Brown 
regulator: Defer init completion for a while after late_initcall

Nadav Amit 
iommu/vt-d: Fix wrong analysis whether devices share the same bus

Thadeu Lima de Souza Cascardo 
alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP

Will Deacon 
iommu/arm-smmu-v3: Disable detection of ATS and PRI

Shawn Lin 
arm64: