This is the start of the stable review cycle for the 4.19.172 release. There are 26 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, 31 Jan 2021 10:59:01 +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.172-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.172-rc1
Eric Biggers ebiggers@google.com fs: fix lazytime expiration handling in __writeback_single_inode()
Jan Kara jack@suse.cz writeback: Drop I_DIRTY_TIME_EXPIRE
Mikulas Patocka mpatocka@redhat.com dm integrity: conditionally disable "recalculate" feature
Jean-Philippe Brucker jean-philippe@linaro.org tools: Factor HOSTCC, HOSTLD, HOSTAR definitions
Gaurav Kohli gkohli@codeaurora.org tracing: Fix race in trace_open and buffer resize call
Jason Gerecke killertofu@gmail.com HID: wacom: Correct NULL dereference on AES pen proximity
Thomas Gleixner tglx@linutronix.de futex: Handle faults correctly for PI futexes
Thomas Gleixner tglx@linutronix.de futex: Simplify fixup_pi_state_owner()
Thomas Gleixner tglx@linutronix.de futex: Use pi_state_update_owner() in put_pi_state()
Thomas Gleixner tglx@linutronix.de rtmutex: Remove unused argument from rt_mutex_proxy_unlock()
Thomas Gleixner tglx@linutronix.de futex: Provide and use pi_state_update_owner()
Thomas Gleixner tglx@linutronix.de futex: Replace pointless printk in fixup_owner()
Thomas Gleixner tglx@linutronix.de futex: Ensure the correct return value from futex_lock_pi()
Thomas Gleixner tglx@linutronix.de futex: Prevent exit livelock
Thomas Gleixner tglx@linutronix.de futex: Provide distinct return value when owner is exiting
Thomas Gleixner tglx@linutronix.de futex: Add mutex around futex exit
Thomas Gleixner tglx@linutronix.de futex: Provide state handling for exec() as well
Thomas Gleixner tglx@linutronix.de futex: Sanitize exit state handling
Thomas Gleixner tglx@linutronix.de futex: Mark the begin of futex exit explicitly
Thomas Gleixner tglx@linutronix.de futex: Set task::futex_state to DEAD right after handling futex exit
Thomas Gleixner tglx@linutronix.de futex: Split futex_mm_release() for exit/exec
Thomas Gleixner tglx@linutronix.de exit/exec: Seperate mm_release()
Thomas Gleixner tglx@linutronix.de futex: Replace PF_EXITPIDONE with a state
Thomas Gleixner tglx@linutronix.de futex: Move futex exit handling into futex code
Wang Hai wanghai38@huawei.com Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
Baruch Siach baruch@tkos.co.il gpio: mvebu: fix pwm .get_state period calculation
-------------
Diffstat:
Documentation/device-mapper/dm-integrity.txt | 7 + Makefile | 4 +- drivers/gpio/gpio-mvebu.c | 25 +- drivers/hid/wacom_sys.c | 7 +- drivers/hid/wacom_wac.h | 2 +- drivers/md/dm-integrity.c | 24 +- fs/exec.c | 2 +- fs/ext4/inode.c | 2 +- fs/fs-writeback.c | 36 +- fs/xfs/xfs_trans_inode.c | 4 +- include/linux/compat.h | 2 - include/linux/fs.h | 1 - include/linux/futex.h | 40 ++- include/linux/sched.h | 3 +- include/linux/sched/mm.h | 6 +- include/trace/events/writeback.h | 1 - kernel/exit.c | 30 +- kernel/fork.c | 40 +-- kernel/futex.c | 485 ++++++++++++++++++--------- kernel/locking/rtmutex.c | 3 +- kernel/locking/rtmutex_common.h | 3 +- kernel/trace/ring_buffer.c | 4 + mm/slub.c | 4 +- tools/build/Makefile | 4 - tools/objtool/Makefile | 9 - tools/perf/Makefile.perf | 4 - tools/power/acpi/Makefile.config | 1 - tools/scripts/Makefile.include | 10 + 28 files changed, 460 insertions(+), 303 deletions(-)
Hi!
This is the start of the stable review cycle for the 4.19.172 release. There are 26 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, Jan 29, 2021 at 12:06:57PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.172 release. There are 26 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, 31 Jan 2021 10:59:01 +0000. Anything received after that time might be too late.
Build results: total: 155 pass: 155 fail: 0 Qemu test results: total: 418 pass: 418 fail: 0
Tested-by: Guenter Roeck linux@roeck-us.net
Guenter
On 29/01/2021 18:22, Guenter Roeck wrote:
On Fri, Jan 29, 2021 at 12:06:57PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.172 release. There are 26 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.
Replying here because I don't have the original.
Test results for stable-v4.19: 12 builds: 12 pass, 0 fail 22 boots: 22 pass, 0 fail 38 tests: 38 pass, 0 fail
Linux version: 4.19.172-rc1-gd36f1541af5a Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra194-p2972-0000, tegra20-ventana, tegra210-p2371-2180, tegra30-cardhu-a04
Tested-by: Jon Hunter jonathanh@nvidia.com
Jon
On Fri, 29 Jan 2021 at 16:45, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 4.19.172 release. There are 26 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, 31 Jan 2021 10:59:01 +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.172-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.172-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: d36f1541af5ac2e86ea3548b7da2e962e4ef5266 git describe: v4.19.171-27-gd36f1541af5a 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.171)
No fixes (compared to build v4.19.171)
Ran 48448 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 - qemu-arm64-clang - qemu-arm64-kasan - qemu-x86_64-clang - 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 * 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-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-securebits-tests * perf * fwts * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-sched-tests * ltp-syscalls-tests * ltp-tracing-tests * network-basic-tests * v4l2-compliance * ltp-open-posix-tests * kvm-unit-tests * rcutorture * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none