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.
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.40-rc1... 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.40-rc1
Rafael J. Wysocki rafael.j.wysocki@intel.com ath10k: Drop WARN_ON()s that always trigger during system resume
Greg Kroah-Hartman gregkh@linuxfoundation.org ALSA: line6: use dynamic buffers
Jim Mattson jmattson@google.com KVM: nVMX: Fix size checks in vmx_set_nested_state
Sean Christopherson sean.j.christopherson@intel.com KVM: x86: Whitelist port 0x7e for pre-incrementing %rip
Jakub Kicinski jakub.kicinski@netronome.com net/tls: fix copy to fragments in reencrypt
Jakub Kicinski jakub.kicinski@netronome.com net/tls: don't copy negative amounts of data in reencrypt
Michael Chan michael.chan@broadcom.com bnxt_en: Fix uninitialized variable usage in bnxt_rx_pkt().
Vasundhara Volam vasundhara-v.volam@broadcom.com bnxt_en: Free short FW command HWRM memory in error path in bnxt_init_one()
Michael Chan michael.chan@broadcom.com bnxt_en: Improve multicast address setup logic.
Willem de Bruijn willemb@google.com packet: validate msg_namelen in send directly
Hangbin Liu liuhangbin@gmail.com selftests: fib_rule_tests: print the result and return 1 if any tests failed
Xin Long lucien.xin@gmail.com sctp: avoid running the sctp state machine recursively
David Howells dhowells@redhat.com rxrpc: Fix net namespace cleanup
Jakub Kicinski jakub.kicinski@netronome.com net/tls: avoid NULL pointer deref on nskb->sk in fallback
Andrew Lunn andrew@lunn.ch net: phy: marvell: Fix buffer overrun with stats counters
Dan Carpenter dan.carpenter@oracle.com net: dsa: bcm_sf2: fix buffer overflow doing set_rxnfc
Eric Dumazet edumazet@google.com l2tp: use rcu_dereference_sk_user_data() in l2tp_udp_encap_recv()
Eric Dumazet edumazet@google.com l2ip: fix possible use-after-free
Willem de Bruijn willemb@google.com ipv6: invert flowlabel sharing check in process and user mode
Eric Dumazet edumazet@google.com ipv6/flowlabel: wait rcu grace period before put_pid()
Eric Dumazet edumazet@google.com ipv6: fix races in ip6_dst_destroy()
Martin KaFai Lau kafai@fb.com ipv6: A few fixes on dereferencing rt->from
Shmulik Ladkani shmulik@metanetworks.com ipv4: ip_do_fragment: Preserve skb_iif during fragmentation
-------------
Diffstat:
Makefile | 4 +- arch/x86/include/uapi/asm/kvm.h | 1 + arch/x86/kvm/vmx.c | 4 +- arch/x86/kvm/x86.c | 21 +++++++++- drivers/net/dsa/bcm_sf2_cfp.c | 6 +++ drivers/net/ethernet/broadcom/bnxt/bnxt.c | 19 ++++++--- drivers/net/phy/marvell.c | 6 ++- drivers/net/wireless/ath/ath10k/mac.c | 2 +- include/net/sctp/command.h | 1 - net/ipv4/ip_output.c | 1 + net/ipv6/ip6_fib.c | 4 +- net/ipv6/ip6_flowlabel.c | 22 ++++++---- net/ipv6/route.c | 47 +++++++++------------ net/l2tp/l2tp_core.c | 10 ++--- net/packet/af_packet.c | 24 ++++++----- net/rxrpc/call_object.c | 32 +++++++------- net/sctp/sm_sideeffect.c | 29 ------------- net/sctp/sm_statefuns.c | 35 ++++++++++++---- net/tls/tls_device.c | 39 ++++++++++++----- net/tls/tls_device_fallback.c | 3 +- sound/usb/line6/driver.c | 60 ++++++++++++++++----------- sound/usb/line6/podhd.c | 21 ++++++---- sound/usb/line6/toneport.c | 24 ++++++++--- tools/testing/selftests/net/fib_rule_tests.sh | 6 +++ 24 files changed, 248 insertions(+), 173 deletions(-)
stable-rc/linux-4.19.y boot: 128 boots: 0 failed, 123 passed with 4 offline, 1 untried/unknown (v4.19.39-24-gb0d6421bd855)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19... Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.19.y/kernel/v4.19.39-24-...
Tree: stable-rc Branch: linux-4.19.y Git Describe: v4.19.39-24-gb0d6421bd855 Git Commit: b0d6421bd85515e878edcf33121a818666df7749 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 70 unique boards, 24 SoC families, 14 builds out of 206
Offline Platforms:
arm:
davinci_all_defconfig: gcc-7 dm365evm,legacy: 1 offline lab
exynos_defconfig: gcc-7 exynos5800-peach-pi: 1 offline lab
multi_v7_defconfig: gcc-7 exynos5800-peach-pi: 1 offline lab stih410-b2120: 1 offline lab
--- For more info write to info@kernelci.org
On 5/4/19 3:25 AM, 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.
Build results: total: 156 pass: 156 fail: 0 Qemu test results: total: 349 pass: 349 fail: 0
Guenter
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...
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
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?
On Sun, 5 May 2019 at 12:38, Greg Kroah-Hartman gregkh@linuxfoundation.org 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. We could ignore this failure as known issues.
- Naresh
On Sun, May 05, 2019 at 02:23:22PM +0530, Naresh Kamboju wrote:
On Sun, 5 May 2019 at 12:38, Greg Kroah-Hartman gregkh@linuxfoundation.org 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?
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 gregkh@linuxfoundation.org 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
Built and booted on my x86_64 machine. No dmesg regressions observed.
Thanks Bharath