5.10.49-rc1 review
Subsystems (2)
Greg Kroah-Hartman
maintainercover 5.10.49-rc1 review
This is the start of the stable review cycle for the 5.10.49 release. There are 6 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, 11 Jul 2021 13:14:09 +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.49-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.49-rc1
Juergen Gross <[email protected]>
xen/events: reset active flag for lateeoi events later
Sid Manning <[email protected]>
Hexagon: change jumps to must-extend in futex_atomic_*
Sid Manning <[email protected]>
Hexagon: add target builtins to kernel
Sid Manning <[email protected]>
Hexagon: fix build errors
Laurent Pinchart <[email protected]>
media: uvcvideo: Support devices that report an OT as an entity source
Fabiano Rosas <[email protected]>
KVM: PPC: Book3S HV: Save and restore FSCR in the P9 path
-------------
Diffstat:
Makefile | 4 +- arch/hexagon/Makefile | 6 +-- arch/hexagon/include/asm/futex.h | 4 +- arch/hexagon/include/asm/timex.h | 3 +- arch/hexagon/kernel/hexagon_ksyms.c | 8 ++-- arch/hexagon/kernel/ptrace.c | 4 +- arch/hexagon/lib/Makefile | 3 +- arch/hexagon/lib/divsi3.S | 67 ++++++++++++++++++++++++++++++++ arch/hexagon/lib/memcpy_likely_aligned.S | 56 ++++++++++++++++++++++++++ arch/hexagon/lib/modsi3.S | 46 ++++++++++++++++++++++ arch/hexagon/lib/udivsi3.S | 38 ++++++++++++++++++ arch/hexagon/lib/umodsi3.S | 36 +++++++++++++++++ arch/powerpc/kvm/book3s_hv.c | 4 ++ drivers/media/usb/uvc/uvc_driver.c | 32 +++++++++++++++ drivers/xen/events/events_base.c | 23 +++++++++-- 15 files changed, 315 insertions(+), 19 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/6 KVM: PPC: Book3S HV: Save and restore FSCR in the P9 path
From: Fabiano Rosas <[email protected]>
commit 25edcc50d76c834479d11fcc7de46f3da4d95121 upstream.
The Facility Status and Control Register is a privileged SPR that defines the availability of some features in problem state. Since it can be written by the guest, we must restore it to the previous host value after guest exit.
This restoration is currently done by taking the value from current->thread.fscr, which in the P9 path is not enough anymore because the guest could context switch the QEMU thread, causing the guest-current value to be saved into the thread struct.
The above situation manifested when running a QEMU linked against a libc with System Call Vectored support, which causes scv instructions to be run by QEMU early during the guest boot (during SLOF), at which point the FSCR is 0 due to guest entry. After a few scv calls (1 to a couple hundred), the context switching happens and the QEMU thread runs with the guest value, resulting in a Facility Unavailable interrupt.
This patch saves and restores the host value of FSCR in the inner guest entry loop in a way independent of current->thread.fscr. The old way of doing it is still kept in place because it works for the old entry path.
--- arch/powerpc/kvm/book3s_hv.c | 4 ++++ 1 file changed, 4 insertions(+)
arch/powerpc/kvm/book3s_hv.c +4 -0
@@ -3583,6 +3583,7 @@ static int kvmhv_p9_guest_entry(struct kunsigned long host_tidr =mfspr (SPRN_TIDR );unsigned long host_iamr =mfspr (SPRN_IAMR );unsigned long host_amr =mfspr (SPRN_AMR ); +unsigned long host_fscr =mfspr (SPRN_FSCR );s64 dec;u64 tb;int trap, save_pmu;
@@ -3726,6 +3727,9 @@ static int kvmhv_p9_guest_entry(struct kif (host_amr != vcpu->arch.amr)mtspr (SPRN_AMR , host_amr); +if (host_fscr != vcpu->arch.fscr) +mtspr (SPRN_FSCR , host_fscr); +msr_check_and_set (MSR_FP |MSR_VEC |MSR_VSX );store_fp_state (&vcpu->arch.fp);#ifdef CONFIG_ALTIVEC
Greg Kroah-Hartman
maintainerPATCH 2/6 media: uvcvideo: Support devices that report an OT as an entity source
In reply to Greg Kroah-HartmanFrom: Laurent Pinchart <[email protected]>
commit 4ca052b4ea621d0002a5e5feace51f60ad5e6b23 upstream.
Some devices reference an output terminal as the source of extension units. This is incorrect, as output terminals only have an input pin, and thus can't be connected to any entity in the forward direction. The resulting topology would cause issues when registering the media controller graph. To avoid this problem, connect the extension unit to the source of the output terminal instead.
While at it, and while no device has been reported to be affected by this issue, also handle forward scans where two output terminals would be connected together, and skip the terminals found through such an invalid connection.
--- drivers/media/usb/uvc/uvc_driver.c | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+)
drivers/media/usb/uvc/uvc_driver.c +32 -0
@@ -1588,6 +1588,31 @@ static int uvc_scan_chain_forward(structreturn -EINVAL ; } +/* +* Some devices reference an output terminal as the +* source of extension units. This is incorrect, as +* output terminals only have an input pin, and thus +* can't be connected to any entity in the forward +* direction. The resulting topology would cause issues +* when registering the media controller graph. To +* avoid this problem, connect the extension unit to +* the source of the output terminal instead. +*/ +if (UVC_ENTITY_IS_OTERM (entity)) { +struct uvc_entity *source; + + source =uvc_entity_by_id (chain->dev, + entity->baSourceID[0 ]); +if (!source) { +uvc_trace (UVC_TRACE_DESCR , +"Can't connect extension unit %u in chain\n" , + forward->id); +break ; + } + + forward->baSourceID[0 ] = source->id; + } +list_add_tail (&forward->chain, &chain->entities);if (uvc_trace_param &UVC_TRACE_PROBE ) {if (!found)
@@ -1608,6 +1633,13 @@ static int uvc_scan_chain_forward(structreturn -EINVAL ; } +if (UVC_ENTITY_IS_OTERM (entity)) { +uvc_trace (UVC_TRACE_DESCR , +"Unsupported connection between output terminals %u and %u\n" , + entity->id, forward->id); +break ; + } +list_add_tail (&forward->chain, &chain->entities);if (uvc_trace_param &UVC_TRACE_PROBE ) {if (!found)
Greg Kroah-Hartman
maintainerPATCH 3/6 Hexagon: fix build errors
In reply to Greg Kroah-HartmanFrom: Sid Manning <[email protected]>
commit 788dcee0306e1bdbae1a76d1b3478bb899c5838e upstream.
Fix type-o in ptrace.c.
Add missing include: asm/hexagon_vm.h
Remove superfluous cast.
Replace 'p3_0' with 'preds'.
Add -mlong-calls to build flags.
--- arch/hexagon/Makefile | 3 +++ arch/hexagon/include/asm/timex.h | 3 ++- arch/hexagon/kernel/ptrace.c | 4 ++-- 3 files changed, 7 insertions(+), 3 deletions(-)
arch/hexagon/Makefile +3 -0
@@ -10,6 +10,9 @@ LDFLAGS_vmlinux += -G0 # Do not use single-byte enums; these will overflow. KBUILD_CFLAGS += -fno-short-enums +# We must use long-calls: +KBUILD_CFLAGS += -mlong-calls + # Modules must use either long-calls, or use pic/plt. # Use long-calls for now, it's easier. And faster. # KBUILD_CFLAGS_MODULE += -fPIC
arch/hexagon/include/asm/timex.h +2 -1
@@ -8,6 +8,7 @@#include <asm-generic/timex.h> #include <asm/timer-regs.h> +#include <asm/hexagon_vm.h> /* Using TCX0 as our clock. CLOCK_TICK_RATE scheduled to be removed. */ #define CLOCK_TICK_RATE TCX0_CLK_RATE
@@ -16,7 +17,7 @@static inline int read_current_timer (unsigned long *timer_val) { - *timer_val = (unsigned long )__vmgettime (); + *timer_val =__vmgettime ();return 0 ; }
arch/hexagon/kernel/ptrace.c +2 -2
@@ -35,7 +35,7 @@ void user_disable_single_step(struct tasstatic int genregs_get (struct task_struct *target,const struct user_regset *regset, - srtuct membuf to) +struct membuf to) {struct pt_regs *regs =task_pt_regs (target);
@@ -54,7 +54,7 @@ static int genregs_get(struct task_strucmembuf_store (&to, regs->m0);membuf_store (&to, regs->m1);membuf_store (&to, regs->usr); -membuf_store (&to, regs->p3_0); +membuf_store (&to, regs->preds);membuf_store (&to, regs->gp);membuf_store (&to, regs->ugp);membuf_store (&to,pt_elr (regs));// pc
Greg Kroah-Hartman
maintainerPATCH 4/6 Hexagon: add target builtins to kernel
In reply to Greg Kroah-HartmanFrom: Sid Manning <[email protected]>
commit f1f99adf05f2138ff2646d756d4674e302e8d02d upstream.
Add the compiler-rt builtins like memcpy to the hexagon kernel.
Add SYM_FUNC_START/END, ksyms exports
--- arch/hexagon/Makefile | 3 - arch/hexagon/kernel/hexagon_ksyms.c | 8 +-- arch/hexagon/lib/Makefile | 3 - arch/hexagon/lib/divsi3.S | 67 +++++++++++++++++++++++++++++++ arch/hexagon/lib/memcpy_likely_aligned.S | 56 +++++++++++++++++++++++++ arch/hexagon/lib/modsi3.S | 46 +++++++++++++++++++++ arch/hexagon/lib/udivsi3.S | 38 +++++++++++++++++ arch/hexagon/lib/umodsi3.S | 36 ++++++++++++++++ 8 files changed, 249 insertions(+), 8 deletions(-)
arch/hexagon/Makefile +0 -3
@@ -33,9 +33,6 @@ TIR_NAME := r19 KBUILD_CFLAGS += -ffixed-$(TIR_NAME) -DTHREADINFO_REG=$(TIR_NAME) -D__linux__ KBUILD_AFLAGS += -DTHREADINFO_REG=$(TIR_NAME) -LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name 2>/dev/null) -libs-y += $(LIBGCC) - head-y := arch/hexagon/kernel/head.o core-y += arch/hexagon/kernel/ \
arch/hexagon/kernel/hexagon_ksyms.c +4 -4
@@ -35,8 +35,8 @@ EXPORT_SYMBOL(_dflt_cache_att);DECLARE_EXPORT (__hexagon_memcpy_likely_aligned_min32bytes_mult8bytes);/* Additional functions */ -DECLARE_EXPORT (__divsi3); -DECLARE_EXPORT (__modsi3); -DECLARE_EXPORT (__udivsi3); -DECLARE_EXPORT (__umodsi3); +DECLARE_EXPORT (__hexagon_divsi3); +DECLARE_EXPORT (__hexagon_modsi3); +DECLARE_EXPORT (__hexagon_udivsi3); +DECLARE_EXPORT (__hexagon_umodsi3);DECLARE_EXPORT (csum_tcpudp_magic);
arch/hexagon/lib/Makefile +2 -1
@@ -2,4 +2,5 @@ # # Makefile for hexagon-specific library files. # -obj-y = checksum.o io.o memcpy.o memset.o +obj-y = checksum.o io.o memcpy.o memset.o memcpy_likely_aligned.o \ + divsi3.o modsi3.o udivsi3.o umodsi3.o
arch/hexagon/lib/divsi3.S new file +67 -0
67 lines not on this page · raw message
arch/hexagon/lib/memcpy_likely_aligned.S new file +56 -0
56 lines not on this page · raw message
arch/hexagon/lib/modsi3.S new file +46 -0
46 lines not on this page · raw message
arch/hexagon/lib/udivsi3.S new file +38 -0
@@ -0,0 +1,38 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* + * Copyright (c) 2021, The Linux Foundation. All rights reserved. + */ + +#include <linux/linkage.h> + +SYM_FUNC_START(__hexagon_udivsi3) + { + r2 = cl0(r0) + r3 = cl0(r1) + r5:4 = combine(#1,#0) + p0 = cmp.gtu(r1,r0) + } + { + r6 = sub(r3,r2) + r4 = r1 + r1:0 = combine(r0,r4) + if (p0) jumpr r31 + } + { + r3:2 = vlslw(r5:4,r6) + loop0(1f,r6) + } + .falign +1: + { + p0 = cmp.gtu(r2,r1) + if (!p0.new) r1 = sub(r1,r2) + if (!p0.new) r0 = add(r0,r3) + r3:2 = vlsrw(r3:2,#1) + }:endloop0 + { + p0 = cmp.gtu(r2,r1) + if (!p0.new) r0 = add(r0,r3) + jumpr r31 + } +SYM_FUNC_END(__hexagon_udivsi3)
arch/hexagon/lib/umodsi3.S new file +36 -0
@@ -0,0 +1,36 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* + * Copyright (c) 2021, The Linux Foundation. All rights reserved. + */ + +#include <linux/linkage.h> + +SYM_FUNC_START(__hexagon_umodsi3) + { + r2 = cl0(r0) + r3 = cl0(r1) + p0 = cmp.gtu(r1,r0) + } + { + r2 = sub(r3,r2) + if (p0) jumpr r31 + } + { + loop0(1f,r2) + p1 = cmp.eq(r2,#0) + r2 = lsl(r1,r2) + } + .falign +1: + { + p0 = cmp.gtu(r2,r0) + if (!p0.new) r0 = sub(r0,r2) + r2 = lsr(r2,#1) + if (p1) r1 = #0 + }:endloop0 + { + p0 = cmp.gtu(r2,r0) + if (!p0.new) r0 = sub(r0,r1) + jumpr r31 + } +SYM_FUNC_END(__hexagon_umodsi3)
Greg Kroah-Hartman
maintainerPATCH 5/6 Hexagon: change jumps to must-extend in futex_atomic_*
In reply to Greg Kroah-HartmanFrom: Sid Manning <[email protected]>
commit 6fff7410f6befe5744d54f0418d65a6322998c09 upstream.
Cross-section jumps from .fixup section must be extended.
--- arch/hexagon/include/asm/futex.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/hexagon/include/asm/futex.h +2 -2
@@ -21,7 +21,7 @@"3:\n" \".section .fixup,\"ax\"\n" \"4: %1 = #%5;\n" \ -" jump 3b\n" \ +" jump ##3b\n" \".previous\n" \".section __ex_table,\"a\"\n" \".long 1b,4b,2b,4b\n" \
@@ -90,7 +90,7 @@ futex_atomic_cmpxchg_inatomic(u32 *uval,"3:\n" ".section .fixup,\"ax\"\n" "4: %0 = #%6\n" -" jump 3b\n" +" jump ##3b\n" ".previous\n" ".section __ex_table,\"a\"\n" ".long 1b,4b,2b,4b\n"
Greg Kroah-Hartman
maintainerPATCH 6/6 xen/events: reset active flag for lateeoi events later
In reply to Greg Kroah-HartmanFrom: Juergen Gross <[email protected]>
commit 3de218ff39b9e3f0d453fe3154f12a174de44b25 upstream.
In order to avoid a race condition for user events when changing cpu affinity reset the active flag only when EOI-ing the event.
This is working fine as all user events are lateeoi events. Note that lateeoi_ack_mask_dynirq() is not modified as there is no explicit call to xen_irq_lateeoi() expected later.
--- drivers/xen/events/events_base.c | 23 +++++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-)
drivers/xen/events/events_base.c +19 -4
@@ -583,6 +583,9 @@ static void xen_irq_lateeoi_locked(struc } info->eoi_time =0 ; + +/* is_active hasn't been reset yet, do it now. */ +smp_store_release (&info->is_active,0 );do_unmask (info,EVT_MASK_REASON_EOI_PENDING ); }
@@ -1807,10 +1810,22 @@ static void lateeoi_ack_dynirq(struct irstruct irq_info *info =info_for_irq (data->irq);evtchn_port_t evtchn = info ? info->evtchn :0 ; -if (VALID_EVTCHN (evtchn)) { -do_mask (info,EVT_MASK_REASON_EOI_PENDING ); -ack_dynirq (data); - } +if (!VALID_EVTCHN (evtchn)) +return ; + +do_mask (info,EVT_MASK_REASON_EOI_PENDING ); + +if (unlikely (irqd_is_setaffinity_pending (data)) && +likely (!irqd_irq_disabled (data))) { +do_mask (info,EVT_MASK_REASON_TEMPORARY ); + +clear_evtchn (evtchn); + +irq_move_masked_irq (data); + +do_unmask (info,EVT_MASK_REASON_TEMPORARY ); + }else +clear_evtchn (evtchn); }static void lateeoi_mask_ack_dynirq (struct irq_data *data)
Quoted 47 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.49 release. There are 6 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, 11 Jul 2021 13:14:09 +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.49-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-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.49-rc1Juergen Gross <[email protected]>
xen/events: reset active flag for lateeoi events laterSid Manning <[email protected]>
Hexagon: change jumps to must-extend in futex_atomic_*Sid Manning <[email protected]>
Hexagon: add target builtins to kernelSid Manning <[email protected]>
Hexagon: fix build errorsLaurent Pinchart <[email protected]>
media: uvcvideo: Support devices that report an OT as an entity sourceFabiano Rosas <[email protected]>
KVM: PPC: Book3S HV: Save and restore FSCR in the P9 path-------------
Diffstat:
Quoted 19 lines
Makefile | 4 +- arch/hexagon/Makefile | 6 +-- arch/hexagon/include/asm/futex.h | 4 +- arch/hexagon/include/asm/timex.h | 3 +- arch/hexagon/kernel/hexagon_ksyms.c | 8 ++-- arch/hexagon/kernel/ptrace.c | 4 +- arch/hexagon/lib/Makefile | 3 +- arch/hexagon/lib/divsi3.S | 67 ++++++++++++++++++++++++++++++++ arch/hexagon/lib/memcpy_likely_aligned.S | 56 ++++++++++++++++++++++++++ arch/hexagon/lib/modsi3.S | 46 ++++++++++++++++++++++ arch/hexagon/lib/udivsi3.S | 38 ++++++++++++++++++ arch/hexagon/lib/umodsi3.S | 36 +++++++++++++++++ arch/powerpc/kvm/book3s_hv.c | 4 ++ drivers/media/usb/uvc/uvc_driver.c | 32 +++++++++++++++ drivers/xen/events/events_base.c | 23 +++++++++-- 15 files changed, 315 insertions(+), 19 deletions(-)
All tests passing for Tegra ...
Test results for stable-v5.10:
10 builds: 10 pass, 0 fail
28 boots: 28 pass, 0 fail
70 tests: 70 pass, 0 failLinux version: 5.10.49-rc1-g5b40bcb16853
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
tegra20-ventana, tegra210-p2371-2180,
tegra210-p3450-0000, tegra30-cardhu-a04Jon
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.49 release. There are 6 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, 11 Jul 2021 13:14:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.49-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.10.y
and the diffstat can be found below.thanks,
greg k-h
5.10.49-rc1 Successfully Compiled and booted on my Raspberry PI 4b (8g) (bcm2711)
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.49 release. There are 6 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, 11 Jul 2021 13:14:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.49-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.10.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.49 release. There are 6 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, 11 Jul 2021 13:14:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.49-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.10.y
and the diffstat can be found below.thanks,
greg k-h
Tested on arm64 and x86 for 5.10.49-rc1,
Kernel repo:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Branch: linux-5.10.y
Version: 5.10.49-rc1
Commit: 5b40bcb16853d5fa948446202f43ea3fbcc14f33
Compiler: gcc version 7.3.0 (GCC)
arm64:
--------------------------------------------------------------------
Testcase Result Summary:
total: 8906
passed: 8906
failed: 0
timeout: 0
--------------------------------------------------------------------
x86:
--------------------------------------------------------------------
Testcase Result Summary:
total: 8906
passed: 8906
failed: 0
timeout: 0
--------------------------------------------------------------------
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.49 release. There are 6 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, 11 Jul 2021 13:14:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.49-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-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.
## Build
* kernel: 5.10.49-rc1
* git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
* git branch: linux-5.10.y
* git commit: 5b40bcb16853d5fa948446202f43ea3fbcc14f33
* git describe: v5.10.48-7-g5b40bcb16853
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10.48-7-g5b40bcb16853
## No regressions (compared to v5.10.48)
## No fixes (compared to v5.10.48)
## Test result summary
total: 80634, pass: 65802, fail: 2163, skip: 11403, xfail: 1266,
## Build Summary
* arc: 10 total, 10 passed, 0 failed
* arm: 193 total, 193 passed, 0 failed
* arm64: 27 total, 27 passed, 0 failed
* dragonboard-410c: 1 total, 1 passed, 0 failed
* hi6220-hikey: 1 total, 1 passed, 0 failed
* i386: 26 total, 26 passed, 0 failed
* juno-r2: 1 total, 1 passed, 0 failed
* mips: 45 total, 45 passed, 0 failed
* parisc: 9 total, 9 passed, 0 failed
* powerpc: 27 total, 27 passed, 0 failed
* riscv: 21 total, 21 passed, 0 failed
* s390: 18 total, 18 passed, 0 failed
* sh: 18 total, 18 passed, 0 failed
* sparc: 9 total, 9 passed, 0 failed
* x15: 1 total, 1 passed, 0 failed
* x86: 1 total, 1 passed, 0 failed
* x86_64: 27 total, 27 passed, 0 failed
## Test suites summary
* fwts
* igt-gpu-tools
* install-android-platform-tools-r2600
* kselftest-
* kselftest-android
* kselftest-bpf
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers
* 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-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-vm
* kselftest-vsyscall-mode-native-
* kselftest-vsyscall-mode-none-
* 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
--
Linaro LKFT
https://lkft.linaro.org
Hi Greg,
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.49 release. There are 6 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, 11 Jul 2021 13:14:09 +0000. Anything received after that time might be too late.
Build test:
mips (gcc version 11.1.1 20210702): 63 configs -> no failure arm (gcc version 11.1.1 20210702): 105 configs -> no new failure arm64 (gcc version 11.1.1 20210702): 3 configs -> no failure x86_64 (gcc version 10.2.1 20210110): 2 configs -> no failure
Boot test:x86_64: Booted on my test laptop. No regression.x86_64: Booted on qemu. No regression.
arm64: Booted on rpi4b (4GB model). No regression.
--
Regards
Sudip
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.49 release. There are 6 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, 11 Jul 2021 13:14:09 +0000. Anything received after that time might be too late.
Build results:
total: 159 pass: 159 fail: 0 Qemu test results: total: 455 pass: 455 fail: 0
Guenter
Hi!
Quoted 4 lines
This is the start of the stable review cycle for the 5.10.49 release. There are 6 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
Best regards,
Pavel
Signature · 2 lines
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.49 release. There are 6 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, 11 Jul 2021 13:14:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.49-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-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:
--
Florian