This is the start of the stable review cycle for the 4.19.182 release. There are 8 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, 21 Mar 2021 12:17:37 +0000. 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.182-rc... 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
------------- Pseudo-Shortlog of commits:
Greg Kroah-Hartman gregkh@linuxfoundation.org Linux 4.19.182-rc1
Florian Fainelli f.fainelli@gmail.com net: dsa: b53: Support setting learning on port
DENG Qingfang dqfext@gmail.com net: dsa: tag_mtk: fix 802.1ad VLAN egress
Piotr Krysiuk piotras@gmail.com bpf: Add sanity check for upper ptr_limit
Piotr Krysiuk piotras@gmail.com bpf: Simplify alu_limit masking for pointer arithmetic
Piotr Krysiuk piotras@gmail.com bpf: Fix off-by-one for area size in creating mask to left
Piotr Krysiuk piotras@gmail.com bpf: Prohibit alu ops for pointer types not defining ptr_limit
Suzuki K Poulose suzuki.poulose@arm.com KVM: arm64: nvhe: Save the SPE context early
Jan Kara jack@suse.cz ext4: check journal inode extents more carefully
-------------
Diffstat:
Makefile | 4 ++-- arch/arm64/include/asm/kvm_hyp.h | 3 +++ arch/arm64/kvm/hyp/debug-sr.c | 24 +++++++++++++--------- arch/arm64/kvm/hyp/switch.c | 4 +++- drivers/net/dsa/b53/b53_common.c | 19 ++++++++++++++++++ drivers/net/dsa/b53/b53_regs.h | 1 + drivers/net/dsa/bcm_sf2.c | 5 ----- fs/ext4/block_validity.c | 43 ++++++++++++++++++++-------------------- fs/ext4/ext4.h | 6 +++--- fs/ext4/extents.c | 16 ++++++--------- fs/ext4/indirect.c | 6 ++---- fs/ext4/inode.c | 5 ++--- fs/ext4/mballoc.c | 4 ++-- kernel/bpf/verifier.c | 33 +++++++++++++++++++----------- net/dsa/tag_mtk.c | 19 ++++++++++++------ 15 files changed, 114 insertions(+), 78 deletions(-)
Hi!
This is the start of the stable review cycle for the 4.19.182 release. There are 8 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.
CIP testing did not find any problems here:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-4...
Tested-by: Pavel Machek (CIP) pavel@denx.de
Best regards, Pavel
On Fri, Mar 19, 2021 at 08:17:22PM +0100, Pavel Machek wrote:
Hi!
This is the start of the stable review cycle for the 4.19.182 release. There are 8 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.
CIP testing did not find any problems here:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-4...
Tested-by: Pavel Machek (CIP) pavel@denx.de
Thanks for testing!
On Fri, Mar 19, 2021 at 01:18:19PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.182 release. There are 8 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, 21 Mar 2021 12:17:37 +0000. Anything received after that time might be too late.
Build results: total: 155 pass: 154 fail: 1 Failed builds: x86_64:tools/perf Qemu test results: total: 420 pass: 420 fail: 0
jvmti/jvmti_agent.c:48:21: error: static declaration of ‘gettid’ follows non-static declaration 48 | static inline pid_t gettid(void) | ^~~~~~ In file included from /usr/include/unistd.h:1170, from jvmti/jvmti_agent.c:33: /usr/include/x86_64-linux-gnu/bits/unistd_ext.h:34:16: note: previous declaration of ‘gettid’ was here
The tools/perf error is not new. It is seen because I started updating my servers to Ubuntu 20.0. The following patches would be needed to fix the problem in v4.19.y.
8feb8efef97a tools build feature: Check if get_current_dir_name() is available 11c6cbe706f2 tools build feature: Check if eventfd() is available 4541a8bb13a8 tools build: Check if gettid() is available before providing helper fc8c0a992233 perf tools: Use %define api.pure full instead of %pure-parser
The first two patches prevent a conflict with the third patch, and the last patch fixes an unrelated build warning.
Older kernels are also affected. The list of patches needed for v4.14.y is:
0ada120c883d perf: Make perf able to build with latest libbfd (this patch is in v4.9.y but not in v4.14.y) 25ab5abf5b14 tools build feature: Check if pthread_barrier_t is available 8feb8efef97a tools build feature: Check if get_current_dir_name() is available 11c6cbe706f2 tools build feature: Check if eventfd() is available 4541a8bb13a8 tools build: Check if gettid() is available before providing helper fc8c0a992233 perf tools: Use %define api.pure full instead of %pure-parser
I tried to fix the problem in v4.9.y and v4.4.y as well, but that is pretty much hopeless. I'll have to stop testing perf builds for those kernels.
Anyway,
Tested-by: Guenter Roeck linux@roeck-us.net
Guenter
On Fri, Mar 19, 2021 at 02:21:46PM -0700, Guenter Roeck wrote:
On Fri, Mar 19, 2021 at 01:18:19PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.182 release. There are 8 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, 21 Mar 2021 12:17:37 +0000. Anything received after that time might be too late.
Build results: total: 155 pass: 154 fail: 1 Failed builds: x86_64:tools/perf Qemu test results: total: 420 pass: 420 fail: 0
jvmti/jvmti_agent.c:48:21: error: static declaration of ‘gettid’ follows non-static declaration 48 | static inline pid_t gettid(void) | ^~~~~~ In file included from /usr/include/unistd.h:1170, from jvmti/jvmti_agent.c:33: /usr/include/x86_64-linux-gnu/bits/unistd_ext.h:34:16: note: previous declaration of ‘gettid’ was here
The tools/perf error is not new. It is seen because I started updating my servers to Ubuntu 20.0. The following patches would be needed to fix the problem in v4.19.y.
8feb8efef97a tools build feature: Check if get_current_dir_name() is available 11c6cbe706f2 tools build feature: Check if eventfd() is available 4541a8bb13a8 tools build: Check if gettid() is available before providing helper fc8c0a992233 perf tools: Use %define api.pure full instead of %pure-parser
The first two patches prevent a conflict with the third patch, and the last patch fixes an unrelated build warning.
Older kernels are also affected. The list of patches needed for v4.14.y is:
0ada120c883d perf: Make perf able to build with latest libbfd (this patch is in v4.9.y but not in v4.14.y) 25ab5abf5b14 tools build feature: Check if pthread_barrier_t is available 8feb8efef97a tools build feature: Check if get_current_dir_name() is available 11c6cbe706f2 tools build feature: Check if eventfd() is available 4541a8bb13a8 tools build: Check if gettid() is available before providing helper fc8c0a992233 perf tools: Use %define api.pure full instead of %pure-parser
I tried to fix the problem in v4.9.y and v4.4.y as well, but that is pretty much hopeless. I'll have to stop testing perf builds for those kernels.
I'll suck these in for the next round of releases, thanks.
and thanks for testing.
greg k-h
On Fri, 19 Mar 2021 at 17:48, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 4.19.182 release. There are 8 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, 21 Mar 2021 12:17:37 +0000. 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.182-rc... 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
Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing lkft@linaro.org
Summary ------------------------------------------------------------------------
kernel: 4.19.182-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: 7281e11121f6fb47ea1e757b7781c5c15e3781fe git describe: v4.19.181-9-g7281e11121f6 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.19.y/build/v4.19....
No regressions (compared to build v4.19.181)
No fixes (compared to build v4.19.181)
Ran 58666 total tests in the following environments and test suites.
Environments -------------- - arm - arm64 - dragonboard-410c - arm64 - hi6220-hikey - arm64 - i386 - juno-r2 - arm64 - juno-r2-compat - juno-r2-kasan - mips - nxp-ls2088 - nxp-ls2088-64k_page_size - powerpc - qemu-arm-debug - qemu-arm64-clang - qemu-arm64-debug - qemu-arm64-kasan - qemu-i386-debug - qemu-x86_64-clang - qemu-x86_64-debug - qemu-x86_64-kasan - qemu_arm - qemu_arm64 - qemu_arm64-compat - qemu_i386 - qemu_x86_64 - qemu_x86_64-compat - s390 - sparc - x15 - arm - x86_64 - x86-kasan - x86_64
Test Suites ----------- * build * linux-log-parser * install-android-platform-tools-r2600 * kselftest- * kselftest-android * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-efivarfs * kselftest-filesystems * kselftest-firmware * kselftest-fpu * kselftest-futex * kselftest-gpio * kselftest-intel_pstate * kselftest-ipc * kselftest-ir * kselftest-kcmp * kselftest-kvm * kselftest-lib * kselftest-livepatch * kselftest-lkdtm * kselftest-membarrier * kselftest-memfd * kselftest-memory-hotplug * kselftest-mincore * kselftest-mount * kselftest-mqueue * kselftest-net * kselftest-netfilter * kselftest-nsfs * kselftest-openat2 * kselftest-pid_namespace * kselftest-pidfd * kselftest-proc * kselftest-pstore * kselftest-ptrace * kselftest-rseq * kselftest-rtc * kselftest-seccomp * kselftest-sigaltstack * kselftest-size * kselftest-splice * kselftest-static_keys * kselftest-sync * kselftest-sysctl * kselftest-tc-testing * kselftest-timens * kselftest-timers * kselftest-tmpfs * kselftest-tpm2 * kselftest-user * kselftest-zram * ltp-cap_bounds-tests * ltp-commands-tests * ltp-controllers-tests * ltp-cpuhotplug-tests * ltp-crypto-tests * ltp-cve-tests * ltp-ipc-tests * ltp-math-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * perf * v4l2-compliance * fwts * kselftest-bpf * libhugetlbfs * ltp-dio-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-mm-tests * ltp-syscalls-tests * ltp-tracing-tests * network-basic-tests * kselftest-kexec * kselftest-vm * kselftest-x86 * ltp-containers-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-open-posix-tests * kvm-unit-tests * rcutorture * kselftest-vsyscall-mode-native- * kselftest-vsyscall-mode-none- * ssuite
On 2021/3/19 20:18, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.182 release. There are 8 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, 21 Mar 2021 12:17:37 +0000. 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.182-rc... 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
Tested on arm64 and x86 for 4.19.182-rc1,
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-4.19.y Version: 4.19.182-rc1 Commit: 7281e11121f6fb47ea1e757b7781c5c15e3781fe Compiler: gcc version 7.3.0 (GCC)
arm64: -------------------------------------------------------------------- Testcase Result Summary: total: 4688 passed: 4688 failed: 0 timeout: 0 --------------------------------------------------------------------
x86: -------------------------------------------------------------------- Testcase Result Summary: total: 4688 passed: 4688 failed: 0 timeout: 0 --------------------------------------------------------------------
Tested-by: Hulk Robot hulkrobot@huawei.com
-
Greg Kroah-Hartman -
Guenter Roeck -
Naresh Kamboju -
Pavel Machek -
Samuel Zou