2022-02-28 20:26:45

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.10 00/80] 5.10.103-rc1 review

This is the start of the stable review cycle for the 5.10.103 release.
There are 80 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, 02 Mar 2022 17:20:16 +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/v5.x/stable-review/patch-5.10.103-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.10.y
and the diffstat can be found below.

thanks,

greg k-h

-------------
Pseudo-Shortlog of commits:

Greg Kroah-Hartman <[email protected]>
Linux 5.10.103-rc1

Miaohe Lin <[email protected]>
memblock: use kfree() to release kmalloced memblock regions

Marc Zyngier <[email protected]>
gpio: tegra186: Fix chip_data type confusion

[email protected] <[email protected]>
tty: n_gsm: fix deadlock in gsmtty_open()

[email protected] <[email protected]>
tty: n_gsm: fix wrong tty control line for flow control

[email protected] <[email protected]>
tty: n_gsm: fix NULL pointer access due to DLCI release

[email protected] <[email protected]>
tty: n_gsm: fix proper link termination after failed open

[email protected] <[email protected]>
tty: n_gsm: fix encoding of control signal octet bit DV

Changbin Du <[email protected]>
riscv: fix oops caused by irqsoff latency tracer

Chuansheng Liu <[email protected]>
thermal: int340x: fix memory leak in int3400_notify()

Jason Gunthorpe <[email protected]>
RDMA/cma: Do not change route.addr.src_addr outside state checks

Mårten Lindahl <[email protected]>
driver core: Free DMA range map when device is released

Hongyu Xie <[email protected]>
xhci: Prevent futile URB re-submissions due to incorrect return value.

Puma Hsu <[email protected]>
xhci: re-initialize the HC during resume if HCE was set

Sebastian Andrzej Siewior <[email protected]>
usb: dwc3: gadget: Let the interrupt handler disable bottom halves.

Hans de Goede <[email protected]>
usb: dwc3: pci: Fix Bay Trail phy GPIO mappings

Fabrice Gasnier <[email protected]>
usb: dwc2: drd: fix soft connect when gadget is unconfigured

Daniele Palmas <[email protected]>
USB: serial: option: add Telit LE910R1 compositions

Slark Xiao <[email protected]>
USB: serial: option: add support for DW5829e

Steven Rostedt (Google) <[email protected]>
tracefs: Set the group ownership in apply_options() not parse_options()

Szymon Heidrich <[email protected]>
USB: gadget: validate endpoint index for xilinx udc

Daehwan Jung <[email protected]>
usb: gadget: rndis: add spinlock for rndis response list

Dmytro Bagrii <[email protected]>
Revert "USB: serial: ch341: add new Product ID for CH341A"

Sergey Shtylyov <[email protected]>
ata: pata_hpt37x: disable primary channel on HPT371

Phil Elwell <[email protected]>
sc16is7xx: Fix for incorrect data being transmitted

Miaoqian Lin <[email protected]>
iio: Fix error handling for PM

Lorenzo Bianconi <[email protected]>
iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot

Cosmin Tanislav <[email protected]>
iio: adc: ad7124: fix mask used for setting AIN_BUFP & AIN_BUFM bits

Christophe JAILLET <[email protected]>
iio: adc: men_z188_adc: Fix a resource leak in an error handling path

Steven Rostedt (Google) <[email protected]>
tracing: Have traceon and traceoff trigger honor the instance

Bart Van Assche <[email protected]>
RDMA/ib_srp: Fix a deadlock

ChenXiaoSong <[email protected]>
configfs: fix a race in configfs_{,un}register_subsystem()

Md Haris Iqbal <[email protected]>
RDMA/rtrs-clt: Move free_permit from free_clt to rtrs_clt_close

Guoqing Jiang <[email protected]>
RDMA/rtrs-clt: Kill wait_for_inflight_permits

Md Haris Iqbal <[email protected]>
RDMA/rtrs-clt: Fix possible double free in error case

Prasad Kumpatla <[email protected]>
regmap-irq: Update interrupt clear register for proper reset

Zhou Qingyang <[email protected]>
spi: spi-zynq-qspi: Fix a NULL pointer dereference in zynq_qspi_exec_mem_op()

Tariq Toukan <[email protected]>
net/mlx5e: kTLS, Use CHECKSUM_UNNECESSARY for device-offloaded packets

Ariel Levkovich <[email protected]>
net/mlx5: Fix wrong limitation of metadata match on ecpf

Maor Gottlieb <[email protected]>
net/mlx5: Fix possible deadlock on rule deletion

Dan Carpenter <[email protected]>
udp_tunnel: Fix end of loop test in udp_tunnel_nic_unregister()

Hans de Goede <[email protected]>
surface: surface3_power: Fix battery readings on batteries without a serial number

Fabio M. De Francesco <[email protected]>
net/smc: Use a mutex for locking "struct smc_pnettable"

Florian Westphal <[email protected]>
netfilter: nf_tables: fix memory leak during stateful obj update

Christophe JAILLET <[email protected]>
nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac()

Christophe Leroy <[email protected]>
net: Force inlining of checksum functions in net/checksum.h

Xiaoke Wang <[email protected]>
net: ll_temac: check the return value of devm_kmalloc()

Paul Blakey <[email protected]>
net/sched: act_ct: Fix flow table lookup after ct clear or switching zones

Gal Pressman <[email protected]>
net/mlx5e: Fix wrong return value on ioctl EEPROM query failure

Maxime Ripard <[email protected]>
drm/edid: Always set RGB444

Paul Blakey <[email protected]>
openvswitch: Fix setting ipv6 fields causing hw csum failure

Tao Liu <[email protected]>
gso: do not skip outer ip header in case of ipip and net_failover

Dan Carpenter <[email protected]>
tipc: Fix end of loop tests for list_for_each_entry()

Eric Dumazet <[email protected]>
net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends

Eric Dumazet <[email protected]>
io_uring: add a schedule point in io_add_buffers()

Eric Dumazet <[email protected]>
bpf: Add schedule points in batch ops

Felix Maurer <[email protected]>
selftests: bpf: Check bpf_msg_push_data return value

Felix Maurer <[email protected]>
bpf: Do not try bpf_msg_push_data with len 0

Guenter Roeck <[email protected]>
hwmon: Handle failure to register sensor with thermal zone correctly

Somnath Kotur <[email protected]>
bnxt_en: Fix active FEC reporting to ethtool

Manish Chopra <[email protected]>
bnx2x: fix driver load from initrd

Alexey Bayduraev <[email protected]>
perf data: Fix double free in perf_session__delete()

Xin Long <[email protected]>
ping: remove pr_err from ping_lookup

Jens Wiklander <[email protected]>
optee: use driver internal tee_context for some rpc

Jens Wiklander <[email protected]>
tee: export teedev_open() and teedev_close_context()

Brian Geffon <[email protected]>
x86/fpu: Correct pkru/xstate inconsistency

Pablo Neira Ayuso <[email protected]>
netfilter: nf_tables_offload: incorrect flow offload action array size

Oliver Neukum <[email protected]>
CDC-NCM: avoid overflow in sanity checking

Oliver Neukum <[email protected]>
USB: zaurus: support another broken Zaurus

Oliver Neukum <[email protected]>
sr9700: sanity check for packet length

Ville Syrjälä <[email protected]>
drm/i915: Correctly populate use_sagv_wm for all pipes

Qiang Yu <[email protected]>
drm/amdgpu: check vm ready by amdgpu_vm->evicting flag

Evan Quan <[email protected]>
drm/amdgpu: disable MMHUB PG for Picasso

Liang Zhang <[email protected]>
KVM: x86/mmu: make apf token non-zero to fix bug

Helge Deller <[email protected]>
parisc/unaligned: Fix ldw() and stw() unalignment handlers

Helge Deller <[email protected]>
parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel

Stefano Garzarella <[email protected]>
vhost/vsock: don't check owner in vhost_vsock_stop() while releasing

Siarhei Volkau <[email protected]>
clk: jz4725b: fix mmc0 clock gating

Su Yue <[email protected]>
btrfs: tree-checker: check item_size for dev_item

Su Yue <[email protected]>
btrfs: tree-checker: check item_size for inode_item

Zhang Qiao <[email protected]>
cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug


-------------

Diffstat:

Makefile | 4 +-
arch/parisc/kernel/unaligned.c | 14 +++---
arch/riscv/kernel/Makefile | 2 +
arch/riscv/kernel/entry.S | 10 ++--
arch/riscv/kernel/trace_irq.c | 27 +++++++++++
arch/riscv/kernel/trace_irq.h | 11 +++++
arch/x86/include/asm/fpu/internal.h | 13 +++--
arch/x86/kernel/process_32.c | 6 +--
arch/x86/kernel/process_64.c | 6 +--
arch/x86/kvm/mmu/mmu.c | 13 ++++-
drivers/ata/pata_hpt37x.c | 14 ++++++
drivers/base/dd.c | 5 ++
drivers/base/regmap/regmap-irq.c | 20 +++-----
drivers/clk/ingenic/jz4725b-cgu.c | 3 +-
drivers/gpio/gpio-tegra186.c | 14 ++++--
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 9 +++-
drivers/gpu/drm/amd/amdgpu/soc15.c | 5 +-
drivers/gpu/drm/drm_edid.c | 2 +-
drivers/gpu/drm/i915/intel_pm.c | 22 ++++-----
drivers/hwmon/hwmon.c | 14 +++---
drivers/iio/accel/bmc150-accel-core.c | 5 +-
drivers/iio/accel/kxcjk-1013.c | 5 +-
drivers/iio/accel/mma9551.c | 5 +-
drivers/iio/accel/mma9553.c | 5 +-
drivers/iio/adc/ad7124.c | 2 +-
drivers/iio/adc/men_z188_adc.c | 9 +++-
drivers/iio/gyro/bmg160_core.c | 5 +-
drivers/iio/imu/kmx61.c | 5 +-
drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 6 ++-
drivers/iio/magnetometer/bmc150_magn.c | 5 +-
drivers/infiniband/core/cma.c | 40 +++++++++-------
drivers/infiniband/ulp/rtrs/rtrs-clt.c | 56 +++++++++++-----------
drivers/infiniband/ulp/srp/ib_srp.c | 6 ++-
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c | 3 ++
drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 3 ++
.../net/ethernet/mellanox/mlx5/core/en_ethtool.c | 2 +-
drivers/net/ethernet/mellanox/mlx5/core/en_rx.c | 3 +-
.../ethernet/mellanox/mlx5/core/eswitch_offloads.c | 4 --
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c | 2 +
.../ethernet/netronome/nfp/flower/tunnel_conf.c | 4 +-
drivers/net/ethernet/xilinx/ll_temac_main.c | 2 +
drivers/net/usb/cdc_ether.c | 12 +++++
drivers/net/usb/cdc_ncm.c | 8 ++--
drivers/net/usb/sr9700.c | 2 +-
drivers/net/usb/zaurus.c | 12 +++++
drivers/platform/x86/surface3_power.c | 13 +++--
drivers/spi/spi-zynq-qspi.c | 3 ++
drivers/tee/optee/core.c | 8 ++++
drivers/tee/optee/optee_private.h | 2 +
drivers/tee/optee/rpc.c | 8 ++--
drivers/tee/tee_core.c | 6 ++-
.../intel/int340x_thermal/int3400_thermal.c | 4 ++
drivers/tty/n_gsm.c | 22 ++++++---
drivers/tty/serial/sc16is7xx.c | 3 ++
drivers/usb/dwc2/core.h | 2 +
drivers/usb/dwc2/drd.c | 6 ++-
drivers/usb/dwc3/dwc3-pci.c | 4 +-
drivers/usb/dwc3/gadget.c | 2 +
drivers/usb/gadget/function/rndis.c | 8 ++++
drivers/usb/gadget/function/rndis.h | 1 +
drivers/usb/gadget/udc/udc-xilinx.c | 6 +++
drivers/usb/host/xhci.c | 28 +++++++----
drivers/usb/serial/ch341.c | 1 -
drivers/usb/serial/option.c | 12 +++++
drivers/vhost/vsock.c | 21 +++++---
fs/btrfs/tree-checker.c | 15 ++++++
fs/configfs/dir.c | 14 ++++++
fs/io_uring.c | 1 +
fs/tracefs/inode.c | 5 +-
include/linux/tee_drv.h | 14 ++++++
include/net/checksum.h | 48 +++++++++++--------
include/net/netfilter/nf_tables.h | 2 +-
include/net/netfilter/nf_tables_offload.h | 2 -
kernel/bpf/syscall.c | 3 ++
kernel/cgroup/cpuset.c | 2 +
kernel/trace/trace_events_trigger.c | 52 +++++++++++++++++---
mm/memblock.c | 10 +++-
net/core/filter.c | 3 ++
net/core/skbuff.c | 4 +-
net/ipv4/af_inet.c | 5 +-
net/ipv4/ping.c | 1 -
net/ipv4/udp_tunnel_nic.c | 2 +-
net/ipv6/ip6_offload.c | 2 +
net/netfilter/nf_tables_api.c | 13 +++--
net/netfilter/nf_tables_offload.c | 3 +-
net/netfilter/nft_dup_netdev.c | 6 +++
net/netfilter/nft_fwd_netdev.c | 6 +++
net/netfilter/nft_immediate.c | 12 ++++-
net/openvswitch/actions.c | 46 ++++++++++++++----
net/sched/act_ct.c | 5 --
net/smc/smc_pnet.c | 42 ++++++++--------
net/smc/smc_pnet.h | 2 +-
net/tipc/name_table.c | 2 +-
net/tipc/socket.c | 2 +-
tools/perf/util/data.c | 7 ++-
.../selftests/bpf/progs/test_sockmap_kern.h | 26 ++++++----
96 files changed, 672 insertions(+), 270 deletions(-)



2022-02-28 20:27:19

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.10 78/80] tty: n_gsm: fix deadlock in gsmtty_open()

From: [email protected] <[email protected]>

commit a2ab75b8e76e455af7867e3835fd9cdf386b508f upstream.

In the current implementation the user may open a virtual tty which then
could fail to establish the underlying DLCI. The function gsmtty_open()
gets stuck in tty_port_block_til_ready() while waiting for a carrier rise.
This happens if the remote side fails to acknowledge the link establishment
request in time or completely. At some point gsm_dlci_close() is called
to abort the link establishment attempt. The function tries to inform the
associated virtual tty by performing a hangup. But the blocking loop within
tty_port_block_til_ready() is not informed about this event.
The patch proposed here fixes this by resetting the initialization state of
the virtual tty to ensure the loop exits and triggering it to make
tty_port_block_til_ready() return.

Fixes: e1eaea46bb40 ("tty: n_gsm line discipline")
Cc: [email protected]
Signed-off-by: Daniel Starke <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/tty/n_gsm.c | 3 +++
1 file changed, 3 insertions(+)

--- a/drivers/tty/n_gsm.c
+++ b/drivers/tty/n_gsm.c
@@ -1426,6 +1426,9 @@ static void gsm_dlci_close(struct gsm_dl
if (dlci->addr != 0) {
tty_port_tty_hangup(&dlci->port, false);
kfifo_reset(&dlci->fifo);
+ /* Ensure that gsmtty_open() can return. */
+ tty_port_set_initialized(&dlci->port, 0);
+ wake_up_interruptible(&dlci->port.open_wait);
} else
dlci->gsm->dead = true;
wake_up(&dlci->gsm->event);


2022-02-28 21:29:42

by Pavel Machek

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/80] 5.10.103-rc1 review

Hi!

> This is the start of the stable review cycle for the 5.10.103 release.
> There are 80 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-5.10.y

Tested-by: Pavel Machek (CIP) <[email protected]>

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Attachments:
(No filename) (661.00 B)
signature.asc (201.00 B)
Download all attachments

2022-02-28 21:47:35

by Shuah Khan

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/80] 5.10.103-rc1 review

On 2/28/22 10:23 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.103 release.
> There are 80 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, 02 Mar 2022 17:20:16 +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/v5.x/stable-review/patch-5.10.103-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.10.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>

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

Tested-by: Shuah Khan <[email protected]>

thanks,
-- Shuah

2022-02-28 23:46:31

by Florian Fainelli

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/80] 5.10.103-rc1 review



On 2/28/2022 9:23 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.103 release.
> There are 80 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, 02 Mar 2022 17:20:16 +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/v5.x/stable-review/patch-5.10.103-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.10.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

On ARCH_BRCMSTb using 32-bit and 64-bit ARM kernels:

Tested-by: Florian Fainelli <[email protected]>
--
Florian

2022-03-01 10:24:55

by Bagas Sanjaya

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/80] 5.10.103-rc1 review

On 01/03/22 00.23, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.103 release.
> There are 80 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.
>

Successfully cross-compiled for arm64 (bcm2711_defconfig, gcc 10.2.0) and
powerpc (ps3_defconfig, gcc 11.2.0).

Tested-by: Bagas Sanjaya <[email protected]>

--
An old man doll... just what I always wanted! - Clara

2022-03-01 14:59:51

by Naresh Kamboju

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/80] 5.10.103-rc1 review

On Mon, 28 Feb 2022 at 23:03, Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 5.10.103 release.
> There are 80 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, 02 Mar 2022 17:20:16 +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/v5.x/stable-review/patch-5.10.103-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.10.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 <[email protected]>

## Build
* kernel: 5.10.103-rc1
* git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
* git branch: linux-5.10.y
* git commit: 3a000049e6a1d04d2e57cd3de7783075811d62e8
* git describe: v5.10.102-81-g3a000049e6a1
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10.102-81-g3a000049e6a1

## Test Regressions (compared to v5.10.101-122-g6c935cea31db)
No test regressions found.

## Metric Regressions (compared to v5.10.101-122-g6c935cea31db)
No metric regressions found.

## Test Fixes (compared to v5.10.101-122-g6c935cea31db)
No test fixes found.

## Metric Fixes (compared to v5.10.101-122-g6c935cea31db)
No metric fixes found.

## Test result summary
total: 97503, pass: 84163, fail: 521, skip: 12008, xfail: 811

## Build Summary
* arc: 10 total, 10 passed, 0 failed
* arm: 291 total, 291 passed, 0 failed
* arm64: 41 total, 39 passed, 2 failed
* dragonboard-410c: 1 total, 1 passed, 0 failed
* hi6220-hikey: 1 total, 1 passed, 0 failed
* i386: 40 total, 40 passed, 0 failed
* juno-r2: 1 total, 1 passed, 0 failed
* mips: 37 total, 37 passed, 0 failed
* parisc: 12 total, 12 passed, 0 failed
* powerpc: 24 total, 15 passed, 9 failed
* riscv: 27 total, 27 passed, 0 failed
* s390: 21 total, 21 passed, 0 failed
* sh: 24 total, 24 passed, 0 failed
* sparc: 12 total, 12 passed, 0 failed
* x15: 1 total, 1 passed, 0 failed
* x86: 1 total, 1 passed, 0 failed
* x86_64: 41 total, 41 passed, 0 failed

## Test suites summary
* fwts
* igt-gpu-tools
* kselftest-android
* kselftest-bpf
* 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-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-livepatch
* 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-vm
* kselftest-x86
* kselftest-zram
* kunit
* kvm-unit-tests
* libgpiod
* libhugetlbfs
* 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-open-posix-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-tracing-tests
* network-basic-tests
* packetdrill
* perf
* rcutorture
* ssuite
* v4l2-compliance
* vdso

--
Linaro LKFT
https://lkft.linaro.org

2022-03-01 16:18:39

by Sudip Mukherjee

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/80] 5.10.103-rc1 review

Hi Greg,

On Mon, Feb 28, 2022 at 06:23:41PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.103 release.
> There are 80 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, 02 Mar 2022 17:20:16 +0000.
> Anything received after that time might be too late.

Build test:
mips (gcc version 11.2.1 20220213): 63 configs -> no failure
arm (gcc version 11.2.1 20220213): 105 configs -> no new failure
arm64 (gcc version 11.2.1 20220213): 3 configs -> no failure
x86_64 (gcc version 11.2.1 20220213): 4 configs -> no failure

Boot test:
x86_64: Booted on my test laptop. No regression.
x86_64: Booted on qemu. No regression. [1]
arm64: Booted on rpi4b (4GB model). No regression. [2]

[1]. https://openqa.qa.codethink.co.uk/tests/823
[2]. https://openqa.qa.codethink.co.uk/tests/824


Tested-by: Sudip Mukherjee <[email protected]>

--
Regards
Sudip

2022-03-02 09:15:42

by Guenter Roeck

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/80] 5.10.103-rc1 review

On Mon, Feb 28, 2022 at 06:23:41PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.103 release. There
> are 80 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, 02 Mar 2022 17:20:16 +0000. Anything
> received after that time might be too late.
>

Build results:
total: 161 pass: 161 fail: 0
Qemu test results:
total: 477 pass: 477 fail: 0

Tested-by: Guenter Roeck <[email protected]>

Guenter

2022-03-02 09:32:24

by Slade's Kernel Patch Bot

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/80] 5.10.103-rc1 review

On Mon, Feb 28, 2022, at 12:23 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.103 release.
> There are 80 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, 02 Mar 2022 17:20:16 +0000.
> Anything received after that time might be too late.

5.10.103-rc1 compiled and booted with no errors or regressions on my x86_64 test system.

Tested-by: Slade Watkins <[email protected]>

Cheers,
Slade