This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +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.15.55-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y and the diffstat can be found below.
thanks,
greg k-h
------------- Pseudo-Shortlog of commits:
Greg Kroah-Hartman gregkh@linuxfoundation.org Linux 5.15.55-rc1
Thomas Gleixner tglx@linutronix.de x86/static_call: Serialize __static_call_fixup() properly
Pawan Gupta pawan.kumar.gupta@linux.intel.com x86/speculation: Disable RRSBA behavior
Konrad Rzeszutek Wilk konrad.wilk@oracle.com x86/kexec: Disable RET on kexec
Thadeu Lima de Souza Cascardo cascardo@canonical.com x86/bugs: Do not enable IBPB-on-entry when IBPB is not supported
Peter Zijlstra peterz@infradead.org x86/entry: Move PUSH_AND_CLEAR_REGS() back into error_entry
Pawan Gupta pawan.kumar.gupta@linux.intel.com x86/bugs: Add Cannon lake to RETBleed affected CPU list
Peter Zijlstra peterz@infradead.org x86/retbleed: Add fine grained Kconfig knobs
Andrew Cooper andrew.cooper3@citrix.com x86/cpu/amd: Enumerate BTC_NO
Peter Zijlstra peterz@infradead.org x86/common: Stamp out the stepping madness
Josh Poimboeuf jpoimboe@kernel.org x86/speculation: Fill RSB on vmexit for IBRS
Josh Poimboeuf jpoimboe@kernel.org KVM: VMX: Fix IBRS handling after vmexit
Josh Poimboeuf jpoimboe@kernel.org KVM: VMX: Prevent guest RSB poisoning attacks with eIBRS
Josh Poimboeuf jpoimboe@kernel.org KVM: VMX: Convert launched argument to flags
Josh Poimboeuf jpoimboe@kernel.org KVM: VMX: Flatten __vmx_vcpu_run()
Josh Poimboeuf jpoimboe@kernel.org objtool: Re-add UNWIND_HINT_{SAVE_RESTORE}
Josh Poimboeuf jpoimboe@kernel.org x86/speculation: Remove x86_spec_ctrl_mask
Josh Poimboeuf jpoimboe@kernel.org x86/speculation: Use cached host SPEC_CTRL value for guest entry/exit
Josh Poimboeuf jpoimboe@kernel.org x86/speculation: Fix SPEC_CTRL write on SMT state change
Josh Poimboeuf jpoimboe@kernel.org x86/speculation: Fix firmware entry SPEC_CTRL handling
Josh Poimboeuf jpoimboe@kernel.org x86/speculation: Fix RSB filling with CONFIG_RETPOLINE=n
Peter Zijlstra peterz@infradead.org x86/cpu/amd: Add Spectral Chicken
Peter Zijlstra peterz@infradead.org objtool: Add entry UNRET validation
Josh Poimboeuf jpoimboe@kernel.org x86/bugs: Do IBPB fallback check only once
Peter Zijlstra peterz@infradead.org x86/bugs: Add retbleed=ibpb
Peter Zijlstra peterz@infradead.org x86/xen: Add UNTRAIN_RET
Peter Zijlstra peterz@infradead.org x86/xen: Rename SYS* entry points
Peter Zijlstra peterz@infradead.org objtool: Update Retpoline validation
Peter Zijlstra peterz@infradead.org intel_idle: Disable IBRS during long idle
Peter Zijlstra peterz@infradead.org x86/bugs: Report Intel retbleed vulnerability
Peter Zijlstra peterz@infradead.org x86/bugs: Split spectre_v2_select_mitigation() and spectre_v2_user_select_mitigation()
Pawan Gupta pawan.kumar.gupta@linux.intel.com x86/speculation: Add spectre_v2=ibrs option to support Kernel IBRS
Peter Zijlstra peterz@infradead.org x86/bugs: Optimize SPEC_CTRL MSR writes
Thadeu Lima de Souza Cascardo cascardo@canonical.com x86/entry: Add kernel IBRS implementation
Peter Zijlstra peterz@infradead.org x86/bugs: Keep a per-CPU IA32_SPEC_CTRL value
Kim Phillips kim.phillips@amd.com x86/bugs: Enable STIBP for JMP2RET
Alexandre Chartre alexandre.chartre@oracle.com x86/bugs: Add AMD retbleed= boot parameter
Alexandre Chartre alexandre.chartre@oracle.com x86/bugs: Report AMD retbleed vulnerability
Peter Zijlstra peterz@infradead.org x86: Add magic AMD return-thunk
Peter Zijlstra peterz@infradead.org objtool: Treat .text.__x86.* as noinstr
Peter Zijlstra peterz@infradead.org x86/entry: Avoid very early RET
Peter Zijlstra peterz@infradead.org x86: Use return-thunk in asm code
Kim Phillips kim.phillips@amd.com x86/sev: Avoid using __x86_return_thunk
Peter Zijlstra peterz@infradead.org x86/vsyscall_emu/64: Don't use RET in vsyscall emulation
Peter Zijlstra peterz@infradead.org x86/kvm: Fix SETcc emulation for return thunks
Peter Zijlstra peterz@infradead.org x86/bpf: Use alternative RET encoding
Peter Zijlstra peterz@infradead.org x86/ftrace: Use alternative RET encoding
Peter Zijlstra peterz@infradead.org x86,static_call: Use alternative RET encoding
Thadeu Lima de Souza Cascardo cascardo@canonical.com objtool: skip non-text sections when adding return-thunk sites
Peter Zijlstra peterz@infradead.org x86,objtool: Create .return_sites
Peter Zijlstra peterz@infradead.org x86: Undo return-thunk damage
Peter Zijlstra peterz@infradead.org x86/retpoline: Use -mfunction-return
Peter Zijlstra peterz@infradead.org x86/retpoline: Swizzle retpoline thunk
Peter Zijlstra peterz@infradead.org x86/retpoline: Cleanup some #ifdefery
Peter Zijlstra peterz@infradead.org x86/cpufeatures: Move RETPOLINE flags to word 11
Peter Zijlstra peterz@infradead.org x86/kvm/vmx: Make noinstr clean
Thadeu Lima de Souza Cascardo cascardo@canonical.com x86/realmode: build with -D__DISABLE_EXPORTS
Peter Zijlstra peterz@infradead.org x86/entry: Remove skip_r11rcx
Peter Zijlstra peterz@infradead.org objtool: Default ignore INT3 for unreachable
Peter Zijlstra peterz@infradead.org bpf,x86: Respect X86_FEATURE_RETPOLINE*
Peter Zijlstra peterz@infradead.org bpf,x86: Simplify computing label offsets
Peter Zijlstra peterz@infradead.org x86/alternative: Add debug prints to apply_retpolines()
Peter Zijlstra peterz@infradead.org x86/alternative: Try inline spectre_v2=retpoline,amd
Peter Zijlstra peterz@infradead.org x86/alternative: Handle Jcc __x86_indirect_thunk_\reg
Peter Zijlstra peterz@infradead.org x86/alternative: Implement .retpoline_sites support
Peter Zijlstra peterz@infradead.org x86/retpoline: Create a retpoline thunk array
Peter Zijlstra peterz@infradead.org x86/retpoline: Move the retpoline thunk declarations to nospec-branch.h
Peter Zijlstra peterz@infradead.org x86/asm: Fixup odd GEN-for-each-reg.h usage
Peter Zijlstra peterz@infradead.org x86/asm: Fix register order
Peter Zijlstra peterz@infradead.org x86/retpoline: Remove unused replacement symbols
Peter Zijlstra peterz@infradead.org objtool: Introduce CFI hash
Peter Zijlstra peterz@infradead.org objtool,x86: Replace alternatives with .retpoline_sites
Peter Zijlstra peterz@infradead.org objtool: Shrink struct instruction
Peter Zijlstra peterz@infradead.org objtool: Explicitly avoid self modifying code in .altinstr_replacement
Peter Zijlstra peterz@infradead.org objtool: Classify symbols
Lai Jiangshan jiangshan.ljs@antgroup.com x86/entry: Don't call error_entry() for XENPV
Lai Jiangshan jiangshan.ljs@antgroup.com x86/entry: Move PUSH_AND_CLEAR_REGS out of error_entry()
Lai Jiangshan jiangshan.ljs@antgroup.com x86/entry: Switch the stack after error_entry() returns
Lai Jiangshan jiangshan.ljs@antgroup.com x86/traps: Use pt_regs directly in fixup_bad_iret()
-------------
Diffstat:
Documentation/admin-guide/kernel-parameters.txt | 25 + Makefile | 10 +- arch/um/kernel/um_arch.c | 4 + arch/x86/Kconfig | 103 +++- arch/x86/Makefile | 2 +- arch/x86/entry/Makefile | 2 +- arch/x86/entry/calling.h | 72 ++- arch/x86/entry/entry.S | 22 + arch/x86/entry/entry_32.S | 2 - arch/x86/entry/entry_64.S | 88 ++- arch/x86/entry/entry_64_compat.S | 21 +- arch/x86/entry/vdso/Makefile | 1 + arch/x86/entry/vsyscall/vsyscall_emu_64.S | 9 +- arch/x86/include/asm/GEN-for-each-reg.h | 14 +- arch/x86/include/asm/alternative.h | 2 + arch/x86/include/asm/asm-prototypes.h | 18 - arch/x86/include/asm/cpufeatures.h | 12 +- arch/x86/include/asm/disabled-features.h | 21 +- arch/x86/include/asm/linkage.h | 8 + arch/x86/include/asm/msr-index.h | 13 + arch/x86/include/asm/nospec-branch.h | 133 ++--- arch/x86/include/asm/static_call.h | 17 + arch/x86/include/asm/traps.h | 2 +- arch/x86/include/asm/unwind_hints.h | 14 +- arch/x86/kernel/alternative.c | 260 ++++++++- arch/x86/kernel/cpu/amd.c | 46 +- arch/x86/kernel/cpu/bugs.c | 475 +++++++++++++--- arch/x86/kernel/cpu/common.c | 61 ++- arch/x86/kernel/cpu/cpu.h | 2 + arch/x86/kernel/cpu/hygon.c | 6 + arch/x86/kernel/cpu/scattered.c | 1 + arch/x86/kernel/ftrace.c | 7 +- arch/x86/kernel/head_64.S | 5 + arch/x86/kernel/module.c | 15 +- arch/x86/kernel/process.c | 2 +- arch/x86/kernel/relocate_kernel_32.S | 25 +- arch/x86/kernel/relocate_kernel_64.S | 23 +- arch/x86/kernel/static_call.c | 49 +- arch/x86/kernel/traps.c | 19 +- arch/x86/kernel/vmlinux.lds.S | 23 +- arch/x86/kvm/emulate.c | 26 +- arch/x86/kvm/svm/vmenter.S | 18 + arch/x86/kvm/vmx/nested.c | 2 +- arch/x86/kvm/vmx/run_flags.h | 8 + arch/x86/kvm/vmx/vmenter.S | 164 +++--- arch/x86/kvm/vmx/vmx.c | 76 ++- arch/x86/kvm/vmx/vmx.h | 6 +- arch/x86/kvm/x86.c | 4 +- arch/x86/lib/memmove_64.S | 7 +- arch/x86/lib/retpoline.S | 133 +++-- arch/x86/mm/mem_encrypt_boot.S | 10 +- arch/x86/net/bpf_jit_comp.c | 179 +++--- arch/x86/net/bpf_jit_comp32.c | 22 +- arch/x86/xen/setup.c | 6 +- arch/x86/xen/xen-asm.S | 30 +- arch/x86/xen/xen-head.S | 1 + arch/x86/xen/xen-ops.h | 6 +- drivers/base/cpu.c | 8 + drivers/idle/intel_idle.c | 43 +- include/linux/cpu.h | 2 + include/linux/kvm_host.h | 2 +- include/linux/objtool.h | 9 +- scripts/Makefile.build | 1 + scripts/link-vmlinux.sh | 3 + security/Kconfig | 11 - tools/arch/x86/include/asm/msr-index.h | 9 + tools/include/linux/objtool.h | 9 +- tools/objtool/arch/x86/decode.c | 145 +---- tools/objtool/builtin-check.c | 4 +- tools/objtool/check.c | 701 ++++++++++++++++++++---- tools/objtool/elf.c | 84 --- tools/objtool/include/objtool/arch.h | 3 +- tools/objtool/include/objtool/builtin.h | 2 +- tools/objtool/include/objtool/cfi.h | 2 + tools/objtool/include/objtool/check.h | 10 +- tools/objtool/include/objtool/elf.h | 9 +- tools/objtool/include/objtool/objtool.h | 1 + tools/objtool/objtool.c | 1 + tools/objtool/orc_gen.c | 15 +- tools/objtool/special.c | 8 - 80 files changed, 2470 insertions(+), 944 deletions(-)
On 7/12/22 11:38, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +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.15.55-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.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 f.fainelli@gmail.com
On 7/12/22 12:38 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +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.15.55-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.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 skhan@linuxfoundation.org
thanks, -- Shuah
On Tue, Jul 12, 2022 at 08:38:30PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 12.1.0).
Tested-by: Bagas Sanjaya bagasdotme@gmail.com
On Tue, 12 Jul 2022 20:38:30 +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +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.15.55-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y and the diffstat can be found below.
thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v5.15: 10 builds: 10 pass, 0 fail 28 boots: 28 pass, 0 fail 114 tests: 114 pass, 0 fail
Linux version: 5.15.55-rc1-g0fe4fdf9b1da 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-a04
Tested-by: Jon Hunter jonathanh@nvidia.com
Jon
Hi Greg,
On Tue, Jul 12, 2022 at 08:38:30PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +0000. Anything received after that time might be too late.
Build test (gcc version 11.3.1 20220706): mips: 62 configs -> no failure arm: 99 configs -> no failure arm64: 3 configs -> no failure x86_64: 4 configs -> no failure alpha allmodconfig -> no failure csky allmodconfig -> no failure powerpc allmodconfig -> no failure riscv allmodconfig -> no failure s390 allmodconfig -> no failure xtensa allmodconfig -> 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] mips: Booted on ci20 board. No regression. [3]
[1]. https://openqa.qa.codethink.co.uk/tests/1508 [2]. https://openqa.qa.codethink.co.uk/tests/1511 [3]. https://openqa.qa.codethink.co.uk/tests/1514
Tested-by: Sudip Mukherjee sudip.mukherjee@codethink.co.uk
-- Regards Sudip
On Wed, 13 Jul 2022 at 00:17, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +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.15.55-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y and the diffstat can be found below.
thanks,
greg k-h
Results from Linaro’s test farm. Regressions on x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
1) Kernel panic noticed on device x86_6 while running kvm-unit-tests. - APIC base relocation is unsupported by KVM
2) while booting qemu-x86_64 the following warning noticed. - WARNING: CPU: 0 PID: 0 at arch/x86/kernel/alternative.c:557 apply_returns+0x19c/0x1d0
kernel panic log: - https://lkft.validation.linaro.org/scheduler/job/5278112#L1703 TESTNAME=emulator TIMEOUT=90s ACCEL= ./x86/run x86/emulator.flat -smp 1 [ 67.774572] APIC base relocation is unsupported by KVM [ 105.643057] kvm: emulating exchange as write [ 105.653717] int3: 0000 [#1] SMP PTI [ 105.653720] CPU: 3 PID: 3747 Comm: qemu-system-x86 Not tainted 5.15.55-rc1 #1 [ 105.653721] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.0b 07/27/2017 [ 105.653722] RIP: 0010:xaddw_ax_dx+0x9/0x10 [ 105.653727] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc cc cc 0f 1f 80 00 00 00 00 0f c0 d0 c3 cc cc cc cc 66 0f c1 d0 c3 cc cc cc cc <0f> 1f 80 00 00 00 00 0f c1 d0 c3 cc cc cc cc 48 0f c1 d0 c3 cc cc [ 105.653728] RSP: 0018:ffffb98bc5157ce8 EFLAGS: 00000206 [ 105.653729] RAX: 0000000089abcdef RBX: 0000000000000001 RCX: 0000000000000000 [ 105.653730] RDX: 0000000076543210 RSI: ffffffff8ea56000 RDI: 0000000000000204 [ 105.653731] RBP: ffffb98bc5157cf0 R08: ffffa306c6cf5df0 R09: 0000000000000002 [ 105.653732] R10: ffffa306c6cf5df0 R11: 0000000000000000 R12: ffffa306c6cf5df0 [ 105.653733] R13: ffffffff900090c0 R14: 0000000000000000 R15: 0000000000000000 [ 105.653734] FS: 00007f30ab0df700(0000) GS:ffffa30a1fd80000(0000) knlGS:0000000000000000 [ 105.653735] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 105.653736] CR2: 0000000000000000 CR3: 000000014e0d0003 CR4: 00000000003726e0 [ 105.653736] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 105.653737] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 105.653738] Call Trace: [ 105.653738] <TASK> [ 105.653739] ? fastop+0x5d/0xa0 [ 105.653741] x86_emulate_insn+0x7c9/0xf20 [ 105.653743] x86_emulate_instruction+0x2e3/0x790 [ 105.653746] complete_emulated_mmio+0x238/0x310 [ 105.653748] kvm_arch_vcpu_ioctl_run+0x11ba/0x1a70 [ 105.653750] ? vfs_writev+0xcb/0x140 [ 105.653753] kvm_vcpu_ioctl+0x281/0x6b0 [ 105.653755] ? clockevents_program_event+0x98/0x100 [ 105.653757] ? selinux_file_ioctl+0xae/0x140 [ 105.653760] ? selinux_file_ioctl+0xae/0x140 [ 105.653762] __x64_sys_ioctl+0x95/0xd0 [ 105.653764] do_syscall_64+0x3b/0x90 [ 105.653767] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 105.653769] RIP: 0033:0x7f30aca698f7 [ 105.653770] Code: b3 66 90 48 8b 05 a1 35 2c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 71 35 2c 00 f7 d8 64 89 01 48 [ 105.653771] RSP: 002b:00007f30ab0dea28 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 105.653772] RAX: ffffffffffffffda RBX: 000000000000ae80 RCX: 00007f30aca698f7 [ 105.653773] RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000000f [ 105.653774] RBP: 000055fb7fb6faf0 R08: 000055fb7d67c450 R09: 00000000ffffffff [ 105.653775] R10: 00000000000216a8 R11: 0000000000000246 R12: 0000000000000000 [ 105.653775] R13: 00007f30aed99000 R14: 0000000000000006 R15: 000055fb7fb6faf0 [ 105.653776] </TASK> [ 105.653777] Modules linked in: x86_pkg_temp_thermal [ 105.902123] ---[ end trace cec99cae36bcbfd7 ]--- [ 105.902124] RIP: 0010:xaddw_ax_dx+0x9/0x10 [ 105.902126] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc cc cc 0f 1f 80 00 00 00 00 0f c0 d0 c3 cc cc cc cc 66 0f c1 d0 c3 cc cc cc cc <0f> 1f 80 00 00 00 00 0f c1 d0 c3 cc cc cc cc 48 0f c1 d0 c3 cc cc [ 105.902127] RSP: 0018:ffffb98bc5157ce8 EFLAGS: 00000206 [ 105.902127] RAX: 0000000089abcdef RBX: 0000000000000001 RCX: 0000000000000000 [ 105.902128] RDX: 0000000076543210 RSI: ffffffff8ea56000 RDI: 0000000000000204 [ 105.902129] RBP: ffffb98bc5157cf0 R08: ffffa306c6cf5df0 R09: 0000000000000002 [ 105.902129] R10: ffffa306c6cf5df0 R11: 0000000000000000 R12: ffffa306c6cf5df0 [ 105.902130] R13: ffffffff900090c0 R14: 0000000000000000 R15: 0000000000000000 [ 105.902130] FS: 00007f30ab0df700(0000) GS:ffffa30a1fd80000(0000) knlGS:0000000000000000 [ 105.902131] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 105.902132] CR2: 0000000000000000 CR3: 000000014e0d0003 CR4: 00000000003726e0 [ 105.902133] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 105.902133] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 105.902134] Kernel panic - not syncing: Fatal exception in interrupt [ 105.902170] Kernel Offset: 0xda00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 106.022663] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- [ 106.030224] ------------[ cut here ]------------ [ 106.030224] sched: Unexpected reschedule of offline CPU#0! [ 106.030226] WARNING: CPU: 3 PID: 3747 at arch/x86/kernel/apic/ipi.c:68 native_smp_send_reschedule+0x3e/0x50 [ 106.030229] Modules linked in: x86_pkg_temp_thermal [ 106.030230] CPU: 3 PID: 3747 Comm: qemu-system-x86 Tainted: G D 5.15.55-rc1 #1 [ 106.030231] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.0b 07/27/2017 [ 106.030232] RIP: 0010:native_smp_send_reschedule+0x3e/0x50 [ 106.030234] Code: 1b 48 8b 05 d4 70 a6 01 be fd 00 00 00 48 8b 40 30 e8 66 dc 31 01 5d c3 cc cc cc cc 89 fe 48 c7 c7 a0 e9 41 90 e8 1e c3 ea 00 <0f> 0b 5d c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 [ 106.030234] RSP: 0018:ffffb98bc0160c60 EFLAGS: 00010086 [ 106.030235] RAX: 0000000000000000 RBX: ffffa30a1fc29b00 RCX: 0000000000000027 [ 106.030236] RDX: ffffa30a1fd9b4b8 RSI: 0000000000000001 RDI: ffffa30a1fd9b4b0 [ 106.030237] RBP: ffffb98bc0160c60 R08: ffffffff90b65665 R09: 0000000000000000 [ 106.030237] R10: 0000000000000030 R11: ffffffff90b65665 R12: ffffa306c097c100 [ 106.030238] R13: ffffb98bc0160d00 R14: ffffb98bc0160d00 R15: 0000000000000009 [ 106.030239] FS: 00007f30ab0df700(0000) GS:ffffa30a1fd80000(0000) knlGS:0000000000000000 [ 106.030239] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 106.030240] CR2: 0000000000000000 CR3: 000000014e0d0003 CR4: 00000000003726e0 [ 106.030241] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 106.030241] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 106.030242] Call Trace: [ 106.030242] <IRQ> [ 106.030243] resched_curr+0x52/0xb0 [ 106.030245] check_preempt_curr+0x3b/0x70 [ 106.030247] ttwu_do_wakeup+0x1c/0x160 [ 106.030249] ttwu_do_activate+0x94/0x190 [ 106.030251] try_to_wake_up+0x1c4/0x480 [ 106.030253] default_wake_function+0x1a/0x40 [ 106.030254] autoremove_wake_function+0x12/0x40 [ 106.030256] __wake_up_common+0x7d/0x140 [ 106.030258] __wake_up_common_lock+0x7c/0xc0 [ 106.030261] __wake_up+0x13/0x20 [ 106.030263] wake_up_klogd_work_func+0x7b/0x90 [ 106.030265] irq_work_single+0x46/0x80 [ 106.030267] irq_work_run_list+0x2a/0x40 [ 106.030269] irq_work_tick+0x3b/0x50 [ 106.030270] update_process_times+0xba/0xd0 [ 106.030272] tick_sched_handle+0x38/0x50 [ 106.030274] tick_sched_timer+0x8c/0xc0 [ 106.030276] ? can_stop_idle_tick+0xa0/0xa0 [ 106.030278] __hrtimer_run_queues+0xa6/0x2b0 [ 106.030280] hrtimer_interrupt+0x101/0x220 [ 106.030281] __sysvec_apic_timer_interrupt+0x61/0xe0 [ 106.030283] sysvec_apic_timer_interrupt+0x7b/0x90 [ 106.030285] </IRQ> [ 106.030285] <TASK> [ 106.030286] asm_sysvec_apic_timer_interrupt+0x1a/0x20 [ 106.030288] RIP: 0010:panic+0x277/0x2b6 [ 106.030290] Code: e8 65 ac 25 ff 48 c7 c6 80 04 b5 90 48 c7 c7 80 3f 42 90 e8 6a 58 00 00 c7 05 cc 8e f5 00 01 00 00 00 e8 d3 80 33 ff fb 31 db <4c> 39 eb 7c 1d 41 83 f4 01 48 8b 05 a0 d2 1b 01 44 89 e7 e8 18 16 [ 106.030291] RSP: 0018:ffffb98bc5157b10 EFLAGS: 00000246 [ 106.030292] RAX: ffffb98bc5157b80 RBX: 0000000000000000 RCX: 0000000000000027 [ 106.030292] RDX: 0000000000000000 RSI: ffffffff8f98de8f RDI: ffffffff8f99314d [ 106.030293] RBP: ffffb98bc5157b80 R08: ffffffff90b655fa R09: 0000000090b655d6 [ 106.030293] R10: ffffffffffffffff R11: ffffffffffffffff R12: 0000000000000000 [ 106.030294] R13: 0000000000000000 R14: ffffffff904131e0 R15: 0000000000000000 [ 106.030295] ? oops_end.cold+0xc/0x18 [ 106.030297] ? panic+0x274/0x2b6 [ 106.030299] oops_end.cold+0xc/0x18 [ 106.030300] die+0x43/0x60 [ 106.030302] exc_int3+0x137/0x160 [ 106.030303] asm_exc_int3+0x39/0x40 [ 106.030305] RIP: 0010:xaddw_ax_dx+0x9/0x10 [ 106.030307] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc cc cc 0f 1f 80 00 00 00 00 0f c0 d0 c3 cc cc cc cc 66 0f c1 d0 c3 cc cc cc cc <0f> 1f 80 00 00 00 00 0f c1 d0 c3 cc cc cc cc 48 0f c1 d0 c3 cc cc [ 106.030308] RSP: 0018:ffffb98bc5157ce8 EFLAGS: 00000206 [ 106.030308] RAX: 0000000089abcdef RBX: 0000000000000001 RCX: 0000000000000000 [ 106.030309] RDX: 0000000076543210 RSI: ffffffff8ea56000 RDI: 0000000000000204 [ 106.030310] RBP: ffffb98bc5157cf0 R08: ffffa306c6cf5df0 R09: 0000000000000002 [ 106.030310] R10: ffffa306c6cf5df0 R11: 0000000000000000 R12: ffffa306c6cf5df0 [ 106.030311] R13: ffffffff900090c0 R14: 0000000000000000 R15: 0000000000000000 [ 106.030312] ? xaddw_ax_dx+0x8/0x10 [ 106.030314] ? xaddw_ax_dx+0x9/0x10 [ 106.030315] ? xaddw_ax_dx+0x8/0x10 [ 106.030317] ? fastop+0x5d/0xa0 [ 106.030319] x86_emulate_insn+0x7c9/0xf20 [ 106.030321] x86_emulate_instruction+0x2e3/0x790 [ 106.030323] complete_emulated_mmio+0x238/0x310 [ 106.030325] kvm_arch_vcpu_ioctl_run+0x11ba/0x1a70 [ 106.030327] ? vfs_writev+0xcb/0x140 [ 106.030330] kvm_vcpu_ioctl+0x281/0x6b0 [ 106.030331] ? clockevents_program_event+0x98/0x100 [ 106.030333] ? selinux_file_ioctl+0xae/0x140 [ 106.030335] ? selinux_file_ioctl+0xae/0x140 [ 106.030337] __x64_sys_ioctl+0x95/0xd0 [ 106.030339] do_syscall_64+0x3b/0x90 [ 106.030340] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 106.030342] RIP: 0033:0x7f30aca698f7 [ 106.030343] Code: b3 66 90 48 8b 05 a1 35 2c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 71 35 2c 00 f7 d8 64 89 01 48 [ 106.030343] RSP: 002b:00007f30ab0dea28 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 106.030344] RAX: ffffffffffffffda RBX: 000000000000ae80 RCX: 00007f30aca698f7 [ 106.030345] RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000000f [ 106.030346] RBP: 000055fb7fb6faf0 R08: 000055fb7d67c450 R09: 00000000ffffffff [ 106.030346] R10: 00000000000216a8 R11: 0000000000000246 R12: 0000000000000000 [ 106.030347] R13: 00007f30aed99000 R14: 0000000000000006 R15: 000055fb7fb6faf0 [ 106.030348] </TASK> [ 106.030348] ---[ end trace cec99cae36bcbfd8 ]--- [ 106.030350] ------------[ cut here ]------------ [ 106.030350] sched: Unexpected reschedule of offline CPU#2! [ 106.030351] WARNING: CPU: 3 PID: 3747 at arch/x86/kernel/apic/ipi.c:68 native_smp_send_reschedule+0x3e/0x50 [ 106.030354] Modules linked in: x86_pkg_temp_thermal [ 106.030354] CPU: 3 PID: 3747 Comm: qemu-system-x86 Tainted: G D W 5.15.55-rc1 #1 [ 106.030355] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.0b 07/27/2017 [ 106.030356] RIP: 0010:native_smp_send_reschedule+0x3e/0x50 [ 106.030357] Code: 1b 48 8b 05 d4 70 a6 01 be fd 00 00 00 48 8b 40 30 e8 66 dc 31 01 5d c3 cc cc cc cc 89 fe 48 c7 c7 a0 e9 41 90 e8 1e c3 ea 00 <0f> 0b 5d c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 [ 106.030358] RSP: 0018:ffffb98bc0160b40 EFLAGS: 00010086 [ 106.030359] RAX: 0000000000000000 RBX: ffffa30a1fd29b00 RCX: 0000000000000027 [ 106.030360] RDX: ffffa30a1fd9b4b8 RSI: 0000000000000001 RDI: ffffa30a1fd9b4b0 [ 106.030360] RBP: ffffb98bc0160b40 R08: ffffffff90b66d1d R09: 0000000000000000 [ 106.030361] R10: 0000000000000030 R11: ffffffff90b66d1d R12: ffffa306c2216180 [ 106.030361] R13: ffffb98bc0160be0 R14: ffffb98bc0160be0 R15: 0000000000000009 [ 106.030362] FS: 00007f30ab0df700(0000) GS:ffffa30a1fd80000(0000) knlGS:0000000000000000 [ 106.030363] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 106.030364] CR2: 0000000000000000 CR3: 000000014e0d0003 CR4: 00000000003726e0 [ 106.030364] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 106.030365] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 106.030365] Call Trace: [ 106.030366] <IRQ> [ 106.030366] resched_curr+0x52/0xb0 [ 106.030368] check_preempt_curr+0x3b/0x70 [ 106.030369] ttwu_do_wakeup+0x1c/0x160 [ 106.030371] ttwu_do_activate+0x94/0x190 [ 106.030373] try_to_wake_up+0x1c4/0x480 [ 106.030375] default_wake_function+0x1a/0x40 [ 106.030377] autoremove_wake_function+0x12/0x40 [ 106.030378] __wake_up_common+0x7d/0x140 [ 106.030380] __wake_up_common_lock+0x7c/0xc0 [ 106.030382] __wake_up+0x13/0x20 [ 106.030384] ep_poll_callback+0x10e/0x290 [ 106.030386] __wake_up_common+0x7d/0x140 [ 106.030389] __wake_up_common_lock+0x7c/0xc0 [ 106.030391] __wake_up+0x13/0x20 [ 106.030393] wake_up_klogd_work_func+0x7b/0x90 [ 106.030395] irq_work_single+0x46/0x80 [ 106.030397] irq_work_run_list+0x2a/0x40 [ 106.030398] irq_work_tick+0x3b/0x50 [ 106.030400] update_process_times+0xba/0xd0 [ 106.030401] tick_sched_handle+0x38/0x50 [ 106.030403] tick_sched_timer+0x8c/0xc0 [ 106.030405] ? can_stop_idle_tick+0xa0/0xa0 [ 106.030407] __hrtimer_run_queues+0xa6/0x2b0 [ 106.030408] hrtimer_interrupt+0x101/0x220 [ 106.030410] __sysvec_apic_timer_interrupt+0x61/0xe0 [ 106.030411] sysvec_apic_timer_interrupt+0x7b/0x90 [ 106.030413] </IRQ> [ 106.030413] <TASK> [ 106.030414] asm_sysvec_apic_timer_interrupt+0x1a/0x20 [ 106.030416] RIP: 0010:panic+0x277/0x2b6 [ 106.030417] Code: e8 65 ac 25 ff 48 c7 c6 80 04 b5 90 48 c7 c7 80 3f 42 90 e8 6a 58 00 00 c7 05 cc 8e f5 00 01 00 00 00 e8 d3 80 33 ff fb 31 db <4c> 39 eb 7c 1d 41 83 f4 01 48 8b 05 a0 d2 1b 01 44 89 e7 e8 18 16 [ 106.030418] RSP: 0018:ffffb98bc5157b10 EFLAGS: 00000246 [ 106.030419] RAX: ffffb98bc5157b80 RBX: 0000000000000000 RCX: 0000000000000027 [ 106.030419] RDX: 0000000000000000 RSI: ffffffff8f98de8f RDI: ffffffff8f99314d [ 106.030420] RBP: ffffb98bc5157b80 R08: ffffffff90b655fa R09: 0000000090b655d6 [ 106.030420] R10: ffffffffffffffff R11: ffffffffffffffff R12: 0000000000000000 [ 106.030421] R13: 0000000000000000 R14: ffffffff904131e0 R15: 0000000000000000 [ 106.030422] ? oops_end.cold+0xc/0x18 [ 106.030423] ? panic+0x274/0x2b6 [ 106.030425] oops_end.cold+0xc/0x18 [ 106.030427] die+0x43/0x60 [ 106.030428] exc_int3+0x137/0x160 [ 106.030430] asm_exc_int3+0x39/0x40 [ 106.030431] RIP: 0010:xaddw_ax_dx+0x9/0x10 [ 106.030433] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc cc cc 0f 1f 80 00 00 00 00 0f c0 d0 c3 cc cc cc cc 66 0f c1 d0 c3 cc cc cc cc <0f> 1f 80 00 00 00 00 0f c1 d0 c3 cc cc cc cc 48 0f c1 d0 c3 cc cc [ 106.030434] RSP: 0018:ffffb98bc5157ce8 EFLAGS: 00000206 [ 106.030434] RAX: 0000000089abcdef RBX: 0000000000000001 RCX: 0000000000000000 [ 106.030435] RDX: 0000000076543210 RSI: ffffffff8ea56000 RDI: 0000000000000204 [ 106.030436] RBP: ffffb98bc5157cf0 R08: ffffa306c6cf5df0 R09: 0000000000000002 [ 106.030436] R10: ffffa306c6cf5df0 R11: 0000000000000000 R12: ffffa306c6cf5df0 [ 106.030437] R13: ffffffff900090c0 R14: 0000000000000000 R15: 0000000000000000 [ 106.030437] ? xaddw_ax_dx+0x8/0x10 [ 106.030439] ? xaddw_ax_dx+0x9/0x10 [ 106.030441] ? xaddw_ax_dx+0x8/0x10 [ 106.030443] ? fastop+0x5d/0xa0 [ 106.030445] x86_emulate_insn+0x7c9/0xf20 [ 106.030446] x86_emulate_instruction+0x2e3/0x790 [ 106.030449] complete_emulated_mmio+0x238/0x310 [ 106.030450] kvm_arch_vcpu_ioctl_run+0x11ba/0x1a70 [ 106.030453] ? vfs_writev+0xcb/0x140 [ 106.030455] kvm_vcpu_ioctl+0x281/0x6b0 [ 106.030456] ? clockevents_program_event+0x98/0x100 [ 106.030458] ? selinux_file_ioctl+0xae/0x140 [ 106.030460] ? selinux_file_ioctl+0xae/0x140 [ 106.030462] __x64_sys_ioctl+0x95/0xd0 [ 106.030464] do_syscall_64+0x3b/0x90 [ 106.030465] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 106.030467] RIP: 0033:0x7f30aca698f7 [ 106.030468] Code: b3 66 90 48 8b 05 a1 35 2c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 71 35 2c 00 f7 d8 64 89 01 48 [ 106.030468] RSP: 002b:00007f30ab0dea28 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 106.030469] RAX: ffffffffffffffda RBX: 000000000000ae80 RCX: 00007f30aca698f7 [ 106.030470] RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000000f [ 106.030470] RBP: 000055fb7fb6faf0 R08: 000055fb7d67c450 R09: 00000000ffffffff [ 106.030471] R10: 00000000000216a8 R11: 0000000000000246 R12: 0000000000000000 [ 106.030472] R13: 00007f30aed99000 R14: 0000000000000006 R15: 000055fb7fb6faf0 [ 106.030473] </TASK> [ 106.030473] ---[ end trace cec99cae36bcbfd9 ]---
2. Kernel warning - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.... <6>[ 0.571674] Speculative Store Bypass: Vulnerable <6>[ 0.573329] MDS: Vulnerable: Clear CPU buffers attempted, no microcode <4>[ 0.942716] ------------[ cut here ]------------ <4>[ 0.944263] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/alternative.c:557 apply_returns+0x19c/0x1d0 <4>[ 0.945106] Modules linked in: <4>[ 0.946322] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.55-rc1 #1 <4>[ 0.947052] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 <4>[ 0.947844] RIP: 0010:apply_returns+0x19c/0x1d0 <4>[ 0.948453] Code: 8d 7d c8 4c 89 75 c1 4c 89 74 08 f8 48 29 f8 8d 0c 02 4c 89 f0 c1 e9 03 f3 48 ab 8b 05 9d ba 52 02 85 c0 74 a0 e9 45 32 1a 01 <0f> 0b 48 83 c3 04 49 39 dd 0f 87 96 fe ff ff e9 0f ff ff ff c7 45 <4>[ 0.950059] RSP: 0000:ffffffff89803d78 EFLAGS: 00000206 <4>[ 0.950484] RAX: 0000000000000000 RBX: ffffffff89dbb174 RCX: 0000000000000000 <4>[ 0.951033] RDX: ffffffff891011b5 RSI: 00000000000000e9 RDI: ffffffff891011b0 <4>[ 0.951488] RBP: ffffffff89803e40 R08: 0000000000000000 R09: 0000000000000001 <4>[ 0.952032] R10: 0000000000000029 R11: 0000000000000000 R12: ffffffff891011b0 <4>[ 0.952488] R13: ffffffff89ddb184 R14: cccccccccccccccc R15: ffffffff891011b5 <4>[ 0.953125] FS: 0000000000000000(0000) GS:ffff90f63fc00000(0000) knlGS:0000000000000000 <4>[ 0.953634] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>[ 0.954031] CR2: ffff90f63fa01000 CR3: 000000003e826000 CR4: 00000000000006f0 <4>[ 0.954669] Call Trace: <4>[ 0.955846] <TASK> <4>[ 0.957183] alternative_instructions+0x7d/0x146 <4>[ 0.957673] check_bugs+0xf16/0xf57 <4>[ 0.958114] start_kernel+0x6b6/0x6ef <4>[ 0.958446] x86_64_start_reservations+0x24/0x2a <4>[ 0.958764] x86_64_start_kernel+0x8d/0x95 <4>[ 0.959035] secondary_startup_64_no_verify+0xc2/0xcb <4>[ 0.959591] </TASK> <4>[ 0.960146] irq event stamp: 121171 <4>[ 0.960419] hardirqs last enabled at (121179): [<ffffffff87a7247c>] __up_console_sem+0x5c/0x70 <4>[ 0.961036] hardirqs last disabled at (121188): [<ffffffff87a72461>] __up_console_sem+0x41/0x70 <4>[ 0.961577] softirqs last enabled at (1484): [<ffffffff87ad3f20>] cgroup_idr_alloc.constprop.0+0x60/0xe0 <4>[ 0.962031] softirqs last disabled at (1482): [<ffffffff87ad3ef3>] cgroup_idr_alloc.constprop.0+0x33/0xe0 <4>[ 0.963358] ---[ end trace 7af0f35d34a8be8b ]--- <6>[ 1.100332] Freeing SMP alternatives memory: 52K <6>[ 1.233988] smpboot: CPU0: Intel Core i7 9xx (Nehalem Class Core i7) (family: 0x6, model: 0x1a, stepping: 0x3) <6>[ 1.266761] Running RCU-tasks wait API self tests <6>[ 1.271070] Performance Events: unsupported p6 CPU model 26 no PMU driver, software events only. <6>[ 1.276776] rcu: Hierarchical SRCU implementation. <6>[ 1.281153] Callback from call_rcu_ta# sks_trace() invoked. <6>[ 1.308215] smp: Bringing up secondary CPUs ... <6>[ 1.322732] x86: Booting SMP configuration: <6>[ 1.323121] .... node #0, CPUs: #1 <6>[ 1.361239] smp: Brought up 1 node, 2 CPUs
## Build * kernel: 5.15.55-rc1 * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc * git branch: linux-5.15.y * git commit: 0fe4fdf9b1dac90e23465eefeff45e529adcf3c6 * git describe: v5.15.54-79-g0fe4fdf9b1da * test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15....
## Test Regressions (compared to v5.15.53-227-g71721f5974f2) kernel crash regression found.
## Metric Regressions (compared to v5.15.53-227-g71721f5974f2) No metric regressions found.
## Test Fixes (compared to v5.15.53-227-g71721f5974f2) No test fixes found.
## Metric Fixes (compared to v5.15.53-227-g71721f5974f2) No metric fixes found.
## Test result summary total: 137556, pass: 124337, fail: 404, skip: 12121, xfail: 694
## Build Summary * arc: 10 total, 10 passed, 0 failed * arm: 308 total, 308 passed, 0 failed * arm64: 62 total, 62 passed, 0 failed * i386: 52 total, 49 passed, 3 failed * mips: 48 total, 48 passed, 0 failed * parisc: 12 total, 12 passed, 0 failed * powerpc: 54 total, 52 passed, 2 failed * riscv: 22 total, 22 passed, 0 failed * s390: 21 total, 21 passed, 0 failed * sh: 24 total, 24 passed, 0 failed * sparc: 12 total, 12 passed, 0 failed * x86_64: 56 total, 55 passed, 1 failed
## Test suites summary * fwts * kunit * kvm-unit-tests * libgpiod * libhugetlbfs * log-parser-boot * log-parser-test * ltp-cap_bounds * ltp-commands * ltp-containers * ltp-controllers * ltp-cpuhotplug * ltp-crypto * ltp-cve * ltp-dio * ltp-fcntl-locktests * ltp-filecaps * ltp-fs * ltp-fs_bind * ltp-fs_perms_simple * ltp-fsx * ltp-hugetlb * ltp-io * ltp-ipc * ltp-math * ltp-mm * ltp-nptl * ltp-open-posix-tests * ltp-pty * ltp-sched * ltp-securebits * ltp-smoke * ltp-syscalls * ltp-tracing * network-basic-tests * packetdrill * perf * perf/Zstd-perf.data-compression * rcutorture * ssuite * v4l2-compliance * vdso
-- Linaro LKFT https://lkft.linaro.org
On 7/13/22 05:52, Naresh Kamboju wrote:
On Wed, 13 Jul 2022 at 00:17, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +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.15.55-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y and the diffstat can be found below.
thanks,
greg k-h
Results from Linaro’s test farm. Regressions on x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
- Kernel panic noticed on device x86_6 while running kvm-unit-tests.
- APIC base relocation is unsupported by KVM
Looking into the log, I don't think that message is related to the crash.
[ 67.774572] APIC base relocation is unsupported by KVM [ 105.643057] kvm: emulating exchange as write <--- warning [ 105.653717] int3: 0000 [#1] SMP PTI [ 105.653720] CPU: 3 PID: 3747 Comm: qemu-system-x86 Not tainted 5.15.55-rc1 #1 [ 105.653721] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.0b 07/27/2017 [ 105.653722] RIP: 0010:xaddw_ax_dx+0x9/0x10 ... [ 105.653777] Modules linked in: x86_pkg_temp_thermal [ 105.902123] ---[ end trace cec99cae36bcbfd7 ]--- [ 105.902124] RIP: 0010:xaddw_ax_dx+0x9/0x10 <--- crash [ 105.902126] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc
Guenter
On Wed, Jul 13, 2022 at 6:34 AM Guenter Roeck linux@roeck-us.net wrote:
Looking into the log, I don't think that message is related to the crash.
... [ 105.653777] Modules linked in: x86_pkg_temp_thermal [ 105.902123] ---[ end trace cec99cae36bcbfd7 ]--- [ 105.902124] RIP: 0010:xaddw_ax_dx+0x9/0x10 <--- crash [ 105.902126] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc
Yeah, the code you snipped, shows
20: 66 0f c1 d0 xadd %dx,%ax 24: c3 ret 25: cc int3 26: cc int3 27: cc int3 28: cc int3 29:* 0f 1f 80 00 00 00 00 nopl 0x0(%rax) <-- trapping instruction 30: 0f c1 d0 xadd %edx,%eax 33: c3 ret 34: cc int3 35: cc int3 36: cc int3 37: cc int3 38: 48 0f c1 d0 xadd %rdx,%rax 3c: c3 ret 3d: cc int3
and that's a bit odd.
It says "xaddw_ax_dx+0x9/0x10", but I think somebody jumped to "xaddw_ax_dx+8", hit the 'int3', and the RIP points to the next instruction (because that's how int3 works).
And the fastop code says:
* fastop functions have a special calling convention: ... * Moreover, they are all exactly FASTOP_SIZE bytes long,
but that is clearly *NOT* the case for xaddw_ax_dx, because it's 16 bytes in size, and the other ones are 8 bytes. That's where the "nopl" comes from: it's the alignment instruction to the next fastop function.
Compare that to the word-sized 'xaddl' case rigth afterwards: that one *is* just 8 bytes in size, so the 64-byte 'xaddq' comes 8 bytes aftrer it, and there's no 7-byte padding nop-instruction.
So I think that that is where the "xaddw_ax_dx+8" comes from: some code assumes that FASTOP_SIZE is 8, but that xaddw_ax_dx case was actually 9 bytes and thus got that "int3 + padding" in the next 8 bytes.
The whole kvm x86 emulation thiing is quite complicated and has lots of instruction size #defines and magic.
I'm not familiar enough with it to go "Ahh, it's obviously XYZ", but I'm sure PeterZ and Borislav know exactly what's going on.
Linus
On Wed, Jul 13, 2022 at 11:33 AM Linus Torvalds torvalds@linux-foundation.org wrote:
So I think that that is where the "xaddw_ax_dx+8" comes from: some code assumes that FASTOP_SIZE is 8, but that xaddw_ax_dx case was actually 9 bytes and thus got that "int3 + padding" in the next 8 bytes.
The whole kvm x86 emulation thing is quite complicated and has lots of instruction size #defines and magic.
I'm not familiar enough with it to go "Ahh, it's obviously XYZ", but I'm sure PeterZ and Borislav know exactly what's going on.
And I see that Thadeau already figured it out:
https://lore.kernel.org/all/20220713171241.184026-1-cascardo@canonical.com/
So presumably we need that patch everywhere.
Linus
On Wed, Jul 13, 2022 at 11:40:03AM -0700, Linus Torvalds wrote:
And I see that Thadeau already figured it out:
https://lore.kernel.org/all/20220713171241.184026-1-cascardo@canonical.com/
So presumably we need that patch everywhere.
Right, I've queued it along with other fallout fixes. Will do some testing before I send them to you on Sunday.
I'm guessing you're thinking of cutting an -rc7 so that people can test the whole retbleed mitigation disaster an additional week?
Thx.
On 7/14/22 11:01, Borislav Petkov wrote:
On Wed, Jul 13, 2022 at 11:40:03AM -0700, Linus Torvalds wrote:
And I see that Thadeau already figured it out:
https://lore.kernel.org/all/20220713171241.184026-1-cascardo@canonical.com/
So presumably we need that patch everywhere.
Right, I've queued it along with other fallout fixes. Will do some testing before I send them to you on Sunday.
I'm guessing you're thinking of cutting an -rc7 so that people can test the whole retbleed mitigation disaster an additional week?
Please leave that one out as Peter suggested a better fix and I have that queued for Linus.
(If you don't no big deal, the conflict will be very clear, but it will be a bit more work for everyone).
Paolo
On July 14, 2022 1:46:53 PM UTC, Paolo Bonzini pbonzini@redhat.com wrote:
Please leave that one out as Peter suggested a better fix and I have that queued for Linus.
Already zapped.
Thx.
On Thu, Jul 14, 2022 at 7:46 AM Boris Petkov bp@alien8.de wrote:
On July 14, 2022 1:46:53 PM UTC, Paolo Bonzini pbonzini@redhat.com wrote:
Please leave that one out as Peter suggested a better fix and I have that queued for Linus.
Already zapped.
I like Peter's more obvious use of FASTYOP_LENGTH, but this is just disgusting:
#define FASTOP_SIZE (8 << ((FASTOP_LENGTH > 8) & 1) << ((FASTOP_LENGTH > 16) & 1))
I mean, I understand what it's doing, but just two lines above it the code has a "ilog2()" use that already depends on the fact that you can use ilog2() as a constant compile-time expression.
And guess what? The code could just use roundup_pow_of_two(), which is designed exactly like ilog2() to be used for compile-time constant values.
So the code should just use
#define FASTOP_SIZE roundup_pow_of_two(FASTOP_LENGTH)
and be a lot more legible, wouldn't it?
Because I don't think there is anything magical about the length "8/16/32". It's purely "aligned and big enough to contain FASTOP_LENGTH".
And then the point of that
static_assert(FASTOP_LENGTH <= FASTOP_SIZE);
just goes away, because there are no subtle math issues there any more.
In fact, the remaining question is just "where did the 7 come from" in
#define FASTOP_LENGTH (7 + ENDBR_INSN_SIZE + RET_LENGTH)
because other than that it all looks fairly straightforward.
Linus
On 7/14/22 19:02, Linus Torvalds wrote:
And guess what? The code could just use roundup_pow_of_two(), which is designed exactly like ilog2() to be used for compile-time constant values.
So the code should just use
#define FASTOP_SIZE roundup_pow_of_two(FASTOP_LENGTH)and be a lot more legible, wouldn't it?
Because I don't think there is anything magical about the length "8/16/32". It's purely "aligned and big enough to contain FASTOP_LENGTH".
roundup_pow_of_two unfortunately is not enough for stringizing FASTOP_SIZE into an asm statement. :(
#define __FOP_FUNC(name) \ ".align " __stringify(FASTOP_SIZE) " \n\t" \ ".type " name ", @function \n\t" \ name ":\n\t" \ ASM_ENDBR
The shifts are what we came up with for the SETCC thunks when ENDBR and SLS made them grew beyond 4 bytes; Peter's patch is reusing the trick for the fastop thunks.
Because I don't think there is anything magical about the length "8/16/32". It's purely "aligned and big enough to contain FASTOP_LENGTH".
I agree with that, it's only limited to 8/16/32 to keep the macro to a decent size.
And then the point of that
static_assert(FASTOP_LENGTH <= FASTOP_SIZE);just goes away, because there are no subtle math issues there any more.
In fact, the remaining question is just "where did the 7 come from" in
#define FASTOP_LENGTH (7 + ENDBR_INSN_SIZE + RET_LENGTH)
The 7 is an upper limit to the length of the code between endbr and ret. There's no particular reason to limit to 7, but it allows using an alignment of 8 in the smallest case (no thunks, no SLS, no endbr) where you just have ".align 8; ...; ret".
Paolo
On Thu, Jul 14, 2022 at 10:02:57AM -0700, Linus Torvalds wrote:
I like Peter's more obvious use of FASTYOP_LENGTH, but this is just disgusting:
#define FASTOP_SIZE (8 << ((FASTOP_LENGTH > 8) & 1) <<((FASTOP_LENGTH > 16) & 1))
I mean, I understand what it's doing, but just two lines above it the code has a "ilog2()" use that already depends on the fact that you can use ilog2() as a constant compile-time expression.
And guess what? The code could just use roundup_pow_of_two(), which is designed exactly like ilog2() to be used for compile-time constant values.
But NR_FASTOP isn't used in ASM.
So the code should just use
#define FASTOP_SIZE roundup_pow_of_two(FASTOP_LENGTH)and be a lot more legible, wouldn't it?
If only :/ FASTOP_SIZE is used in ASM, which means we've got to play by GNU-as rules, and them are aweful.
On Thu, Jul 14, 2022 at 10:22 AM Peter Zijlstra peterz@infradead.org wrote:
If only :/ FASTOP_SIZE is used in ASM, which means we've got to play by GNU-as rules, and they are awful.
Oh Gods. Yes they are.
Linus
Oh, btw, how bad would it be to just do
#define FASTOP_SIZE 16 static_assert(FASTOP_SIZE >= FASTOP_LENGTH)
and leave it at that?
Afaik both gcc and clang default to -falign-functions=16 *anyway*, and while on 32-bit x86 we have options to minimize alignment, we don't do that on x86-64 afaik.
In fact, we have an option to force *bigger* alignment (DEBUG_FORCE_FUNCTION_ALIGN_64B) but not any way to make it less.
And we use
.p2align 4
in most of our asm, aling with
#define __ALIGN .p2align 4, 0x90
So all the *normal* functions already get 16-byte alignment anyway.
So yeah, it would be less dense, but do we care? Wouldn't the "this is really simple" be a nice thing? It's not like there are a ton of those fastop functions anyway. 128 of them? Plus 16 of the "setCC" ones?
Linus
On July 14, 2022 6:16:40 PM UTC, Linus Torvalds torvalds@linux-foundation.org wrote:
So yeah, it would be less dense, but do we care? Wouldn't the "this is really simple" be a nice thing? It's not like there are a ton of those fastop functions anyway. 128 of them? Plus 16 of the "setCC" ones?
I definitely like simple.
Along with a comment why we have this magic 16 there.
On 7/14/22 20:16, Linus Torvalds wrote:
Oh, btw, how bad would it be to just do
#define FASTOP_SIZE 16 static_assert(FASTOP_SIZE >= FASTOP_LENGTH)
Yeah, for 32 I might have some (probably irrational) qualms, but 16 is not worth the trouble.
Given 3 bytes for ENDBR, 5 for the return thunk and 1 for the straight line speculation INT3, there are 7 bytes left and only 4 are currently used (for instructions encoded as "66 0f xx xx"). So FASTOP_SIZE at SETCC_ALIGN can indeed be 16 unconditionally.
Paolo
On Thu, Jul 14, 2022 at 2:02 AM Borislav Petkov bp@alien8.de wrote:
I'm guessing you're thinking of cutting an -rc7 so that people can test the whole retbleed mitigation disaster an additional week?
Oh, absolutely. Doing an -rc7 is normal.
Right now the question isn't whether an rc7 happens, but whether we'll need an rc8. We'll see.
Oh, I do hate the hw-embargoed stuff that doesn't get all the usual testing in all our automation.
Linus
On Thu, Jul 14, 2022 at 09:51:40AM -0700, Linus Torvalds wrote:
Oh, absolutely. Doing an -rc7 is normal.
Good. I'm gathering all the fallout fixes and will send them to you on Sunday, if nothing unexpected happens.
Right now the question isn't whether an rc7 happens, but whether we'll need an rc8. We'll see.
Right, we'll see what additional fallout happens next week. I'll try to Cc you on such reports so that you're aware.
Oh, I do hate the hw-embargoed stuff that doesn't get all the usual testing in all our automation.
Tell me about it.
Thx.
On Thu, Jul 14, 2022 at 10:02 AM Borislav Petkov bp@alien8.de wrote:
On Thu, Jul 14, 2022 at 09:51:40AM -0700, Linus Torvalds wrote:
Oh, absolutely. Doing an -rc7 is normal.
Good. I'm gathering all the fallout fixes and will send them to you on Sunday, if nothing unexpected happens.
Btw, I assume that includes the clang fix for the x86_spec_ctrl_current section attribute.
That's kind of personally embarrassing that it slipped through: I do all my normal test builds that I actually *boot* with clang.
But since I kept all of the embargoed stuff outside my normal trees, it also meant that the test builds I did didn't have my "this is my clang tree" stuff in it.
And so I - like apparently everybody else - only did those builds with gcc.
And gcc for some reason doesn't care about this whole "you redeclared that variable with a different attribute" thing.
And sadly, our percpu accessor functions don't verify these things either, so you can write code like this:
unsigned long myvariable;
unsigned long test_fn(void) { return this_cpu_read(myvariable); }
and the compiler will not complain about anything at all, and happily generate completely nonsensical code like
movq %gs:myvariable(%rip), %rax
for it, which will do entirely the wrong thing because 'myvariable' wasn't allocated in the percpu section.
In the 'x86_spec_ctrl_current' case, that nonsensical code _worked_ (with gcc), because despite the declaration being for a regular variable, the actual definition was in the proper segment.
But that 'myvariable' thing above does end up being another example of how we are clearly missing some type checkng in this area.
I'm not sure if there's any way to get that section mismatch at compile-time at all. For the static declarations, we could just make DECLARE_PER_CPU() add some prefix/postfix to the name (and obviously then do it at use time too).
We have that '__pcpu_scope_##name' thing to make sure of globally unique naming due to the whole weak type thing. I wonder if we could do something similar to verify that "yes, this has been declared as a percpu variable" at use time?
Linus
On Thu, Jul 14, 2022 at 01:39:25PM -0700, Linus Torvalds wrote:
On Thu, Jul 14, 2022 at 10:02 AM Borislav Petkov bp@alien8.de wrote:
On Thu, Jul 14, 2022 at 09:51:40AM -0700, Linus Torvalds wrote:
Oh, absolutely. Doing an -rc7 is normal.
Good. I'm gathering all the fallout fixes and will send them to you on Sunday, if nothing unexpected happens.
Btw, I assume that includes the clang fix for the x86_spec_ctrl_current section attribute.
Yap. Here's the current lineup:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/urgen...
That's kind of personally embarrassing that it slipped through: I do all my normal test builds that I actually *boot* with clang.
But since I kept all of the embargoed stuff outside my normal trees, it also meant that the test builds I did didn't have my "this is my clang tree" stuff in it.
And so I - like apparently everybody else - only did those builds with gcc.
And gcc for some reason doesn't care about this whole "you redeclared that variable with a different attribute" thing.
... so why does clang care? Or, why doesn't gcc care?
I guess I need to talk to gcc folks again.
In the 'x86_spec_ctrl_current' case, that nonsensical code _worked_ (with gcc), because despite the declaration being for a regular variable, the actual definition was in the proper segment.
I'm guessing this is the reason why gcc doesn't fail - it probably looks at the declaration but doesn't care too much about it. And it is the definition that matters.
While clang goes, uh, ah, declaration and definition mismatch, I better warn.
But that 'myvariable' thing above does end up being another example of how we are clearly missing some type checkng in this area.
I'm not sure if there's any way to get that section mismatch at compile-time at all.
Well, apparently, clang can:
arch/x86/kernel/cpu/bugs.c:58:21: error: section attribute is specified on redeclared variable [-Werror,-Wsection]
so there's a -Wsection warning which gcc could implement too.
For the static declarations, we could just make DECLARE_PER_CPU() add some prefix/postfix to the name (and obviously then do it at use time too).
We have that '__pcpu_scope_##name' thing to make sure of globally unique naming due to the whole weak type thing. I wonder if we could do something similar to verify that "yes, this has been declared as a percpu variable" at use time?
But how?
We need to save the info how a var has been declared and then use that info at access time.
Yeah, lemme bother compiler guys a bit...
On Wed, 2022-07-13 at 18:22 +0530, Naresh Kamboju wrote:
On Wed, 13 Jul 2022 at 00:17, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +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.15.55-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y and the diffstat can be found below.
thanks,
greg k-h
Results from Linaro’s test farm. Regressions on x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
- Kernel panic noticed on device x86_6 while running kvm-unit-tests.
- APIC base relocation is unsupported by KVM
My 0.2 cent:
APIC base relocation warning is harmless, and I removed it 5.19 kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h...
The 'emulating exchange as write' is also something that KVM unit tests trigger normally although this warning recently did signal a real and very nasty bug, which I fixed in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h...
FYI, Another 'pr_info_ratelimited' message from KVM that you will see when running the unit tests is this "kvm: vcpu 0: requested 2000 ns lapic timer period limited to 200000 ns"
It is also harmless, but I do wonder how much value it adds.
And the panic I guess was already figured out.
BTW, there is a script in the kernel source, called decode_stacktrace (./scripts/decode_stacktrace.sh)
It is very useful to figure out, on which source line the panic/oops was triggered, you might want to consider using it in the report.
(I do wish the kernel had a debug option, of 'I don't care about kernel addresses/info leaks', please print all the info you can in the stacktrace).
Best regards, Maxim Levitsky
- while booting qemu-x86_64 the following warning noticed.
- WARNING: CPU: 0 PID: 0 at arch/x86/kernel/alternative.c:557 apply_returns+0x19c/0x1d0
kernel panic log: - https://lkft.validation.linaro.org/scheduler/job/5278112#L1703 TESTNAME=emulator TIMEOUT=90s ACCEL= ./x86/run x86/emulator.flat -smp 1 [ 67.774572] APIC base relocation is unsupported by KVM [ 105.643057] kvm: emulating exchange as write [ 105.653717] int3: 0000 [#1] SMP PTI [ 105.653720] CPU: 3 PID: 3747 Comm: qemu-system-x86 Not tainted 5.15.55-rc1 #1 [ 105.653721] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.0b 07/27/2017 [ 105.653722] RIP: 0010:xaddw_ax_dx+0x9/0x10 [ 105.653727] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc cc cc 0f 1f 80 00 00 00 00 0f c0 d0 c3 cc cc cc cc 66 0f c1 d0 c3 cc cc cc cc <0f> 1f 80 00 00 00 00 0f c1 d0 c3 cc cc cc cc 48 0f c1 d0 c3 cc cc [ 105.653728] RSP: 0018:ffffb98bc5157ce8 EFLAGS: 00000206 [ 105.653729] RAX: 0000000089abcdef RBX: 0000000000000001 RCX: 0000000000000000 [ 105.653730] RDX: 0000000076543210 RSI: ffffffff8ea56000 RDI: 0000000000000204 [ 105.653731] RBP: ffffb98bc5157cf0 R08: ffffa306c6cf5df0 R09: 0000000000000002 [ 105.653732] R10: ffffa306c6cf5df0 R11: 0000000000000000 R12: ffffa306c6cf5df0 [ 105.653733] R13: ffffffff900090c0 R14: 0000000000000000 R15: 0000000000000000 [ 105.653734] FS: 00007f30ab0df700(0000) GS:ffffa30a1fd80000(0000) knlGS:0000000000000000 [ 105.653735] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 105.653736] CR2: 0000000000000000 CR3: 000000014e0d0003 CR4: 00000000003726e0 [ 105.653736] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 105.653737] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 105.653738] Call Trace: [ 105.653738] <TASK> [ 105.653739] ? fastop+0x5d/0xa0 [ 105.653741] x86_emulate_insn+0x7c9/0xf20 [ 105.653743] x86_emulate_instruction+0x2e3/0x790 [ 105.653746] complete_emulated_mmio+0x238/0x310 [ 105.653748] kvm_arch_vcpu_ioctl_run+0x11ba/0x1a70 [ 105.653750] ? vfs_writev+0xcb/0x140 [ 105.653753] kvm_vcpu_ioctl+0x281/0x6b0 [ 105.653755] ? clockevents_program_event+0x98/0x100 [ 105.653757] ? selinux_file_ioctl+0xae/0x140 [ 105.653760] ? selinux_file_ioctl+0xae/0x140 [ 105.653762] __x64_sys_ioctl+0x95/0xd0 [ 105.653764] do_syscall_64+0x3b/0x90 [ 105.653767] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 105.653769] RIP: 0033:0x7f30aca698f7 [ 105.653770] Code: b3 66 90 48 8b 05 a1 35 2c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 71 35 2c 00 f7 d8 64 89 01 48 [ 105.653771] RSP: 002b:00007f30ab0dea28 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 105.653772] RAX: ffffffffffffffda RBX: 000000000000ae80 RCX: 00007f30aca698f7 [ 105.653773] RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000000f [ 105.653774] RBP: 000055fb7fb6faf0 R08: 000055fb7d67c450 R09: 00000000ffffffff [ 105.653775] R10: 00000000000216a8 R11: 0000000000000246 R12: 0000000000000000 [ 105.653775] R13: 00007f30aed99000 R14: 0000000000000006 R15: 000055fb7fb6faf0 [ 105.653776] </TASK> [ 105.653777] Modules linked in: x86_pkg_temp_thermal [ 105.902123] ---[ end trace cec99cae36bcbfd7 ]--- [ 105.902124] RIP: 0010:xaddw_ax_dx+0x9/0x10 [ 105.902126] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc cc cc 0f 1f 80 00 00 00 00 0f c0 d0 c3 cc cc cc cc 66 0f c1 d0 c3 cc cc cc cc <0f> 1f 80 00 00 00 00 0f c1 d0 c3 cc cc cc cc 48 0f c1 d0 c3 cc cc [ 105.902127] RSP: 0018:ffffb98bc5157ce8 EFLAGS: 00000206 [ 105.902127] RAX: 0000000089abcdef RBX: 0000000000000001 RCX: 0000000000000000 [ 105.902128] RDX: 0000000076543210 RSI: ffffffff8ea56000 RDI: 0000000000000204 [ 105.902129] RBP: ffffb98bc5157cf0 R08: ffffa306c6cf5df0 R09: 0000000000000002 [ 105.902129] R10: ffffa306c6cf5df0 R11: 0000000000000000 R12: ffffa306c6cf5df0 [ 105.902130] R13: ffffffff900090c0 R14: 0000000000000000 R15: 0000000000000000 [ 105.902130] FS: 00007f30ab0df700(0000) GS:ffffa30a1fd80000(0000) knlGS:0000000000000000 [ 105.902131] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 105.902132] CR2: 0000000000000000 CR3: 000000014e0d0003 CR4: 00000000003726e0 [ 105.902133] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 105.902133] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 105.902134] Kernel panic - not syncing: Fatal exception in interrupt [ 105.902170] Kernel Offset: 0xda00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 106.022663] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- [ 106.030224] ------------[ cut here ]------------ [ 106.030224] sched: Unexpected reschedule of offline CPU#0! [ 106.030226] WARNING: CPU: 3 PID: 3747 at arch/x86/kernel/apic/ipi.c:68 native_smp_send_reschedule+0x3e/0x50 [ 106.030229] Modules linked in: x86_pkg_temp_thermal [ 106.030230] CPU: 3 PID: 3747 Comm: qemu-system-x86 Tainted: G D 5.15.55-rc1 #1 [ 106.030231] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.0b 07/27/2017 [ 106.030232] RIP: 0010:native_smp_send_reschedule+0x3e/0x50 [ 106.030234] Code: 1b 48 8b 05 d4 70 a6 01 be fd 00 00 00 48 8b 40 30 e8 66 dc 31 01 5d c3 cc cc cc cc 89 fe 48 c7 c7 a0 e9 41 90 e8 1e c3 ea 00 <0f> 0b 5d c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 [ 106.030234] RSP: 0018:ffffb98bc0160c60 EFLAGS: 00010086 [ 106.030235] RAX: 0000000000000000 RBX: ffffa30a1fc29b00 RCX: 0000000000000027 [ 106.030236] RDX: ffffa30a1fd9b4b8 RSI: 0000000000000001 RDI: ffffa30a1fd9b4b0 [ 106.030237] RBP: ffffb98bc0160c60 R08: ffffffff90b65665 R09: 0000000000000000 [ 106.030237] R10: 0000000000000030 R11: ffffffff90b65665 R12: ffffa306c097c100 [ 106.030238] R13: ffffb98bc0160d00 R14: ffffb98bc0160d00 R15: 0000000000000009 [ 106.030239] FS: 00007f30ab0df700(0000) GS:ffffa30a1fd80000(0000) knlGS:0000000000000000 [ 106.030239] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 106.030240] CR2: 0000000000000000 CR3: 000000014e0d0003 CR4: 00000000003726e0 [ 106.030241] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 106.030241] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 106.030242] Call Trace: [ 106.030242] <IRQ> [ 106.030243] resched_curr+0x52/0xb0 [ 106.030245] check_preempt_curr+0x3b/0x70 [ 106.030247] ttwu_do_wakeup+0x1c/0x160 [ 106.030249] ttwu_do_activate+0x94/0x190 [ 106.030251] try_to_wake_up+0x1c4/0x480 [ 106.030253] default_wake_function+0x1a/0x40 [ 106.030254] autoremove_wake_function+0x12/0x40 [ 106.030256] __wake_up_common+0x7d/0x140 [ 106.030258] __wake_up_common_lock+0x7c/0xc0 [ 106.030261] __wake_up+0x13/0x20 [ 106.030263] wake_up_klogd_work_func+0x7b/0x90 [ 106.030265] irq_work_single+0x46/0x80 [ 106.030267] irq_work_run_list+0x2a/0x40 [ 106.030269] irq_work_tick+0x3b/0x50 [ 106.030270] update_process_times+0xba/0xd0 [ 106.030272] tick_sched_handle+0x38/0x50 [ 106.030274] tick_sched_timer+0x8c/0xc0 [ 106.030276] ? can_stop_idle_tick+0xa0/0xa0 [ 106.030278] __hrtimer_run_queues+0xa6/0x2b0 [ 106.030280] hrtimer_interrupt+0x101/0x220 [ 106.030281] __sysvec_apic_timer_interrupt+0x61/0xe0 [ 106.030283] sysvec_apic_timer_interrupt+0x7b/0x90 [ 106.030285] </IRQ> [ 106.030285] <TASK> [ 106.030286] asm_sysvec_apic_timer_interrupt+0x1a/0x20 [ 106.030288] RIP: 0010:panic+0x277/0x2b6 [ 106.030290] Code: e8 65 ac 25 ff 48 c7 c6 80 04 b5 90 48 c7 c7 80 3f 42 90 e8 6a 58 00 00 c7 05 cc 8e f5 00 01 00 00 00 e8 d3 80 33 ff fb 31 db <4c> 39 eb 7c 1d 41 83 f4 01 48 8b 05 a0 d2 1b 01 44 89 e7 e8 18 16 [ 106.030291] RSP: 0018:ffffb98bc5157b10 EFLAGS: 00000246 [ 106.030292] RAX: ffffb98bc5157b80 RBX: 0000000000000000 RCX: 0000000000000027 [ 106.030292] RDX: 0000000000000000 RSI: ffffffff8f98de8f RDI: ffffffff8f99314d [ 106.030293] RBP: ffffb98bc5157b80 R08: ffffffff90b655fa R09: 0000000090b655d6 [ 106.030293] R10: ffffffffffffffff R11: ffffffffffffffff R12: 0000000000000000 [ 106.030294] R13: 0000000000000000 R14: ffffffff904131e0 R15: 0000000000000000 [ 106.030295] ? oops_end.cold+0xc/0x18 [ 106.030297] ? panic+0x274/0x2b6 [ 106.030299] oops_end.cold+0xc/0x18 [ 106.030300] die+0x43/0x60 [ 106.030302] exc_int3+0x137/0x160 [ 106.030303] asm_exc_int3+0x39/0x40 [ 106.030305] RIP: 0010:xaddw_ax_dx+0x9/0x10 [ 106.030307] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc cc cc 0f 1f 80 00 00 00 00 0f c0 d0 c3 cc cc cc cc 66 0f c1 d0 c3 cc cc cc cc <0f> 1f 80 00 00 00 00 0f c1 d0 c3 cc cc cc cc 48 0f c1 d0 c3 cc cc [ 106.030308] RSP: 0018:ffffb98bc5157ce8 EFLAGS: 00000206 [ 106.030308] RAX: 0000000089abcdef RBX: 0000000000000001 RCX: 0000000000000000 [ 106.030309] RDX: 0000000076543210 RSI: ffffffff8ea56000 RDI: 0000000000000204 [ 106.030310] RBP: ffffb98bc5157cf0 R08: ffffa306c6cf5df0 R09: 0000000000000002 [ 106.030310] R10: ffffa306c6cf5df0 R11: 0000000000000000 R12: ffffa306c6cf5df0 [ 106.030311] R13: ffffffff900090c0 R14: 0000000000000000 R15: 0000000000000000 [ 106.030312] ? xaddw_ax_dx+0x8/0x10 [ 106.030314] ? xaddw_ax_dx+0x9/0x10 [ 106.030315] ? xaddw_ax_dx+0x8/0x10 [ 106.030317] ? fastop+0x5d/0xa0 [ 106.030319] x86_emulate_insn+0x7c9/0xf20 [ 106.030321] x86_emulate_instruction+0x2e3/0x790 [ 106.030323] complete_emulated_mmio+0x238/0x310 [ 106.030325] kvm_arch_vcpu_ioctl_run+0x11ba/0x1a70 [ 106.030327] ? vfs_writev+0xcb/0x140 [ 106.030330] kvm_vcpu_ioctl+0x281/0x6b0 [ 106.030331] ? clockevents_program_event+0x98/0x100 [ 106.030333] ? selinux_file_ioctl+0xae/0x140 [ 106.030335] ? selinux_file_ioctl+0xae/0x140 [ 106.030337] __x64_sys_ioctl+0x95/0xd0 [ 106.030339] do_syscall_64+0x3b/0x90 [ 106.030340] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 106.030342] RIP: 0033:0x7f30aca698f7 [ 106.030343] Code: b3 66 90 48 8b 05 a1 35 2c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 71 35 2c 00 f7 d8 64 89 01 48 [ 106.030343] RSP: 002b:00007f30ab0dea28 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 106.030344] RAX: ffffffffffffffda RBX: 000000000000ae80 RCX: 00007f30aca698f7 [ 106.030345] RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000000f [ 106.030346] RBP: 000055fb7fb6faf0 R08: 000055fb7d67c450 R09: 00000000ffffffff [ 106.030346] R10: 00000000000216a8 R11: 0000000000000246 R12: 0000000000000000 [ 106.030347] R13: 00007f30aed99000 R14: 0000000000000006 R15: 000055fb7fb6faf0 [ 106.030348] </TASK> [ 106.030348] ---[ end trace cec99cae36bcbfd8 ]--- [ 106.030350] ------------[ cut here ]------------ [ 106.030350] sched: Unexpected reschedule of offline CPU#2! [ 106.030351] WARNING: CPU: 3 PID: 3747 at arch/x86/kernel/apic/ipi.c:68 native_smp_send_reschedule+0x3e/0x50 [ 106.030354] Modules linked in: x86_pkg_temp_thermal [ 106.030354] CPU: 3 PID: 3747 Comm: qemu-system-x86 Tainted: G D W 5.15.55-rc1 #1 [ 106.030355] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.0b 07/27/2017 [ 106.030356] RIP: 0010:native_smp_send_reschedule+0x3e/0x50 [ 106.030357] Code: 1b 48 8b 05 d4 70 a6 01 be fd 00 00 00 48 8b 40 30 e8 66 dc 31 01 5d c3 cc cc cc cc 89 fe 48 c7 c7 a0 e9 41 90 e8 1e c3 ea 00 <0f> 0b 5d c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 [ 106.030358] RSP: 0018:ffffb98bc0160b40 EFLAGS: 00010086 [ 106.030359] RAX: 0000000000000000 RBX: ffffa30a1fd29b00 RCX: 0000000000000027 [ 106.030360] RDX: ffffa30a1fd9b4b8 RSI: 0000000000000001 RDI: ffffa30a1fd9b4b0 [ 106.030360] RBP: ffffb98bc0160b40 R08: ffffffff90b66d1d R09: 0000000000000000 [ 106.030361] R10: 0000000000000030 R11: ffffffff90b66d1d R12: ffffa306c2216180 [ 106.030361] R13: ffffb98bc0160be0 R14: ffffb98bc0160be0 R15: 0000000000000009 [ 106.030362] FS: 00007f30ab0df700(0000) GS:ffffa30a1fd80000(0000) knlGS:0000000000000000 [ 106.030363] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 106.030364] CR2: 0000000000000000 CR3: 000000014e0d0003 CR4: 00000000003726e0 [ 106.030364] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 106.030365] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 106.030365] Call Trace: [ 106.030366] <IRQ> [ 106.030366] resched_curr+0x52/0xb0 [ 106.030368] check_preempt_curr+0x3b/0x70 [ 106.030369] ttwu_do_wakeup+0x1c/0x160 [ 106.030371] ttwu_do_activate+0x94/0x190 [ 106.030373] try_to_wake_up+0x1c4/0x480 [ 106.030375] default_wake_function+0x1a/0x40 [ 106.030377] autoremove_wake_function+0x12/0x40 [ 106.030378] __wake_up_common+0x7d/0x140 [ 106.030380] __wake_up_common_lock+0x7c/0xc0 [ 106.030382] __wake_up+0x13/0x20 [ 106.030384] ep_poll_callback+0x10e/0x290 [ 106.030386] __wake_up_common+0x7d/0x140 [ 106.030389] __wake_up_common_lock+0x7c/0xc0 [ 106.030391] __wake_up+0x13/0x20 [ 106.030393] wake_up_klogd_work_func+0x7b/0x90 [ 106.030395] irq_work_single+0x46/0x80 [ 106.030397] irq_work_run_list+0x2a/0x40 [ 106.030398] irq_work_tick+0x3b/0x50 [ 106.030400] update_process_times+0xba/0xd0 [ 106.030401] tick_sched_handle+0x38/0x50 [ 106.030403] tick_sched_timer+0x8c/0xc0 [ 106.030405] ? can_stop_idle_tick+0xa0/0xa0 [ 106.030407] __hrtimer_run_queues+0xa6/0x2b0 [ 106.030408] hrtimer_interrupt+0x101/0x220 [ 106.030410] __sysvec_apic_timer_interrupt+0x61/0xe0 [ 106.030411] sysvec_apic_timer_interrupt+0x7b/0x90 [ 106.030413] </IRQ> [ 106.030413] <TASK> [ 106.030414] asm_sysvec_apic_timer_interrupt+0x1a/0x20 [ 106.030416] RIP: 0010:panic+0x277/0x2b6 [ 106.030417] Code: e8 65 ac 25 ff 48 c7 c6 80 04 b5 90 48 c7 c7 80 3f 42 90 e8 6a 58 00 00 c7 05 cc 8e f5 00 01 00 00 00 e8 d3 80 33 ff fb 31 db <4c> 39 eb 7c 1d 41 83 f4 01 48 8b 05 a0 d2 1b 01 44 89 e7 e8 18 16 [ 106.030418] RSP: 0018:ffffb98bc5157b10 EFLAGS: 00000246 [ 106.030419] RAX: ffffb98bc5157b80 RBX: 0000000000000000 RCX: 0000000000000027 [ 106.030419] RDX: 0000000000000000 RSI: ffffffff8f98de8f RDI: ffffffff8f99314d [ 106.030420] RBP: ffffb98bc5157b80 R08: ffffffff90b655fa R09: 0000000090b655d6 [ 106.030420] R10: ffffffffffffffff R11: ffffffffffffffff R12: 0000000000000000 [ 106.030421] R13: 0000000000000000 R14: ffffffff904131e0 R15: 0000000000000000 [ 106.030422] ? oops_end.cold+0xc/0x18 [ 106.030423] ? panic+0x274/0x2b6 [ 106.030425] oops_end.cold+0xc/0x18 [ 106.030427] die+0x43/0x60 [ 106.030428] exc_int3+0x137/0x160 [ 106.030430] asm_exc_int3+0x39/0x40 [ 106.030431] RIP: 0010:xaddw_ax_dx+0x9/0x10 [ 106.030433] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc cc cc 0f 1f 80 00 00 00 00 0f c0 d0 c3 cc cc cc cc 66 0f c1 d0 c3 cc cc cc cc <0f> 1f 80 00 00 00 00 0f c1 d0 c3 cc cc cc cc 48 0f c1 d0 c3 cc cc [ 106.030434] RSP: 0018:ffffb98bc5157ce8 EFLAGS: 00000206 [ 106.030434] RAX: 0000000089abcdef RBX: 0000000000000001 RCX: 0000000000000000 [ 106.030435] RDX: 0000000076543210 RSI: ffffffff8ea56000 RDI: 0000000000000204 [ 106.030436] RBP: ffffb98bc5157cf0 R08: ffffa306c6cf5df0 R09: 0000000000000002 [ 106.030436] R10: ffffa306c6cf5df0 R11: 0000000000000000 R12: ffffa306c6cf5df0 [ 106.030437] R13: ffffffff900090c0 R14: 0000000000000000 R15: 0000000000000000 [ 106.030437] ? xaddw_ax_dx+0x8/0x10 [ 106.030439] ? xaddw_ax_dx+0x9/0x10 [ 106.030441] ? xaddw_ax_dx+0x8/0x10 [ 106.030443] ? fastop+0x5d/0xa0 [ 106.030445] x86_emulate_insn+0x7c9/0xf20 [ 106.030446] x86_emulate_instruction+0x2e3/0x790 [ 106.030449] complete_emulated_mmio+0x238/0x310 [ 106.030450] kvm_arch_vcpu_ioctl_run+0x11ba/0x1a70 [ 106.030453] ? vfs_writev+0xcb/0x140 [ 106.030455] kvm_vcpu_ioctl+0x281/0x6b0 [ 106.030456] ? clockevents_program_event+0x98/0x100 [ 106.030458] ? selinux_file_ioctl+0xae/0x140 [ 106.030460] ? selinux_file_ioctl+0xae/0x140 [ 106.030462] __x64_sys_ioctl+0x95/0xd0 [ 106.030464] do_syscall_64+0x3b/0x90 [ 106.030465] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 106.030467] RIP: 0033:0x7f30aca698f7 [ 106.030468] Code: b3 66 90 48 8b 05 a1 35 2c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 71 35 2c 00 f7 d8 64 89 01 48 [ 106.030468] RSP: 002b:00007f30ab0dea28 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 106.030469] RAX: ffffffffffffffda RBX: 000000000000ae80 RCX: 00007f30aca698f7 [ 106.030470] RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000000f [ 106.030470] RBP: 000055fb7fb6faf0 R08: 000055fb7d67c450 R09: 00000000ffffffff [ 106.030471] R10: 00000000000216a8 R11: 0000000000000246 R12: 0000000000000000 [ 106.030472] R13: 00007f30aed99000 R14: 0000000000000006 R15: 000055fb7fb6faf0 [ 106.030473] </TASK> [ 106.030473] ---[ end trace cec99cae36bcbfd9 ]---
- Kernel warning
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.... <6>[ 0.571674] Speculative Store Bypass: Vulnerable <6>[ 0.573329] MDS: Vulnerable: Clear CPU buffers attempted, no microcode <4>[ 0.942716] ------------[ cut here ]------------ <4>[ 0.944263] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/alternative.c:557 apply_returns+0x19c/0x1d0 <4>[ 0.945106] Modules linked in: <4>[ 0.946322] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.55-rc1 #1 <4>[ 0.947052] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 <4>[ 0.947844] RIP: 0010:apply_returns+0x19c/0x1d0 <4>[ 0.948453] Code: 8d 7d c8 4c 89 75 c1 4c 89 74 08 f8 48 29 f8 8d 0c 02 4c 89 f0 c1 e9 03 f3 48 ab 8b 05 9d ba 52 02 85 c0 74 a0 e9 45 32 1a 01 <0f> 0b 48 83 c3 04 49 39 dd 0f 87 96 fe ff ff e9 0f ff ff ff c7 45 <4>[ 0.950059] RSP: 0000:ffffffff89803d78 EFLAGS: 00000206 <4>[ 0.950484] RAX: 0000000000000000 RBX: ffffffff89dbb174 RCX: 0000000000000000 <4>[ 0.951033] RDX: ffffffff891011b5 RSI: 00000000000000e9 RDI: ffffffff891011b0 <4>[ 0.951488] RBP: ffffffff89803e40 R08: 0000000000000000 R09: 0000000000000001 <4>[ 0.952032] R10: 0000000000000029 R11: 0000000000000000 R12: ffffffff891011b0 <4>[ 0.952488] R13: ffffffff89ddb184 R14: cccccccccccccccc R15: ffffffff891011b5 <4>[ 0.953125] FS: 0000000000000000(0000) GS:ffff90f63fc00000(0000) knlGS:0000000000000000 <4>[ 0.953634] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>[ 0.954031] CR2: ffff90f63fa01000 CR3: 000000003e826000 CR4: 00000000000006f0 <4>[ 0.954669] Call Trace: <4>[ 0.955846] <TASK> <4>[ 0.957183] alternative_instructions+0x7d/0x146 <4>[ 0.957673] check_bugs+0xf16/0xf57 <4>[ 0.958114] start_kernel+0x6b6/0x6ef <4>[ 0.958446] x86_64_start_reservations+0x24/0x2a <4>[ 0.958764] x86_64_start_kernel+0x8d/0x95 <4>[ 0.959035] secondary_startup_64_no_verify+0xc2/0xcb <4>[ 0.959591] </TASK> <4>[ 0.960146] irq event stamp: 121171 <4>[ 0.960419] hardirqs last enabled at (121179): [<ffffffff87a7247c>] __up_console_sem+0x5c/0x70 <4>[ 0.961036] hardirqs last disabled at (121188): [<ffffffff87a72461>] __up_console_sem+0x41/0x70 <4>[ 0.961577] softirqs last enabled at (1484): [<ffffffff87ad3f20>] cgroup_idr_alloc.constprop.0+0x60/0xe0 <4>[ 0.962031] softirqs last disabled at (1482): [<ffffffff87ad3ef3>] cgroup_idr_alloc.constprop.0+0x33/0xe0 <4>[ 0.963358] ---[ end trace 7af0f35d34a8be8b ]--- <6>[ 1.100332] Freeing SMP alternatives memory: 52K <6>[ 1.233988] smpboot: CPU0: Intel Core i7 9xx (Nehalem Class Core i7) (family: 0x6, model: 0x1a, stepping: 0x3) <6>[ 1.266761] Running RCU-tasks wait API self tests <6>[ 1.271070] Performance Events: unsupported p6 CPU model 26 no PMU driver, software events only. <6>[ 1.276776] rcu: Hierarchical SRCU implementation. <6>[ 1.281153] Callback from call_rcu_ta# sks_trace() invoked. <6>[ 1.308215] smp: Bringing up secondary CPUs ... <6>[ 1.322732] x86: Booting SMP configuration: <6>[ 1.323121] .... node #0, CPUs: #1 <6>[ 1.361239] smp: Brought up 1 node, 2 CPUs
## Build
- kernel: 5.15.55-rc1
- git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
- git branch: linux-5.15.y
- git commit: 0fe4fdf9b1dac90e23465eefeff45e529adcf3c6
- git describe: v5.15.54-79-g0fe4fdf9b1da
- test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15....
## Test Regressions (compared to v5.15.53-227-g71721f5974f2) kernel crash regression found.
## Metric Regressions (compared to v5.15.53-227-g71721f5974f2) No metric regressions found.
## Test Fixes (compared to v5.15.53-227-g71721f5974f2) No test fixes found.
## Metric Fixes (compared to v5.15.53-227-g71721f5974f2) No metric fixes found.
## Test result summary total: 137556, pass: 124337, fail: 404, skip: 12121, xfail: 694
## Build Summary
- arc: 10 total, 10 passed, 0 failed
- arm: 308 total, 308 passed, 0 failed
- arm64: 62 total, 62 passed, 0 failed
- i386: 52 total, 49 passed, 3 failed
- mips: 48 total, 48 passed, 0 failed
- parisc: 12 total, 12 passed, 0 failed
- powerpc: 54 total, 52 passed, 2 failed
- riscv: 22 total, 22 passed, 0 failed
- s390: 21 total, 21 passed, 0 failed
- sh: 24 total, 24 passed, 0 failed
- sparc: 12 total, 12 passed, 0 failed
- x86_64: 56 total, 55 passed, 1 failed
## Test suites summary
- fwts
- kunit
- kvm-unit-tests
- libgpiod
- libhugetlbfs
- log-parser-boot
- log-parser-test
- ltp-cap_bounds
- ltp-commands
- ltp-containers
- ltp-controllers
- ltp-cpuhotplug
- ltp-crypto
- ltp-cve
- ltp-dio
- ltp-fcntl-locktests
- ltp-filecaps
- ltp-fs
- ltp-fs_bind
- ltp-fs_perms_simple
- ltp-fsx
- ltp-hugetlb
- ltp-io
- ltp-ipc
- ltp-math
- ltp-mm
- ltp-nptl
- ltp-open-posix-tests
- ltp-pty
- ltp-sched
- ltp-securebits
- ltp-smoke
- ltp-syscalls
- ltp-tracing
- network-basic-tests
- packetdrill
- perf
- perf/Zstd-perf.data-compression
- rcutorture
- ssuite
- v4l2-compliance
- vdso
-- Linaro LKFT https://lkft.linaro.org
On Thu, Jul 14, 2022 at 12:50:10PM +0300, Maxim Levitsky wrote:
On Wed, 2022-07-13 at 18:22 +0530, Naresh Kamboju wrote:
On Wed, 13 Jul 2022 at 00:17, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +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.15.55-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y and the diffstat can be found below.
thanks,
greg k-h
Results from Linaro’s test farm. Regressions on x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
- Kernel panic noticed on device x86_6 while running kvm-unit-tests.
- APIC base relocation is unsupported by KVM
My 0.2 cent:
APIC base relocation warning is harmless, and I removed it 5.19 kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h...
Nice, but doesn't look relevant for stable trees.
The 'emulating exchange as write' is also something that KVM unit tests trigger normally although this warning recently did signal a real and very nasty bug, which I fixed in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h...
Already in the 5.18.2 release, doesn't look all that relevant for 5.15, odd that it is showing up on 5.15.
thanks,
greg k-h
On Thu, 2022-07-14 at 12:04 +0200, Greg Kroah-Hartman wrote:
On Thu, Jul 14, 2022 at 12:50:10PM +0300, Maxim Levitsky wrote:
On Wed, 2022-07-13 at 18:22 +0530, Naresh Kamboju wrote:
On Wed, 13 Jul 2022 at 00:17, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +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.15.55-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y and the diffstat can be found below.
thanks,
greg k-h
Results from Linaro’s test farm. Regressions on x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
- Kernel panic noticed on device x86_6 while running kvm-unit-tests.
- APIC base relocation is unsupported by KVM
My 0.2 cent:
APIC base relocation warning is harmless, and I removed it 5.19 kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h...
Nice, but doesn't look relevant for stable trees.
The 'emulating exchange as write' is also something that KVM unit tests trigger normally although this warning recently did signal a real and very nasty bug, which I fixed in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h...
Already in the 5.18.2 release, doesn't look all that relevant for 5.15, odd that it is showing up on 5.15.
Yep, I also think so - I just wanted to point out the source of these warnings.
Best regards, Maxim Levitsky
thanks,
greg k-h
On 7/12/22 11:38 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +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.15.55-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y and the diffstat can be found below.
thanks,
greg k-h
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Tested-by: Ron Economos re@w6rz.net
On Tue, Jul 12, 2022 at 08:38:30PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.15.55 release. There are 78 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 Thu, 14 Jul 2022 18:32:19 +0000. Anything received after that time might be too late.
Build results: total: 159 pass: 158 fail: 1 Failed builds: um:defconfig Qemu test results: total: 488 pass: 480 fail: 8 Failed tests: x86_64:q35:SandyBridge:defconfig:smp4:net,ne2k_pci:efi32:mem1G:usb:hd x86_64:q35:Conroe:defconfig:smp4:net,tulip:efi32:mem256:scsi[DC395]:hd x86_64:q35:Skylake-Server:defconfig:smp4:net,e1000-82544gc:efi32:mem2G:scsi[53C895A]:hd x86_64:q35:Opteron_G5:defconfig:smp4:net,i82559c:efi32:mem256:scsi[MEGASAS2]:hd x86_64:pc:Opteron_G2:defconfig:smp:net,usb:efi32:mem2G:scsi[virtio-pci]:hd x86_64:q35:Nehalem:defconfig:smp2:net,i82558a:efi32:mem1G:virtio:hd x86_64:q35:Skylake-Client-IBRS:defconfig:preempt:smp2:net,i82558b:efi32:mem1G:sdhci:mmc:hd x86_64:q35:Haswell-noTSX-IBRS:defconfig:nosmp:net,pcnet:efi32:mem2G:ata:hd
Guenter
-
Bagas Sanjaya -
Boris Petkov -
Borislav Petkov
-
Florian Fainelli -
Greg Kroah-Hartman -
Guenter Roeck -
Jon Hunter -
Linus Torvalds -
Maxim Levitsky -
Naresh Kamboju -
Paolo Bonzini -
Peter Zijlstra -
Ron Economos -
Shuah Khan -
Sudip Mukherjee (Codethink)