* [Bug 206525] New: BUG: KASAN: stack-out-of-bounds in test_bit+0x30/0x44 (kernel 5.6-rc1)
From: bugzilla-daemon @ 2020-02-13 20:07 UTC (permalink / raw)
To: linuxppc-dev
https://bugzilla.kernel.org/show_bug.cgi?id=206525
Bug ID: 206525
Summary: BUG: KASAN: stack-out-of-bounds in test_bit+0x30/0x44
(kernel 5.6-rc1)
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.6.0-rc1
Hardware: PPC-32
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-32
Assignee: platform_ppc-32@kernel-bugs.osdl.org
Reporter: erhard_f@mailbox.org
Regression: No
Created attachment 287357
--> https://bugzilla.kernel.org/attachment.cgi?id=287357&action=edit
dmesg (5.6.0-rc1 + v2 Fix DSI and ISI... patch, PowerMac G4 DP)
[...]
Feb 13 20:18:53 T600 kernel:
==================================================================
Feb 13 20:18:53 T600 kernel: BUG: KASAN: stack-out-of-bounds in
test_bit+0x30/0x44
Feb 13 20:18:53 T600 kernel: Read of size 4 at addr ee8bddac by task systemd/1
Feb 13 20:18:53 T600 kernel:
Feb 13 20:18:53 T600 kernel: CPU: 0 PID: 1 Comm: systemd Tainted: G W
5.6.0-rc1-PowerMacG4+ #20
Feb 13 20:18:53 T600 kernel: Call Trace:
Feb 13 20:18:53 T600 kernel: [ee8bdc38] [c078cf18] dump_stack+0xbc/0x118
(unreliable)
Feb 13 20:18:53 T600 kernel: [ee8bdc68] [c0249f94]
print_address_description.isra.0+0x3c/0x420
Feb 13 20:18:53 T600 kernel: [ee8bdcf8] [c024a554] __kasan_report+0x138/0x180
Feb 13 20:18:53 T600 kernel: [ee8bdd38] [c0249718] kasan_report+0x7c/0x104
Feb 13 20:18:53 T600 kernel: [ee8bdd58] [c06526b4] test_bit+0x30/0x44
Feb 13 20:18:53 T600 kernel: [ee8bdd78] [c0657c6c] netlink_bind+0x24c/0x33c
Feb 13 20:18:53 T600 kernel: [ee8bde18] [c05c0c3c] __sys_bind+0xd4/0x120
Feb 13 20:18:53 T600 kernel: [ee8bdf38] [c001a278] ret_from_syscall+0x0/0x34
Feb 13 20:18:53 T600 kernel: --- interrupt: c01 at 0x4f3ea8
LR = 0x8f5b80
Feb 13 20:18:53 T600 kernel:
Feb 13 20:18:53 T600 kernel: The buggy address belongs to the page:
Feb 13 20:18:53 T600 kernel: page:ef460a94 refcount:0 mapcount:0
mapping:00000000 index:0x0
Feb 13 20:18:53 T600 kernel: flags: 0x0()
Feb 13 20:18:53 T600 kernel: raw: 00000000 ef460a98 ef460a98 00000000 00000000
00000000 ffffffff 00000000
Feb 13 20:18:53 T600 kernel: raw: 00000000
Feb 13 20:18:53 T600 kernel: page dumped because: kasan: bad access detected
Feb 13 20:18:53 T600 kernel:
Feb 13 20:18:53 T600 kernel: addr ee8bddac is located in stack of task
systemd/1 at offset 36 in frame:
Feb 13 20:18:53 T600 kernel: netlink_bind+0x0/0x33c
Feb 13 20:18:53 T600 kernel:
Feb 13 20:18:53 T600 kernel: this frame has 1 object:
Feb 13 20:18:53 T600 kernel: [32, 36) 'groups'
Feb 13 20:18:53 T600 kernel:
Feb 13 20:18:53 T600 kernel: Memory state around the buggy address:
Feb 13 20:18:53 T600 kernel: ee8bdc80: 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
Feb 13 20:18:53 T600 kernel: ee8bdd00: 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
Feb 13 20:18:53 T600 kernel: >ee8bdd80: 00 f1 f1 f1 f1 04 f3 f3 f3 00 00 00 00
00 00 00
Feb 13 20:18:53 T600 kernel: ^
Feb 13 20:18:53 T600 kernel: ee8bde00: 00 00 00 00 00 f1 f1 f1 f1 04 f2 04 f2
00 00 00
Feb 13 20:18:53 T600 kernel: ee8bde80: 00 00 00 00 00 00 00 00 00 00 00 00 00
f3 f3 f3
Feb 13 20:18:53 T600 kernel:
==================================================================
Happens on my G4 DP with kernel 5.6.0-rc1 and KASAN enabled (outline) during
boot. kernel is patched with Christophe's '[v2] powerpc/32s: Fix DSI and ISI
exceptions for CONFIG_VMAP_STACK' (https://patchwork.ozlabs.org/patch/1237387/)
but CONFIG_VMAP_STACK was not used here.
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply
* Re: [PATCH] serial: cpm_uart: call cpm_muram_init before registering console
From: Greg Kroah-Hartman @ 2020-02-13 20:00 UTC (permalink / raw)
To: Rasmus Villemoes
Cc: Timur Tabi, linux-kernel, Li Yang, Scott Wood, linux-serial,
Jiri Slaby, linuxppc-dev, Qiang Zhao
In-Reply-To: <20200213114342.21712-1-linux@rasmusvillemoes.dk>
On Thu, Feb 13, 2020 at 12:43:42PM +0100, Rasmus Villemoes wrote:
> Christophe reports that powerpc 8xx silently fails to 5.6-rc1. It turns
> out I was wrong about nobody relying on the lazy initialization of the
> cpm/qe muram in commit b6231ea2b3c6 (soc: fsl: qe: drop broken lazy
> call of cpm_muram_init()).
>
> Rather than reinstating the somewhat dubious lazy call (initializing a
> currently held spinlock, and implicitly doing a GFP_KERNEL under that
> spinlock), make sure that cpm_muram_init() is called early enough - I
> thought the calls from the subsys_initcalls were good enough, but when
> used by console drivers, that's obviously not the
> case. cpm_muram_init() is safe to call twice (there's an early return
> if it is already initialized), so keep the call from cpm_init() - in
> case SERIAL_CPM_CONSOLE=n.
>
> Reported-by: Christophe Leroy <christophe.leroy@c-s.fr>
> Fixes: b6231ea2b3c6 (soc: fsl: qe: drop broken lazy call of cpm_muram_init())
> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> ---
>
> Christophe, can I get you to add a formal Tested-by?
>
> I'm not sure which tree this should go through.
I can take it, thanks.
greg k-h
^ permalink raw reply
* [Bug 206501] Kernel 5.6-rc1 fails to boot on a PowerMac G4 3,6 with CONFIG_VMAP_STACK=y: Oops! Machine check, sig: 7 [#1]
From: bugzilla-daemon @ 2020-02-13 19:49 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <bug-206501-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206501
--- Comment #10 from Erhard F. (erhard_f@mailbox.org) ---
Sure. Thanks!
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply
* Re: [PATCH v2 1/4] mm/memremap_pages: Introduce memremap_compat_align()
From: Dan Williams @ 2020-02-13 18:26 UTC (permalink / raw)
To: Jeff Moyer
Cc: linux-nvdimm, Aneesh Kumar K.V, Linux Kernel Mailing List,
Paul Mackerras, Vishal L Verma, linuxppc-dev
In-Reply-To: <x498sl677cf.fsf@segfault.boston.devel.redhat.com>
On Thu, Feb 13, 2020 at 8:58 AM Jeff Moyer <jmoyer@redhat.com> wrote:
>
> Dan Williams <dan.j.williams@intel.com> writes:
>
> > The "sub-section memory hotplug" facility allows memremap_pages() users
> > like libnvdimm to compensate for hardware platforms like x86 that have a
> > section size larger than their hardware memory mapping granularity. The
> > compensation that sub-section support affords is being tolerant of
> > physical memory resources shifting by units smaller (64MiB on x86) than
> > the memory-hotplug section size (128 MiB). Where the platform
> > physical-memory mapping granularity is limited by the number and
> > capability of address-decode-registers in the memory controller.
> >
> > While the sub-section support allows memremap_pages() to operate on
> > sub-section (2MiB) granularity, the Power architecture may still
> > require 16MiB alignment on "!radix_enabled()" platforms.
> >
> > In order for libnvdimm to be able to detect and manage this per-arch
> > limitation, introduce memremap_compat_align() as a common minimum
> > alignment across all driver-facing memory-mapping interfaces, and let
> > Power override it to 16MiB in the "!radix_enabled()" case.
> >
> > The assumption / requirement for 16MiB to be a viable
> > memremap_compat_align() value is that Power does not have platforms
> > where its equivalent of address-decode-registers never hardware remaps a
> > persistent memory resource on smaller than 16MiB boundaries. Note that I
> > tried my best to not add a new Kconfig symbol, but header include
> > entanglements defeated the #ifndef memremap_compat_align design pattern
> > and the need to export it defeats the __weak design pattern for arch
> > overrides.
> >
> > Based on an initial patch by Aneesh.
>
> I have just a couple of questions.
>
> First, can you please add a comment above the generic implementation of
> memremap_compat_align describing its purpose, and why a platform might
> want to override it?
Sure, how about:
/*
* The memremap() and memremap_pages() interfaces are alternately used
* to map persistent memory namespaces. These interfaces place different
* constraints on the alignment and size of the mapping (namespace).
* memremap() can map individual PAGE_SIZE pages. memremap_pages() can
* only map subsections (2MB), and at least one architecture (PowerPC)
* the minimum mapping granularity of memremap_pages() is 16MB.
*
* The role of memremap_compat_align() is to communicate the minimum
* arch supported alignment of a namespace such that it can freely
* switch modes without violating the arch constraint. Namely, do not
* allow a namespace to be PAGE_SIZE aligned since that namespace may be
* reconfigured into a mode that requires SUBSECTION_SIZE alignment.
*/
> Second, I will take it at face value that the power architecture
> requires a 16MB alignment, but it's not clear to me why mmu_linear_psize
> was chosen to represent that. What's the relationship, there, and can
> we please have a comment explaining it?
Aneesh, can you help here?
^ permalink raw reply
* [Bug 206501] Kernel 5.6-rc1 fails to boot on a PowerMac G4 3,6 with CONFIG_VMAP_STACK=y: Oops! Machine check, sig: 7 [#1]
From: bugzilla-daemon @ 2020-02-13 17:32 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <bug-206501-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206501
--- Comment #9 from Christophe Leroy (christophe.leroy@c-s.fr) ---
Great. Can we add your Tested-by: to the commit ?
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply
* [PATCH] powerpc: Fix /proc/cpuinfo revision for POWER9P processors
From: Mahesh Salgaonkar @ 2020-02-13 16:34 UTC (permalink / raw)
To: linuxppc-dev; +Cc: Michael Neuling
POWER9P PVR bits are same as that of POWER9. Hence mask off only the
relevant bits for the major revision similar to POWER9.
Without this patch the cpuinfo output shows 17.0 as revision:
$ cat /proc/cpuinfo
processor : 0
cpu : POWER9P, altivec supported
clock : 2950.000000MHz
revision : 17.0 (pvr 004f 1100)
With this change it reflects the correct revision:
$ cat /proc/cpuinfo
processor : 0
cpu : POWER9P, altivec supported
clock : 2633.000000MHz
revision : 1.0 (pvr 004f 1100)
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
---
arch/powerpc/kernel/setup-common.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/kernel/setup-common.c b/arch/powerpc/kernel/setup-common.c
index 488f1eecc0de..37342ec42cb3 100644
--- a/arch/powerpc/kernel/setup-common.c
+++ b/arch/powerpc/kernel/setup-common.c
@@ -315,6 +315,7 @@ static int show_cpuinfo(struct seq_file *m, void *v)
min = pvr & 0xFF;
break;
case 0x004e: /* POWER9 bits 12-15 give chip type */
+ case 0x004f: /* POWER9P bits 12-15 give chip type */
maj = (pvr >> 8) & 0x0F;
min = pvr & 0xFF;
break;
^ permalink raw reply related
* [PATCH] KVM: PPC: Book3S HV: Treat unrecognized TM instructions as illegal
From: Gustavo Romero @ 2020-02-13 15:15 UTC (permalink / raw)
To: kvm-ppc, paulus; +Cc: linuxppc-dev, gromero
On P9 DD2.2 due to a CPU defect some TM instructions need to be emulated by
KVM. This is handled at first by the hardware raising a softpatch interrupt
when certain TM instructions that need KVM assistance are executed in the
guest. Some TM instructions, although not defined in the Power ISA, might
raise a softpatch interrupt. For instance, 'tresume.' instruction as
defined in the ISA must have bit 31 set (1), but an instruction that
matches 'tresume.' OP and XO opcodes but has bit 31 not set (0), like
0x7cfe9ddc, also raises a softpatch interrupt, for example, if a code
like the following is executed in the guest it will raise a softpatch
interrupt just like a 'tresume.' when the TM facility is enabled:
int main() { asm("tabort. 0; .long 0x7cfe9ddc;"); }
Currently in such a case KVM throws a complete trace like the following:
[345523.705984] WARNING: CPU: 24 PID: 64413 at arch/powerpc/kvm/book3s_hv_tm.c:211 kvmhv_p9_tm_emulation+0x68/0x620 [kvm_hv]
[345523.705985] Modules linked in: kvm_hv(E) xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat
iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ebtable_filter ebtables ip6table_filter
ip6_tables iptable_filter bridge stp llc sch_fq_codel ipmi_powernv at24 vmx_crypto ipmi_devintf ipmi_msghandler
ibmpowernv uio_pdrv_genirq kvm opal_prd uio leds_powernv ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456
async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear tg3
crct10dif_vpmsum crc32c_vpmsum ipr [last unloaded: kvm_hv]
[345523.706030] CPU: 24 PID: 64413 Comm: CPU 0/KVM Tainted: G W E 5.5.0+ #1
[345523.706031] NIP: c0080000072cb9c0 LR: c0080000072b5e80 CTR: c0080000085c7850
[345523.706034] REGS: c000000399467680 TRAP: 0700 Tainted: G W E (5.5.0+)
[345523.706034] MSR: 900000010282b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE,TM[E]> CR: 24022428 XER: 00000000
[345523.706042] CFAR: c0080000072b5e7c IRQMASK: 0
GPR00: c0080000072b5e80 c000000399467910 c0080000072db500 c000000375ccc720
GPR04: c000000375ccc720 00000003fbec0000 0000a10395dda5a6 0000000000000000
GPR08: 000000007cfe9ddc 7cfe9ddc000005dc 7cfe9ddc7c0005dc c0080000072cd530
GPR12: c0080000085c7850 c0000003fffeb800 0000000000000001 00007dfb737f0000
GPR16: c0002001edcca558 0000000000000000 0000000000000000 0000000000000001
GPR20: c000000001b21258 c0002001edcca558 0000000000000018 0000000000000000
GPR24: 0000000001000000 ffffffffffffffff 0000000000000001 0000000000001500
GPR28: c0002001edcc4278 c00000037dd80000 800000050280f033 c000000375ccc720
[345523.706062] NIP [c0080000072cb9c0] kvmhv_p9_tm_emulation+0x68/0x620 [kvm_hv]
[345523.706065] LR [c0080000072b5e80] kvmppc_handle_exit_hv.isra.53+0x3e8/0x798 [kvm_hv]
[345523.706066] Call Trace:
[345523.706069] [c000000399467910] [c000000399467940] 0xc000000399467940 (unreliable)
[345523.706071] [c000000399467950] [c000000399467980] 0xc000000399467980
[345523.706075] [c0000003994679f0] [c0080000072bd1c4] kvmhv_run_single_vcpu+0xa1c/0xb80 [kvm_hv]
[345523.706079] [c000000399467ac0] [c0080000072bd8e0] kvmppc_vcpu_run_hv+0x5b8/0xb00 [kvm_hv]
[345523.706087] [c000000399467b90] [c0080000085c93cc] kvmppc_vcpu_run+0x34/0x48 [kvm]
[345523.706095] [c000000399467bb0] [c0080000085c582c] kvm_arch_vcpu_ioctl_run+0x244/0x420 [kvm]
[345523.706101] [c000000399467c40] [c0080000085b7498] kvm_vcpu_ioctl+0x3d0/0x7b0 [kvm]
[345523.706105] [c000000399467db0] [c0000000004adf9c] ksys_ioctl+0x13c/0x170
[345523.706107] [c000000399467e00] [c0000000004adff8] sys_ioctl+0x28/0x80
[345523.706111] [c000000399467e20] [c00000000000b278] system_call+0x5c/0x68
[345523.706112] Instruction dump:
[345523.706114] 419e0390 7f8a4840 409d0048 6d497c00 2f89075d 419e021c 6d497c00 2f8907dd
[345523.706119] 419e01c0 6d497c00 2f8905dd 419e00a4 <0fe00000> 38210040 38600000 ebc1fff0
and then treats the executed instruction as 'nop' whilst it should actually
be treated as an illegal instruction since it's not defined by the ISA.
This commit changes the handling of the case above by treating the
unrecognized TM instructions that can raise a softpatch but are not
defined in the ISA as illegal ones instead of as 'nop' and by gently
reporting it to the host instead of throwing a trace.
Signed-off-by: Gustavo Romero <gromero@linux.ibm.com>
---
arch/powerpc/kvm/book3s_hv_tm.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/kvm/book3s_hv_tm.c b/arch/powerpc/kvm/book3s_hv_tm.c
index 0db937497169..d342a9e11298 100644
--- a/arch/powerpc/kvm/book3s_hv_tm.c
+++ b/arch/powerpc/kvm/book3s_hv_tm.c
@@ -3,6 +3,8 @@
* Copyright 2017 Paul Mackerras, IBM Corp. <paulus@au1.ibm.com>
*/
+#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
+
#include <linux/kvm_host.h>
#include <asm/kvm_ppc.h>
@@ -208,6 +210,8 @@ int kvmhv_p9_tm_emulation(struct kvm_vcpu *vcpu)
}
/* What should we do here? We didn't recognize the instruction */
- WARN_ON_ONCE(1);
+ kvmppc_core_queue_program(vcpu, SRR1_PROGILL);
+ pr_warn_ratelimited("Unrecognized TM-related instruction %#x for emulation", instr);
+
return RESUME_GUEST;
}
--
2.17.1
^ permalink raw reply related
* Re: RESEND: Re: Problem booting a PowerBook G4 Aluminum after commit cd08f109 with CONFIG_VMAP_STACK=y
From: Christophe Leroy @ 2020-02-13 14:43 UTC (permalink / raw)
To: Larry Finger; +Cc: linuxppc-dev@ozlabs.org
In-Reply-To: <7f63e8a8-95c5-eeca-dc79-3c13f4d98d39@lwfinger.net>
On 02/13/2020 02:28 PM, Larry Finger wrote:
> On 2/11/20 1:23 PM, Christophe Leroy wrote:
>> Can you send me a picture of that BUG Unable to handle kernel data
>> access with all the registers values etc..., together with the
>> matching vmlinux ?
>>
>> First thing is to identify where we are when that happens. That mean
>> see what is at 0xc0013674. Can be done with 'ppc-linux-objdump -d
>> vmlinux' (Or whatever your PPC objdump is named) and get the function
>> code.
>>
>> Then we need to understand how we reach that function and why it tries
>> to access a physical address.
>>
>>
>> Another thing I'm thinking about, not necessarily related to that
>> problem: Some buggy drivers do DMA from stack. This doesn't work
>> anymore with CONFIG_VMAP_STACK. Most of them can be detected with
>> CONFIG_DEBUG_VIRTUAL so you should activate it.
>
> Christophe,
>
> The previous send of this message failed because the attached vmlinux
> was too large.
>
> I have gone about as far as I can in debugging the problem. Setting
> CONFIG_DEBUG_VIRTUAL made no difference.
>
> Attached are the final screenshot, and the patches that I have applied.
> You already have the gzipped vmlinux.
>
This screenshot makes more sense with the vmlinux you provided, problem
at 0xc00136dc.
That's in function power_save_ppc32_restore() in
arch/powerpc/kernel/idle_6xx.S.
c00136c0 <power_save_ppc32_restore>:
c00136c0: 81 2b 00 a0 lwz r9,160(r11)
c00136c4: 91 2b 00 90 stw r9,144(r11)
c00136c8: 39 60 00 00 li r11,0
c00136cc: 7d 30 fa a6 mfspr r9,1008
c00136d0: 75 29 00 40 andis. r9,r9,64
c00136d4: 41 82 00 18 beq c00136ec <power_save_ppc32_restore+0x2c>
c00136d8: 3d 2b 00 7c addis r9,r11,124
>> c00136dc: 81 29 92 5c lwz r9,-28068(r9)
c00136e0: 7d 36 fb a6 mtspr 1014,r9
c00136e4: 7c 00 04 ac hwsync
c00136e8: 4c 00 01 2c isync
c00136ec: 3d 2b 00 7c addis r9,r11,124
c00136f0: 81 29 92 60 lwz r9,-28064(r9)
c00136f4: 7d 31 fb a6 mtspr 1009,r9
c00136f8: 48 00 19 c4 b c00150bc <transfer_to_handler_cont>
c00136fc: 00 00 00 00 .long 0x0
Can you try the change below (won't work anymore without
CONFIG_VMAP_STACK, will fix it properly later when you confirm it is OK).
diff --git a/arch/powerpc/kernel/idle_6xx.S b/arch/powerpc/kernel/idle_6xx.S
index 0ffdd18b9f26..7be8a0f3fac8 100644
--- a/arch/powerpc/kernel/idle_6xx.S
+++ b/arch/powerpc/kernel/idle_6xx.S
@@ -166,7 +166,7 @@ BEGIN_FTR_SECTION
mfspr r9,SPRN_HID0
andis. r9,r9,HID0_NAP@h
beq 1f
- addis r9,r11,(nap_save_msscr0-KERNELBASE)@ha
+ addis r9,r11,nap_save_msscr0@ha
lwz r9,nap_save_msscr0@l(r9)
mtspr SPRN_MSSCR0, r9
sync
@@ -174,7 +174,7 @@ BEGIN_FTR_SECTION
1:
END_FTR_SECTION_IFSET(CPU_FTR_NAP_DISABLE_L2_PR)
BEGIN_FTR_SECTION
- addis r9,r11,(nap_save_hid1-KERNELBASE)@ha
+ addis r9,r11,nap_save_hid1@ha
lwz r9,nap_save_hid1@l(r9)
mtspr SPRN_HID1, r9
END_FTR_SECTION_IFSET(CPU_FTR_DUAL_PLL_750FX)
Thanks
Christophe
^ permalink raw reply related
* Kernel (little-endian) crashing on POWER8 on heavy PowerKVM load
From: John Paul Adrian Glaubitz @ 2020-02-13 12:35 UTC (permalink / raw)
To: linuxppc-dev
Cc: Anatoly Pugachev, debian-powerpc@lists.debian.org, James Clarke
Hello!
We have an IBM POWER server (8247-42L) running Linux kernel 5.4.13 on Debian unstable
hosting a big-endian ppc64 virtual machine running the same kernel in big-endian
mode.
When building OpenJDK-11 on the big-endian VM, the testsuite crashes the *host* system
with the following kernel backtrace. The problem reproduces both with kernel 4.19.98
as well as 5.4.13.
Backtrace has been attached at the end of this mail.
Thanks,
Adrian
watson login: [17667518570.438744] BUG: Unable to handle kernel data access at 0xc000000002bfd038
[17667518570.438772] Faulting instruction address: 0xc00000000017a778
[17667518570.438777] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438781] Faulting instruction address: 0xc0000000002659a0
[17667518570.438785] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438789] Faulting instruction address: 0xc0000000002659a0
[17667518570.438793] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438797] Faulting instruction address: 0xc0000000002659a0
[17667518570.438801] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438804] Faulting instruction address: 0xc0000000002659a0
[17667518570.438808] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438812] Faulting instruction address: 0xc0000000002659a0
[17667518570.438816] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438820] Faulting instruction address: 0xc0000000002659a0
[17667518570.438824] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438828] Faulting instruction address: 0xc0000000002659a0
[17667518570.438832] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438836] Faulting instruction address: 0xc0000000002659a0
[17667518570.438840] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438843] Faulting instruction address: 0xc0000000002659a0
[17667518570.438848] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438851] Faulting instruction address: 0xc0000000002659a0
[17667518570.438855] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438859] Faulting instruction address: 0xc0000000002659a0
[17667518570.438863] Thread overran stack, or stack corrupted
[17667518570.438867] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438870] Faulting instruction address: 0xc0000000002659a0
[17667518570.438874] Thread overran stack, or stack corrupted
[17667518570.438877] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438881] Faulting instruction address: 0xc0000000002659a0
[17667518570.438884] Thread overran stack, or stack corrupted
[17667518570.438887] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438891] Faulting instruction address: 0xc0000000002659a0
[17667518570.438894] Thread overran stack, or stack corrupted
[17667518570.438898] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438902] Faulting instruction address: 0xc0000000002659a0
[17667518570.438905] Thread overran stack, or stack corrupted
[17667518570.438908] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438912] Faulting instruction address: 0xc0000000002659a0
[17667518570.438915] Thread overran stack, or stack corrupted
[17667518570.438919] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438922] Faulting instruction address: 0xc0000000002659a0
[17667518570.438926] Thread overran stack, or stack corrupted
[17667518570.438929] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438933] Faulting instruction address: 0xc0000000002659a0
[17667518570.438936] Thread overran stack, or stack corrupted
[17667518570.438940] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438944] Faulting instruction address: 0xc0000000002659a0
[17667518570.438947] Thread overran stack, or stack corrupted
[17667518570.438950] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438954] Faulting instruction address: 0xc0000000002659a0
[17667518570.438957] Thread overran stack, or stack corrupted
[17667518570.438961] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438965] Faulting instruction address: 0xc0000000002659a0
[17667518570.438968] Thread overran stack, or stack corrupted
[17667518570.438972] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438976] Faulting instruction address: 0xc0000000002659a0
[17667518570.438979] Thread overran stack, or stack corrupted
[17667518570.438982] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438986] Faulting instruction address: 0xc0000000002659a0
[17667518570.438989] Thread overran stack, or stack corrupted
[17667518570.438993] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.438996] Faulting instruction address: 0xc0000000002659a0
[17667518570.438999] Thread overran stack, or stack corrupted
[17667518570.439003] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.439007] Faulting instruction address: 0xc0000000002659a0
[17667518570.439010] Thread overran stack, or stack corrupted
[17667518570.439014] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.439018] Faulting instruction address: 0xc0000000002659a0
[17667518570.439022] Thread overran stack, or stack corrupted
[17667518570.439026] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.439030] Faulting instruction address: 0xc0000000002659a0
[17667518570.439033] Thread overran stack, or stack corrupted
[17667518570.439036] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.439040] Faulting instruction address: 0xc0000000002659a0
[17667518570.439043] Thread overran stack, or stack corrupted
[17667518570.439047] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.439051] Faulting instruction address: 0xc0000000002659a0
[17667518570.439054] Thread overran stack, or stack corrupted
[ 8142.397845] kernel tried to execute exec-protected page (c000000fe3117a00) - exploit attempt? (uid: 64055)
[17667518570.439062] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.439065] Faulting instruction address: 0xc0000000002659a0
[ 8142.397862] BUG: Unable to handle kernel instruction fetch
[17667518570.439080] Thread overran stack, or stack corrupted
[17667518570.439083] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.397872] Faulting instruction address: 0xc000000fe3117a00
[17667518570.439090] Faulting instruction address: 0xc0000000002659a0
[17667518570.439092] Thread overran stack, or stack corrupted
[ 8142.397883] Oops: Kernel access of bad area, sig: 11 [#1]
[17667518570.439102] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.397894] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
[ 8142.397898] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E)
[17667518570.439123] Faulting instruction address: 0xc0000000002659a0
[ 8142.397909] nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E)
[17667518570.439132] Thread overran stack, or stack corrupted
[ 8142.397918] nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E)
[17667518570.439142] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.397927] nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E)
[17667518570.439151] Faulting instruction address: 0xc0000000002659a0
[ 8142.397937] vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E)
[17667518570.439160] Thread overran stack, or stack corrupted
[ 8142.397945] powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E)
[17667518570.439170] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.397956] libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E)
[17667518570.439181] Faulting instruction address: 0xc0000000002659a0
[ 8142.397967] jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E)
[17667518570.439189] Thread overran stack, or stack corrupted
[ 8142.397975] btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E)
[17667518570.439197] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.397983] async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E)
[17667518570.439207] Faulting instruction address: 0xc0000000002659a0
[ 8142.397992] raid1(E) raid0(E) multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E)
[17667518570.439215] Thread overran stack, or stack corrupted
[ 8142.398000] e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8142.398011] CPU: 48 PID: 2571 Comm: CPU 0/KVM Tainted: G E 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8142.398014] NIP: c000000fe3117a00 LR: c000000000196b9c CTR: c000000fe3117a00
[17667518570.439234] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.398026] REGS: c000000fe315f4c0 TRAP: 0400 Tainted: G E (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[17667518570.439243] Faulting instruction address: 0xc0000000002659a0
[17667518570.439245] Thread overran stack, or stack corrupted
[ 8142.398038] MSR: 9000000010009033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 28448484 XER: 00000000
[ 8142.398046] CFAR: c000000000196b98 IRQMASK: 1
[ 8142.398046] GPR00: c000000000196e0c c000000fe315f750 c0000000012e0800 c000000fe31179c0
[ 8142.398046] GPR04: 0000000000000003 0000000000000000 0000000000000000 0000000000000000
[ 8142.398046] GPR08: c000000fe315f7f0 c000000fe3117a00 0000000080000030 c0080000082bcd80
[ 8142.398046] GPR12: c000000fe3117a00 c000000fffff5a00 0000000000000000 0000000000000008
[ 8142.398046] GPR16: c0000000013a5c18 c000000ff1035e00 c000000fe315f8e8 0000000000000001
[ 8142.398046] GPR20: 0000000000000000 c000000fe315f8e8 c000000fe31179c0 0000000000000000
[ 8142.398046] GPR24: c000000fe315f7f0 0000000000000001 0000000000000000 0000000000000003
[ 8142.398046] GPR28: 0000000000000000 c000000fedc6e750 0000000000000010 c000000fe311f8d0
[ 8142.398079] NIP [c000000fe3117a00] 0xc000000fe3117a00
[ 8142.398087] LR [c000000000196b9c] __wake_up_common+0xcc/0x290
[17667518570.439321] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.398109] Call Trace:
[17667518570.439328] Faulting instruction address: 0xc0000000002659a0
[17667518570.439330] Thread overran stack, or stack corrupted
[ 8142.398122] [c000000fe315f750] [c000000000196b9c] __wake_up_common+0xcc/0x290 (unreliable)
[ 8142.398127] [c000000fe315f7d0] [c000000000196e0c] __wake_up_common_lock+0xac/0x110
[ 8142.398134] [c000000fe315f850] [c0080000082a9760] kvmppc_run_core+0x12f8/0x18c0 [kvm_hv]
[ 8142.398140] [c000000fe315fa10] [c0080000082acf14] kvmppc_vcpu_run_hv+0x62c/0xb20 [kvm_hv]
[ 8142.398149] [c000000fe315fae0] [c0080000081098cc] kvmppc_vcpu_run+0x34/0x48 [kvm]
[ 8142.398158] [c000000fe315fb00] [c00800000810587c] kvm_arch_vcpu_ioctl_run+0x2f4/0x400 [kvm]
[ 8142.398166] [c000000fe315fb90] [c0080000080f7ac8] kvm_vcpu_ioctl+0x340/0x7d0 [kvm]
[ 8142.398172] [c000000fe315fd00] [c000000000445410] do_vfs_ioctl+0xe0/0xac0
[ 8142.398176] [c000000fe315fdb0] [c000000000445eb4] ksys_ioctl+0xc4/0x110
[ 8142.398180] [c000000fe315fe00] [c000000000445f28] sys_ioctl+0x28/0x80
[ 8142.398184] [c000000fe315fe20] [c00000000000b9c8] system_call+0x5c/0x68
[ 8142.398186] Instruction dump:
[17667518570.439406] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.398196] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[ 8142.398200] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[ 8142.398206] ---[ end trace 10787fb41cbf2532 ]---
[17667518570.439424] Faulting instruction address: 0xc0000000002659a0
[17667518570.439425] Thread overran stack, or stack corrupted
[17667518570.441146] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441150] Faulting instruction address: 0xc0000000002659a0
[17667518570.441154] Thread overran stack, or stack corrupted
[17667518570.441157] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441161] Faulting instruction address: 0xc0000000002659a0
[17667518570.441164] Thread overran stack, or stack corrupted
[17667518570.441168] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441172] Faulting instruction address: 0xc0000000002659a0
[17667518570.441175] Thread overran stack, or stack corrupted
[17667518570.441179] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441183] Faulting instruction address: 0xc0000000002659a0
[17667518570.441187] Thread overran stack, or stack corrupted
[17667518570.441190] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441194] Faulting instruction address: 0xc0000000002659a0
[17667518570.441197] Thread overran stack, or stack corrupted
[17667518570.441201] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441205] Faulting instruction address: 0xc0000000002659a0
[17667518570.441208] Thread overran stack, or stack corrupted
[17667518570.441212] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441215] Faulting instruction address: 0xc0000000002659a0
[17667518570.441219] Thread overran stack, or stack corrupted
[17667518570.441222] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441226] Faulting instruction address: 0xc0000000002659a0
[17667518570.441229] Thread overran stack, or stack corrupted
[17667518570.441233] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441237] Faulting instruction address: 0xc0000000002659a0
[17667518570.441240] Thread overran stack, or stack corrupted
[17667518570.441243] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441247] Faulting instruction address: 0xc0000000002659a0
[17667518570.441250] Thread overran stack, or stack corrupted
[17667518570.441254] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441258] Faulting instruction address: 0xc0000000002659a0
[17667518570.441261] Thread overran stack, or stack corrupted
[17667518570.441264] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441268] Faulting instruction address: 0xc0000000002659a0
[17667518570.441271] Thread overran stack, or stack corrupted
[17667518570.441275] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441279] Faulting instruction address: 0xc0000000002659a0
[17667518570.441282] Thread overran stack, or stack corrupted
[17667518570.441285] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441289] Faulting instruction address: 0xc0000000002659a0
[17667518570.441292] Thread overran stack, or stack corrupted
[17667518570.441295] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441299] Faulting instruction address: 0xc0000000002659a0
[17667518570.441302] Thread overran stack, or stack corrupted
[17667518570.441306] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441310] Faulting instruction address: 0xc0000000002659a0
[17667518570.441313] Thread overran stack, or stack corrupted
[17667518570.441316] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441320] Faulting instruction address: 0xc0000000002659a0
[17667518570.441323] Thread overran stack, or stack corrupted
[17667518570.441326] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441330] Faulting instruction address: 0xc0000000002659a0
[17667518570.441334] Thread overran stack, or stack corrupted
[17667518570.441337] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441341] Faulting instruction address: 0xc0000000002659a0
[17667518570.441344] Thread overran stack, or stack corrupted
[17667518570.441347] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441351] Faulting instruction address: 0xc0000000002659a0
[17667518570.441354] Thread overran stack, or stack corrupted
[17667518570.441358] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441362] Faulting instruction address: 0xc0000000002659a0
[17667518570.441365] Thread overran stack, or stack corrupted
[17667518570.441368] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441372] Faulting instruction address: 0xc0000000002659a0
[17667518570.441376] Thread overran stack, or stack corrupted
[17667518570.441380] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441383] Faulting instruction address: 0xc0000000002659a0
[17667518570.441386] Thread overran stack, or stack corrupted
[17667518570.441390] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441394] Faulting instruction address: 0xc0000000002659a0
[17667518570.441397] Thread overran stack, or stack corrupted
[17667518570.441400] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441404] Faulting instruction address: 0xc0000000002659a0
[17667518570.441407] Thread overran stack, or stack corrupted
[17667518570.441411] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441415] Faulting instruction address: 0xc0000000002659a0
[17667518570.441418] Thread overran stack, or stack corrupted
[17667518570.441421] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441425] Faulting instruction address: 0xc0000000002659a0
[17667518570.441428] Thread overran stack, or stack corrupted
[17667518570.441432] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441435] Faulting instruction address: 0xc0000000002659a0
[17667518570.441439] Thread overran stack, or stack corrupted
[17667518570.441442] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441446] Faulting instruction address: 0xc0000000002659a0
[17667518570.441449] Thread overran stack, or stack corrupted
[17667518570.441453] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441456] Faulting instruction address: 0xc0000000002659a0
[17667518570.441460] Thread overran stack, or stack corrupted
[17667518570.441463] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441467] Faulting instruction address: 0xc0000000002659a0
[17667518570.441470] Thread overran stack, or stack corrupted
[17667518570.441473] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441477] Faulting instruction address: 0xc0000000002659a0
[17667518570.441480] Thread overran stack, or stack corrupted
[17667518570.441484] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441488] Faulting instruction address: 0xc0000000002659a0
[17667518570.441491] Thread overran stack, or stack corrupted
[17667518570.441495] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441499] Faulting instruction address: 0xc0000000002659a0
[17667518570.441502] Thread overran stack, or stack corrupted
[17667518570.441506] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441510] Faulting instruction address: 0xc0000000002659a0
[17667518570.441513] Thread overran stack, or stack corrupted
[17667518570.441517] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441520] Faulting instruction address: 0xc0000000002659a0
[17667518570.441523] Thread overran stack, or stack corrupted
[17667518570.441527] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441531] Faulting instruction address: 0xc0000000002659a0
[17667518570.441534] Thread overran stack, or stack corrupted
[17667518570.441537] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441541] Faulting instruction address: 0xc0000000002659a0
[17667518570.441544] Thread overran stack, or stack corrupted
[17667518570.441548] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441552] Faulting instruction address: 0xc0000000002659a0
[17667518570.441555] Thread overran stack, or stack corrupted
[17667518570.441558] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441562] Faulting instruction address: 0xc0000000002659a0
[17667518570.441565] Thread overran stack, or stack corrupted
[17667518570.441569] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441573] Faulting instruction address: 0xc0000000002659a0
[17667518570.441576] Thread overran stack, or stack corrupted
[17667518570.441580] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441583] Faulting instruction address: 0xc0000000002659a0
[17667518570.441587] Thread overran stack, or stack corrupted
[17667518570.441590] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441594] Faulting instruction address: 0xc0000000002659a0
[17667518570.441597] Thread overran stack, or stack corrupted
[17667518570.441600] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441604] Faulting instruction address: 0xc0000000002659a0
[17667518570.441607] Thread overran stack, or stack corrupted
[17667518570.441611] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441615] Faulting instruction address: 0xc0000000002659a0
[17667518570.441618] Thread overran stack, or stack corrupted
[17667518570.441622] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441625] Faulting instruction address: 0xc0000000002659a0
[17667518570.441628] Thread overran stack, or stack corrupted
[17667518570.441632] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441636] Faulting instruction address: 0xc0000000002659a0
[17667518570.441639] Thread overran stack, or stack corrupted
[17667518570.441642] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441647] Faulting instruction address: 0xc0000000002659a0
[17667518570.441650] Thread overran stack, or stack corrupted
[17667518570.441653] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441657] Faulting instruction address: 0xc0000000002659a0
[17667518570.441661] Thread overran stack, or stack corrupted
[17667518570.441664] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441669] Faulting instruction address: 0xc0000000002659a0
[17667518570.441672] Thread overran stack, or stack corrupted
[ 8142.400457]
[17667518570.441676] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441682] Faulting instruction address: 0xc0000000002659a0
[17667518570.441686] Thread overran stack, or stack corrupted
[17667518570.441689] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441693] Faulting instruction address: 0xc0000000002659a0
[17667518570.441697] Thread overran stack, or stack corrupted
[17667518570.441700] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441704] Faulting instruction address: 0xc0000000002659a0
[17667518570.441708] Thread overran stack, or stack corrupted
[17667518570.441711] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441715] Faulting instruction address: 0xc0000000002659a0
[17667518570.441718] Thread overran stack, or stack corrupted
[17667518570.441825] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441829] Faulting instruction address: 0xc0000000002659a0
[17667518570.441832] Thread overran stack, or stack corrupted
[17667518570.441836] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441840] Faulting instruction address: 0xc0000000002659a0
[17667518570.441843] Thread overran stack, or stack corrupted
[17667518570.441846] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441850] Faulting instruction address: 0xc0000000002659a0
[17667518570.441853] Thread overran stack, or stack corrupted
[17667518570.441857] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441861] Faulting instruction address: 0xc0000000002659a0
[17667518570.441864] Thread overran stack, or stack corrupted
[17667518570.441867] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441871] Faulting instruction address: 0xc0000000002659a0
[17667518570.441874] Thread overran stack, or stack corrupted
[17667518570.441878] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441881] Faulting instruction address: 0xc0000000002659a0
[17667518570.441885] Thread overran stack, or stack corrupted
[17667518570.441888] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441892] Faulting instruction address: 0xc0000000002659a0
[17667518570.441895] Thread overran stack, or stack corrupted
[17667518570.441898] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441902] Faulting instruction address: 0xc0000000002659a0
[17667518570.441905] Thread overran stack, or stack corrupted
[17667518570.441909] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441913] Faulting instruction address: 0xc0000000002659a0
[17667518570.441916] Thread overran stack, or stack corrupted
[17667518570.441920] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441924] Faulting instruction address: 0xc0000000002659a0
[17667518570.441928] Thread overran stack, or stack corrupted
[17667518570.441932] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441936] Faulting instruction address: 0xc0000000002659a0
[17667518570.441939] Thread overran stack, or stack corrupted
[17667518570.441943] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.441947] Faulting instruction address: 0xc0000000002659a0
[ 8142.400735] BUG: Unable to handle kernel instruction fetch (NULL pointer?)
[ 8142.400738] Faulting instruction address: 0x00000000
[17667518570.441956] Thread overran stack, or stack corrupted
[17667518570.441960] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.400758] Oops: Kernel access of bad area, sig: 11 [#2]
[17667518570.441976] Faulting instruction address: 0xc0000000002659a0
[17667518570.441978] Thread overran stack, or stack corrupted
[ 8142.400769] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
[ 8142.400771] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E)
[17667518570.441997] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.400783] nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E)
[17667518570.442008] Faulting instruction address: 0xc0000000002659a0
[ 8142.400794] llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E)
[17667518570.442019] Thread overran stack, or stack corrupted
[ 8142.400805] iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E)
[17667518570.442123] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.400907] ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E) multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E)
[17667518570.442143] Faulting instruction address: 0xc0000000002659a0
[ 8142.400929] ptp(E) pps_core(E) ipr(E) usb_common(E)
[17667518570.442155] Thread overran stack, or stack corrupted
[17667518570.442157] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.400947] CPU: 152 PID: 2585 Comm: CPU 14/KVM Tainted: G D E 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8142.400949] NIP: 0000000000000000 LR: c000000000196b9c CTR: 0000000000000000
[17667518570.442167] Faulting instruction address: 0xc0000000002659a0
[17667518570.442169] Thread overran stack, or stack corrupted
[ 8142.400960] REGS: c000000fe31234c0 TRAP: 0400 Tainted: G D E (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[17667518570.442181] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.400969] MSR: 9000000040009033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 28448488 XER: 00000000
[ 8142.400977] CFAR: c00000000000e5c8 IRQMASK: 1
[ 8142.400977] GPR00: c000000000196e0c c000000fe3123750 c0000000012e0800 c000000fe31039c0
[ 8142.400977] GPR04: 0000000000000003 0000000000000000 0000000000000000 0000000000000000
[ 8142.400977] GPR08: c000000fe31237f0 0000000000000000 0000000080000098 c0080000082bcd80
[ 8142.400977] GPR12: 0000000000000000 c000001ffff6df80 0000000000000000 0000000000000008
[ 8142.400977] GPR16: c0000000013a5c18 c000000ff103a500 c000000fe31238e8 0000000000000001
[ 8142.400977] GPR20: 0000000000000000 c000000fe31238e8 c000000fe31039c0 0000000000000000
[ 8142.400977] GPR24: c000000fe31237f0 0000000000000001 0000000000000000 0000000000000003
[ 8142.400977] GPR28: 0000000000000000 c000000fe0f18c60 0000000000000000 c000000000c21fb8
[17667518570.442219] Faulting instruction address: 0xc0000000002659a0
[17667518570.442220] Thread overran stack, or stack corrupted
[ 8142.401010] NIP [0000000000000000] 0x0
[ 8142.401017] LR [c000000000196b9c] __wake_up_common+0xcc/0x290
[ 8142.401020] Call Trace:
[17667518570.442258] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.401047] [c000000fe3123750] [c0000000013a5c18] 0xc0000000013a5c18 (unreliable)
[ 8142.401051] [c000000fe31237d0] [c000000000196e0c] __wake_up_common_lock+0xac/0x110
[ 8142.401058] [c000000fe3123850] [c0080000082a9760] kvmppc_run_core+0x12f8/0x18c0 [kvm_hv]
[ 8142.401063] [c000000fe3123a10] [c0080000082acf14] kvmppc_vcpu_run_hv+0x62c/0xb20 [kvm_hv]
[ 8142.401071] [c000000fe3123ae0] [c0080000081098cc] kvmppc_vcpu_run+0x34/0x48 [kvm]
[ 8142.401077] [c000000fe3123b00] [c00800000810587c] kvm_arch_vcpu_ioctl_run+0x2f4/0x400 [kvm]
[ 8142.401083] [c000000fe3123b90] [c0080000080f7ac8] kvm_vcpu_ioctl+0x340/0x7d0 [kvm]
[ 8142.401088] [c000000fe3123d00] [c000000000445410] do_vfs_ioctl+0xe0/0xac0
[ 8142.401091] [c000000fe3123db0] [c000000000445eb4] ksys_ioctl+0xc4/0x110
[ 8142.401107] [c000000fe3123e00] [c000000000445f28] sys_ioctl+0x28/0x80
[ 8142.401111] [c000000fe3123e20] [c00000000000b9c8] system_call+0x5c/0x68
[ 8142.401114] Instruction dump:
[17667518570.442334] Faulting instruction address: 0xc0000000002659a0
[17667518570.442421] Thread overran stack, or stack corrupted
[ 8142.401210] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[17667518570.442431] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.401220] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[17667518570.442439] Faulting instruction address: 0xc0000000002659a0
[17667518570.442441] Thread overran stack, or stack corrupted
[ 8142.401230] ---[ end trace 10787fb41cbf2533 ]---
[17667518570.442450] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444058] Faulting instruction address: 0xc0000000002659a0
[17667518570.444062] Thread overran stack, or stack corrupted
[17667518570.444065] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444069] Faulting instruction address: 0xc0000000002659a0
[17667518570.444072] Thread overran stack, or stack corrupted
[17667518570.444077] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444081] Faulting instruction address: 0xc0000000002659a0
[17667518570.444084] Thread overran stack, or stack corrupted
[17667518570.444087] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444091] Faulting instruction address: 0xc0000000002659a0
[17667518570.444095] Thread overran stack, or stack corrupted
[17667518570.444098] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444103] Faulting instruction address: 0xc0000000002659a0
[17667518570.444106] Thread overran stack, or stack corrupted
[17667518570.444110] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444113] Faulting instruction address: 0xc0000000002659a0
[17667518570.444117] Thread overran stack, or stack corrupted
[17667518570.444120] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444124] Faulting instruction address: 0xc0000000002659a0
[17667518570.444127] Thread overran stack, or stack corrupted
[17667518570.444131] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444134] Faulting instruction address: 0xc0000000002659a0
[17667518570.444138] Thread overran stack, or stack corrupted
[17667518570.444141] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444145] Faulting instruction address: 0xc0000000002659a0
[17667518570.444148] Thread overran stack, or stack corrupted
[17667518570.444152] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444155] Faulting instruction address: 0xc0000000002659a0
[17667518570.444158] Thread overran stack, or stack corrupted
[17667518570.444162] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444166] Faulting instruction address: 0xc0000000002659a0
[17667518570.444169] Thread overran stack, or stack corrupted
[17667518570.444173] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444177] Faulting instruction address: 0xc0000000002659a0
[17667518570.444180] Thread overran stack, or stack corrupted
[17667518570.444184] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444187] Faulting instruction address: 0xc0000000002659a0
[17667518570.444191] Thread overran stack, or stack corrupted
[17667518570.444194] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444198] Faulting instruction address: 0xc0000000002659a0
[17667518570.444201] Thread overran stack, or stack corrupted
[17667518570.444205] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444208] Faulting instruction address: 0xc0000000002659a0
[17667518570.444211] Thread overran stack, or stack corrupted
[17667518570.444215] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444219] Faulting instruction address: 0xc0000000002659a0
[17667518570.444222] Thread overran stack, or stack corrupted
[17667518570.444225] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444229] Faulting instruction address: 0xc0000000002659a0
[17667518570.444232] Thread overran stack, or stack corrupted
[17667518570.444236] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444240] Faulting instruction address: 0xc0000000002659a0
[17667518570.444243] Thread overran stack, or stack corrupted
[17667518570.444246] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444250] Faulting instruction address: 0xc0000000002659a0
[ 8142.403097]
[17667518570.444315] Thread overran stack, or stack corrupted
[17667518570.444317] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444326] Faulting instruction address: 0xc0000000002659a0
[17667518570.444329] Thread overran stack, or stack corrupted
[17667518570.444333] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444337] Faulting instruction address: 0xc0000000002659a0
[17667518570.444340] Thread overran stack, or stack corrupted
[17667518570.444343] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444347] Faulting instruction address: 0xc0000000002659a0
[17667518570.444350] Thread overran stack, or stack corrupted
[17667518570.444354] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444357] Faulting instruction address: 0xc0000000002659a0
[17667518570.444361] Thread overran stack, or stack corrupted
[17667518570.444364] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444368] Faulting instruction address: 0xc0000000002659a0
[17667518570.444372] Thread overran stack, or stack corrupted
[17667518570.444375] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444379] Faulting instruction address: 0xc0000000002659a0
[17667518570.444382] Thread overran stack, or stack corrupted
[17667518570.444386] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444390] Faulting instruction address: 0xc0000000002659a0
[17667518570.444393] Thread overran stack, or stack corrupted
[17667518570.444396] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444400] Faulting instruction address: 0xc0000000002659a0
[17667518570.444403] Thread overran stack, or stack corrupted
[17667518570.444407] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444411] Faulting instruction address: 0xc0000000002659a0
[17667518570.444414] Thread overran stack, or stack corrupted
[17667518570.444417] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444421] Faulting instruction address: 0xc0000000002659a0
[17667518570.444424] Thread overran stack, or stack corrupted
[17667518570.444428] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444431] Faulting instruction address: 0xc0000000002659a0
[17667518570.444434] Thread overran stack, or stack corrupted
[17667518570.444438] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444442] Faulting instruction address: 0xc0000000002659a0
[17667518570.444445] Thread overran stack, or stack corrupted
[17667518570.444448] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444452] Faulting instruction address: 0xc0000000002659a0
[17667518570.444455] Thread overran stack, or stack corrupted
[17667518570.444496] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444500] Faulting instruction address: 0xc0000000002659a0
[17667518570.444503] Thread overran stack, or stack corrupted
[17667518570.444507] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444511] Faulting instruction address: 0xc0000000002659a0
[17667518570.444514] Thread overran stack, or stack corrupted
[17667518570.444518] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444521] Faulting instruction address: 0xc0000000002659a0
[17667518570.444525] Thread overran stack, or stack corrupted
[17667518570.444528] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444532] Faulting instruction address: 0xc0000000002659a0
[17667518570.444536] Thread overran stack, or stack corrupted
[17667518570.444539] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444543] Faulting instruction address: 0xc0000000002659a0
[17667518570.444547] Thread overran stack, or stack corrupted
[17667518570.444550] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444554] Faulting instruction address: 0xc0000000002659a0
[17667518570.444557] Thread overran stack, or stack corrupted
[17667518570.444561] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444565] Faulting instruction address: 0xc0000000002659a0
[17667518570.444568] Thread overran stack, or stack corrupted
[17667518570.444571] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444575] Faulting instruction address: 0xc0000000002659a0
[17667518570.444578] Thread overran stack, or stack corrupted
[17667518570.444582] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444585] Faulting instruction address: 0xc0000000002659a0
[17667518570.444589] Thread overran stack, or stack corrupted
[17667518570.444592] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444596] Faulting instruction address: 0xc0000000002659a0
[17667518570.444627] Thread overran stack, or stack corrupted
[17667518570.444630] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444634] Faulting instruction address: 0xc0000000002659a0
[17667518570.444638] Thread overran stack, or stack corrupted
[17667518570.444641] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444646] Faulting instruction address: 0xc0000000002659a0
[17667518570.444649] Thread overran stack, or stack corrupted
[17667518570.444653] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444656] Faulting instruction address: 0xc0000000002659a0
[17667518570.444659] Thread overran stack, or stack corrupted
[17667518570.444663] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444667] Faulting instruction address: 0xc0000000002659a0
[17667518570.444670] Thread overran stack, or stack corrupted
[17667518570.444673] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444677] Faulting instruction address: 0xc0000000002659a0
[17667518570.444680] Thread overran stack, or stack corrupted
[17667518570.444684] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444688] Faulting instruction address: 0xc0000000002659a0
[17667518570.444691] Thread overran stack, or stack corrupted
[17667518570.444695] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444698] Faulting instruction address: 0xc0000000002659a0
[17667518570.444721] Thread overran stack, or stack corrupted
[17667518570.444724] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444728] Faulting instruction address: 0xc0000000002659a0
[17667518570.444731] Thread overran stack, or stack corrupted
[17667518570.444735] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444739] Faulting instruction address: 0xc0000000002659a0
[17667518570.444742] Thread overran stack, or stack corrupted
[17667518570.444745] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444749] Faulting instruction address: 0xc0000000002659a0
[17667518570.444753] Thread overran stack, or stack corrupted
[17667518570.444756] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444760] Faulting instruction address: 0xc0000000002659a0
[17667518570.444763] Thread overran stack, or stack corrupted
[17667518570.444766] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444770] Faulting instruction address: 0xc0000000002659a0
[17667518570.444773] Thread overran stack, or stack corrupted
[17667518570.444777] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444780] Faulting instruction address: 0xc0000000002659a0
[17667518570.444784] Thread overran stack, or stack corrupted
[17667518570.444805] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444809] Faulting instruction address: 0xc0000000002659a0
[17667518570.444812] Thread overran stack, or stack corrupted
[17667518570.444816] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444820] Faulting instruction address: 0xc0000000002659a0
[17667518570.444823] Thread overran stack, or stack corrupted
[17667518570.444826] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444830] Faulting instruction address: 0xc0000000002659a0
[17667518570.444833] Thread overran stack, or stack corrupted
[17667518570.444837] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444841] Faulting instruction address: 0xc0000000002659a0
[17667518570.444844] Thread overran stack, or stack corrupted
[17667518570.444847] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444851] Faulting instruction address: 0xc0000000002659a0
[17667518570.444854] Thread overran stack, or stack corrupted
[17667518570.444858] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444861] Faulting instruction address: 0xc0000000002659a0
[17667518570.444880] Thread overran stack, or stack corrupted
[17667518570.444884] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444888] Faulting instruction address: 0xc0000000002659a0
[17667518570.444891] Thread overran stack, or stack corrupted
[17667518570.444895] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444898] Faulting instruction address: 0xc0000000002659a0
[17667518570.444902] Thread overran stack, or stack corrupted
[17667518570.444905] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444909] Faulting instruction address: 0xc0000000002659a0
[17667518570.444912] Thread overran stack, or stack corrupted
[17667518570.444916] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444920] Faulting instruction address: 0xc0000000002659a0
[17667518570.444923] Thread overran stack, or stack corrupted
[17667518570.444927] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444944] Faulting instruction address: 0xc0000000002659a0
[17667518570.444947] Thread overran stack, or stack corrupted
[17667518570.444951] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444955] Faulting instruction address: 0xc0000000002659a0
[17667518570.444958] Thread overran stack, or stack corrupted
[17667518570.444961] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444965] Faulting instruction address: 0xc0000000002659a0
[17667518570.444968] Thread overran stack, or stack corrupted
[17667518570.444972] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444976] Faulting instruction address: 0xc0000000002659a0
[17667518570.444979] Thread overran stack, or stack corrupted
[17667518570.444982] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.444998] Faulting instruction address: 0xc0000000002659a0
[17667518570.445001] Thread overran stack, or stack corrupted
[17667518570.445005] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445009] Faulting instruction address: 0xc0000000002659a0
[17667518570.445012] Thread overran stack, or stack corrupted
[17667518570.445016] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445020] Faulting instruction address: 0xc0000000002659a0
[17667518570.445024] Thread overran stack, or stack corrupted
[17667518570.445027] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445031] Faulting instruction address: 0xc0000000002659a0
[17667518570.445035] Thread overran stack, or stack corrupted
[17667518570.445049] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445053] Faulting instruction address: 0xc0000000002659a0
[17667518570.445056] Thread overran stack, or stack corrupted
[17667518570.445060] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445063] Faulting instruction address: 0xc0000000002659a0
[17667518570.445067] Thread overran stack, or stack corrupted
[17667518570.445070] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445074] Faulting instruction address: 0xc0000000002659a0
[17667518570.445077] Thread overran stack, or stack corrupted
[17667518570.445081] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445095] Faulting instruction address: 0xc0000000002659a0
[17667518570.445099] Thread overran stack, or stack corrupted
[17667518570.445103] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445107] Faulting instruction address: 0xc0000000002659a0
[17667518570.445110] Thread overran stack, or stack corrupted
[17667518570.445114] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445118] Faulting instruction address: 0xc0000000002659a0
[17667518570.445122] Thread overran stack, or stack corrupted
[17667518570.445132] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445136] Faulting instruction address: 0xc0000000002659a0
[17667518570.445140] Thread overran stack, or stack corrupted
[17667518570.445143] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445147] Faulting instruction address: 0xc0000000002659a0
[17667518570.445151] Thread overran stack, or stack corrupted
[17667518570.445154] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445158] Faulting instruction address: 0xc0000000002659a0
[17667518570.445168] Thread overran stack, or stack corrupted
[17667518570.445172] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445175] Faulting instruction address: 0xc0000000002659a0
[17667518570.445179] Thread overran stack, or stack corrupted
[17667518570.445186] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445191] Faulting instruction address: 0xc0000000002659a0
[17667518570.445194] Thread overran stack, or stack corrupted
[17667518570.445198] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445202] Faulting instruction address: 0xc0000000002659a0
[17667518570.445205] Thread overran stack, or stack corrupted
[17667518570.445215] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445219] Faulting instruction address: 0xc0000000002659a0
[17667518570.445223] Thread overran stack, or stack corrupted
[17667518570.445228] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445232] Faulting instruction address: 0xc0000000002659a0
[17667518570.445236] Thread overran stack, or stack corrupted
[17667518570.445239] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445244] Faulting instruction address: 0xc0000000002659a0
[17667518570.445247] Thread overran stack, or stack corrupted
[17667518570.445258] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445262] Faulting instruction address: 0xc0000000002659a0
[17667518570.445267] Thread overran stack, or stack corrupted
[17667518570.445271] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445276] Faulting instruction address: 0xc0000000002659a0
[17667518570.445279] Thread overran stack, or stack corrupted
[17667518570.445282] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445289] Faulting instruction address: 0xc0000000002659a0
[17667518570.445292] Thread overran stack, or stack corrupted
[17667518570.445296] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445301] Faulting instruction address: 0xc0000000002659a0
[17667518570.445305] Thread overran stack, or stack corrupted
[17667518570.445310] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445314] Faulting instruction address: 0xc0000000002659a0
[17667518570.445317] Thread overran stack, or stack corrupted
[17667518570.445321] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445329] Faulting instruction address: 0xc0000000002659a0
[17667518570.445333] Thread overran stack, or stack corrupted
[17667518570.445339] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445345] Faulting instruction address: 0xc0000000002659a0
[17667518570.445349] Thread overran stack, or stack corrupted
[17667518570.445355] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445359] Faulting instruction address: 0xc0000000002659a0
[17667518570.445363] Thread overran stack, or stack corrupted
[17667518570.445369] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445373] Faulting instruction address: 0xc0000000002659a0
[17667518570.445378] Thread overran stack, or stack corrupted
[17667518570.445382] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445389] Faulting instruction address: 0xc0000000002659a0
[17667518570.445392] Thread overran stack, or stack corrupted
[17667518570.445396] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445400] Faulting instruction address: 0xc0000000002659a0
[17667518570.445406] Thread overran stack, or stack corrupted
[17667518570.445410] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445416] Faulting instruction address: 0xc0000000002659a0
[17667518570.445420] Thread overran stack, or stack corrupted
[17667518570.445427] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445430] Faulting instruction address: 0xc0000000002659a0
[17667518570.445434] Thread overran stack, or stack corrupted
[17667518570.445440] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445445] Faulting instruction address: 0xc0000000002659a0
[17667518570.445451] Thread overran stack, or stack corrupted
[17667518570.445456] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445460] Faulting instruction address: 0xc0000000002659a0
[17667518570.445464] Thread overran stack, or stack corrupted
[17667518570.445468] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445475] Faulting instruction address: 0xc0000000002659a0
[17667518570.445478] Thread overran stack, or stack corrupted
[17667518570.445485] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445490] Faulting instruction address: 0xc0000000002659a0
[17667518570.445495] Thread overran stack, or stack corrupted
[17667518570.445499] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445502] Faulting instruction address: 0xc0000000002659a0
[17667518570.445506] Thread overran stack, or stack corrupted
[17667518570.445515] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445520] Faulting instruction address: 0xc0000000002659a0
[17667518570.445525] Thread overran stack, or stack corrupted
[17667518570.445530] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445534] Faulting instruction address: 0xc0000000002659a0
[17667518570.445538] Thread overran stack, or stack corrupted
[17667518570.445544] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445548] Faulting instruction address: 0xc0000000002659a0
[17667518570.445553] Thread overran stack, or stack corrupted
[17667518570.445558] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445565] Faulting instruction address: 0xc0000000002659a0
[17667518570.445568] Thread overran stack, or stack corrupted
[17667518570.445572] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445579] Faulting instruction address: 0xc0000000002659a0
[17667518570.445582] Thread overran stack, or stack corrupted
[17667518570.445588] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445593] Faulting instruction address: 0xc0000000002659a0
[17667518570.445596] Thread overran stack, or stack corrupted
[17667518570.445600] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445607] Faulting instruction address: 0xc0000000002659a0
[17667518570.445610] Thread overran stack, or stack corrupted
[17667518570.445616] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445622] Faulting instruction address: 0xc0000000002659a0
[17667518570.445626] Thread overran stack, or stack corrupted
[17667518570.445629] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445634] Faulting instruction address: 0xc0000000002659a0
[17667518570.445638] Thread overran stack, or stack corrupted
[17667518570.445643] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445649] Faulting instruction address: 0xc0000000002659a0
[17667518570.445653] Thread overran stack, or stack corrupted
[17667518570.445660] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445665] Faulting instruction address: 0xc0000000002659a0
[17667518570.445669] Thread overran stack, or stack corrupted
[17667518570.445675] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445680] Faulting instruction address: 0xc0000000002659a0
[17667518570.445684] Thread overran stack, or stack corrupted
[17667518570.445689] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445693] Faulting instruction address: 0xc0000000002659a0
[17667518570.445697] Thread overran stack, or stack corrupted
[17667518570.445704] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445707] Faulting instruction address: 0xc0000000002659a0
[17667518570.445711] Thread overran stack, or stack corrupted
[17667518570.445716] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445721] Faulting instruction address: 0xc0000000002659a0
[17667518570.445725] Thread overran stack, or stack corrupted
[17667518570.445729] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445736] Faulting instruction address: 0xc0000000002659a0
[17667518570.445739] Thread overran stack, or stack corrupted
[17667518570.445746] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445751] Faulting instruction address: 0xc0000000002659a0
[17667518570.445756] Thread overran stack, or stack corrupted
[17667518570.445760] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445764] Faulting instruction address: 0xc0000000002659a0
[17667518570.445771] Thread overran stack, or stack corrupted
[17667518570.445775] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445780] Faulting instruction address: 0xc0000000002659a0
[17667518570.445785] Thread overran stack, or stack corrupted
[17667518570.445789] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445794] Faulting instruction address: 0xc0000000002659a0
[17667518570.445797] Thread overran stack, or stack corrupted
[17667518570.445804] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445808] Faulting instruction address: 0xc0000000002659a0
[17667518570.445813] Thread overran stack, or stack corrupted
[17667518570.445817] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445824] Faulting instruction address: 0xc0000000002659a0
[17667518570.445828] Thread overran stack, or stack corrupted
[17667518570.445831] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445839] Faulting instruction address: 0xc0000000002659a0
[17667518570.445842] Thread overran stack, or stack corrupted
[17667518570.445847] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445852] Faulting instruction address: 0xc0000000002659a0
[17667518570.445856] Thread overran stack, or stack corrupted
[17667518570.445859] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445866] Faulting instruction address: 0xc0000000002659a0
[17667518570.445870] Thread overran stack, or stack corrupted
[17667518570.445875] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445881] Faulting instruction address: 0xc0000000002659a0
[17667518570.445885] Thread overran stack, or stack corrupted
[17667518570.445889] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445893] Faulting instruction address: 0xc0000000002659a0
[17667518570.445899] Thread overran stack, or stack corrupted
[17667518570.445903] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445908] Faulting instruction address: 0xc0000000002659a0
[17667518570.445915] Thread overran stack, or stack corrupted
[17667518570.445919] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445924] Faulting instruction address: 0xc0000000002659a0
[17667518570.445927] Thread overran stack, or stack corrupted
[17667518570.445933] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445937] Faulting instruction address: 0xc0000000002659a0
[17667518570.445941] Thread overran stack, or stack corrupted
[17667518570.445945] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445952] Faulting instruction address: 0xc0000000002659a0
[17667518570.445956] Thread overran stack, or stack corrupted
[17667518570.445959] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445967] Faulting instruction address: 0xc0000000002659a0
[17667518570.445970] Thread overran stack, or stack corrupted
[17667518570.445976] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445981] Faulting instruction address: 0xc0000000002659a0
[17667518570.445984] Thread overran stack, or stack corrupted
[17667518570.445988] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.445995] Faulting instruction address: 0xc0000000002659a0
[17667518570.445999] Thread overran stack, or stack corrupted
[17667518570.446004] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446009] Faulting instruction address: 0xc0000000002659a0
[17667518570.446015] Thread overran stack, or stack corrupted
[17667518570.446019] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446023] Faulting instruction address: 0xc0000000002659a0
[17667518570.446030] Thread overran stack, or stack corrupted
[17667518570.446034] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446039] Faulting instruction address: 0xc0000000002659a0
[17667518570.446044] Thread overran stack, or stack corrupted
[17667518570.446047] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446051] Faulting instruction address: 0xc0000000002659a0
[17667518570.446058] Thread overran stack, or stack corrupted
[17667518570.446062] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446067] Faulting instruction address: 0xc0000000002659a0
[17667518570.446071] Thread overran stack, or stack corrupted
[17667518570.446078] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446082] Faulting instruction address: 0xc0000000002659a0
[17667518570.446085] Thread overran stack, or stack corrupted
[17667518570.446092] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446096] Faulting instruction address: 0xc0000000002659a0
[17667518570.446101] Thread overran stack, or stack corrupted
[17667518570.446106] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446111] Faulting instruction address: 0xc0000000002659a0
[17667518570.446114] Thread overran stack, or stack corrupted
[17667518570.446118] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446125] Faulting instruction address: 0xc0000000002659a0
[17667518570.446129] Thread overran stack, or stack corrupted
[17667518570.446135] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446140] Faulting instruction address: 0xc0000000002659a0
[17667518570.446144] Thread overran stack, or stack corrupted
[17667518570.446148] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446152] Faulting instruction address: 0xc0000000002659a0
[17667518570.446157] Thread overran stack, or stack corrupted
[17667518570.446162] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518570.446166] Faulting instruction address: 0xc0000000002659a0
[17667518570.446171] Thread overran stack, or stack corrupted
[17667518570.446177] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.405100] BUG: Unable to handle kernel instruction fetch (NULL pointer?)
[ 8142.406323] kernel tried to execute exec-protected page (c000000ff1f63170) - exploit attempt? (uid: 64055)
[ 8142.406325] BUG: Unable to handle kernel instruction fetch
[ 8142.406327] Faulting instruction address: 0xc000000ff1f63170
[ 8142.406329] Oops: Kernel access of bad area, sig: 11 [#3]
[ 8142.406331] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
[ 8142.406333] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8142.406370] multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8142.406378] CPU: 80 PID: 2576 Comm: CPU 5/KVM Tainted: G D E 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8142.406380] NIP: c000000ff1f63170 LR: c000000ff1f63170 CTR: c0000000001b8a78
[ 8142.406382] REGS: c000000fe31734f0 TRAP: 0400 Tainted: G D E (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[ 8142.406383] MSR: 900000001280b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE> CR: 28448488 XER: 00000000
[ 8142.406387] CFAR: c0000000001b8a8c IRQMASK: 1
[ 8142.406387] GPR00: c000000ff1f63170 c000000fe3173780 c0000000012e0800 c000000fe311b9c0
[ 8142.406387] GPR04: 0000000000000003 0000000000000000 0000000000000000 0000000000000000
[ 8142.406387] GPR08: c000000fe31737f0 c0000000001b8a78 0000000080000050 c0080000082bcd80
[ 8142.406387] GPR12: c0000000001b8a78 c0000017ffffee00 0000000000000000 0000000000000008
[ 8142.406387] GPR16: c0000000013a5c18 c000000ff1f63100 c000000fe31738e8 0000000000000001
[ 8142.406387] GPR20: 0000000000000000 c000000fe31738e8 c000000fe311b9c0 0000000000000000
[ 8142.406387] GPR24: c000000fe31737f0 0000000000000001 0000000000000000 0000000000000003
[ 8142.406387] GPR28: 0000000000000000 c000000fe0f2b1f0 00000000e311b9f0 0000000000000050
[ 8142.406400] NIP [c000000ff1f63170] 0xc000000ff1f63170
[ 8142.406401] LR [c000000ff1f63170] 0xc000000ff1f63170
[ 8142.406402] Call Trace:
[ 8142.406404] [c000000fe3173780] [c000000ff1f63170] 0xc000000ff1f63170 (unreliable)
[ 8142.406405] Instruction dump:
[ 8142.406407] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[ 8142.406409] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[ 8142.406412] ---[ end trace 10787fb41cbf2534 ]---
[17667518570.449259] Faulting instruction address: 0xc0000000002659a0
[ 8142.408049] Faulting instruction address: 0x00000000
[17667518570.449269] Thread overran stack, or stack corrupted
[ 8142.408055] Thread overran stack, or stack corrupted
[ 8142.408307]
[17667518570.454842] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.413635] Oops: Kernel access of bad area, sig: 11 [#4]
[17667518570.454855] Faulting instruction address: 0xc0000000002659a0
[ 8142.413644] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
[17667518570.454863] Thread overran stack, or stack corrupted
[17667518570.454864] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.422223] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8142.422264] multipath(E)
[17667518570.472274] Faulting instruction address: 0xc0000000002659a0
[ 8142.431060] linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[17667518570.472285] Thread overran stack, or stack corrupted
[ 8142.431074] CPU: 32 PID: 2586 Comm: CPU 15/KVM Tainted: G D E 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8142.431076] NIP: 0000000000000000 LR: 0000000000000000 CTR: c000000000acbed0
[17667518570.472294] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.431082] REGS: c000000fe310b5a0 TRAP: 0400 Tainted: G D E (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[17667518570.472300] Faulting instruction address: 0xc0000000002659a0
[ 8142.431086] MSR: 9000000040001033 <SF,HV,ME,IR,DR,RI,LE> CR: 0000000b XER: 20000000
[ 8142.431091] CFAR: c00000000000e5c8 IRQMASK: 3
[ 8142.431091] GPR00: 0000000000000000 c000000fe310b830 c0000000012e0800 c000000fe0736000
[ 8142.431091] GPR04: c000000fe0721680 c000000fe0720a00 000000000000000b 0000000000000000
[ 8142.431091] GPR08: c000000fe310b650 c000000000000000 33ffffffffffffff c0080000082bc3a8
[ 8142.431091] GPR12: c000000000acbed0 c0000007fffdb080 0000000000000000 c000000000c21fd0
[ 8142.431091] GPR16: 000000000000000b c000000fe310b870 c000000fe310b790 c000000000c21fd0
[ 8142.431091] GPR20: c0000000000294e4 c0000000012e0800 0000000000000000 c000000000c21fd0
[ 8142.431091] GPR24: 000000000000000b c000000fe310b870 c000000fe310b800 c000000000e45f10
[ 8142.431091] GPR28: c00000000007d894 d507963ef7efbb00 c000000fe310b7f0 0000000000000001
[17667518570.472323] Thread overran stack, or stack corrupted
[17667518570.472324] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8142.431112] NIP [0000000000000000] 0x0
[ 8142.431114] LR [0000000000000000] 0x0
[17667518570.478631] Faulting instruction address: 0xc0000000002659a0
[17667518570.478632] Thread overran stack, or stack corrupted
[ 8142.437420] Call Trace:
[17667518571.285842] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8143.244628] [c000000fe310b830] [c00000000146e120] 0xc00000000146e120 (unreliable)
[17667518571.285847] Faulting instruction address: 0xc0000000002659a0
[17667518571.285848] Thread overran stack, or stack corrupted
[ 8143.244637] Instruction dump:
[17667518571.285856] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8143.244645] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[17667518571.285864] Faulting instruction address: 0xc0000000002659a0
[ 8143.244652] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[17667518571.285872] Thread overran stack, or stack corrupted
[17667518571.285873] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8143.244661] ---[ end trace 10787fb41cbf2535 ]---
[17667518572.110559] Faulting instruction address: 0xc0000000002659a0
[17667518572.110561] Thread overran stack, or stack corrupted
[ 8144.071411]
[17667518572.943440] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518573.601693] Faulting instruction address: 0xc0000000002659a0
[17667518573.601696] Thread overran stack, or stack corrupted
[17667518573.601700] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518573.601704] Faulting instruction address: 0xc0000000002659a0
[17667518573.601707] Thread overran stack, or stack corrupted
[17667518573.601711] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518573.601715] Faulting instruction address: 0xc0000000002659a0
[17667518573.601718] Thread overran stack, or stack corrupted
[17667518573.601722] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518573.601726] Faulting instruction address: 0xc0000000002659a0
[17667518574.426502] Thread overran stack, or stack corrupted
[17667518574.426506] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518574.426510] Faulting instruction address: 0xc0000000002659a0
[17667518574.426513] Thread overran stack, or stack corrupted
[17667518574.426517] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518574.426521] Faulting instruction address: 0xc0000000002659a0
[17667518574.426524] Thread overran stack, or stack corrupted
[17667518574.426527] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518574.426531] Faulting instruction address: 0xc0000000002659a0
[17667518574.426534] Thread overran stack, or stack corrupted
[17667518574.426538] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518574.426541] Faulting instruction address: 0xc0000000002659a0
[17667518574.426544] Thread overran stack, or stack corrupted
[17667518575.251461] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518575.251466] Faulting instruction address: 0xc0000000002659a0
[17667518575.251469] Thread overran stack, or stack corrupted
[17667518575.251473] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518575.251477] Faulting instruction address: 0xc0000000002659a0
[17667518575.251481] Thread overran stack, or stack corrupted
[17667518575.251485] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518575.251489] Faulting instruction address: 0xc0000000002659a0
[17667518575.251493] Thread overran stack, or stack corrupted
[17667518575.251497] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518575.251501] Faulting instruction address: 0xc0000000002659a0
[17667518575.251505] Thread overran stack, or stack corrupted
[17667518575.251508] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518575.251513] Faulting instruction address: 0xc0000000002659a0
[17667518576.075571] Thread overran stack, or stack corrupted
[17667518576.075575] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518576.075580] Faulting instruction address: 0xc0000000002659a0
[17667518576.075583] Thread overran stack, or stack corrupted
[17667518576.075587] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518576.075591] Faulting instruction address: 0xc0000000002659a0
[17667518576.075595] Thread overran stack, or stack corrupted
[17667518576.075599] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518576.075603] Faulting instruction address: 0xc0000000002659a0
[17667518576.075606] Thread overran stack, or stack corrupted
[17667518576.075610] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518576.075614] Faulting instruction address: 0xc0000000002659a0
[17667518576.075617] Thread overran stack, or stack corrupted
[17667518576.900573] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518576.900577] Faulting instruction address: 0xc0000000002659a0
[17667518576.900581] Thread overran stack, or stack corrupted
[17667518576.900584] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518576.900589] Faulting instruction address: 0xc0000000002659a0
[17667518576.900592] Thread overran stack, or stack corrupted
[17667518576.900596] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518576.900601] Faulting instruction address: 0xc0000000002659a0
[17667518576.900604] Thread overran stack, or stack corrupted
[17667518576.900608] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518576.900612] Faulting instruction address: 0xc0000000002659a0
[17667518576.900615] Thread overran stack, or stack corrupted
[17667518576.900620] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518576.900624] Faulting instruction address: 0xc0000000002659a0
[17667518577.724123] Thread overran stack, or stack corrupted
[17667518577.724127] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518577.724132] Faulting instruction address: 0xc0000000002659a0
[17667518577.724135] Thread overran stack, or stack corrupted
[17667518577.724139] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518577.724143] Faulting instruction address: 0xc0000000002659a0
[17667518577.724146] Thread overran stack, or stack corrupted
[17667518577.724150] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518577.724155] Faulting instruction address: 0xc0000000002659a0
[17667518577.724158] Thread overran stack, or stack corrupted
[17667518577.724162] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518577.724167] Faulting instruction address: 0xc0000000002659a0
[17667518577.724170] Thread overran stack, or stack corrupted
[17667518578.547773] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518578.547778] Faulting instruction address: 0xc0000000002659a0
[17667518578.547781] Thread overran stack, or stack corrupted
[17667518578.547785] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518578.547790] Faulting instruction address: 0xc0000000002659a0
[17667518578.547793] Thread overran stack, or stack corrupted
[17667518578.547797] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518578.547801] Faulting instruction address: 0xc0000000002659a0
[17667518578.547805] Thread overran stack, or stack corrupted
[17667518578.547809] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518578.547813] Faulting instruction address: 0xc0000000002659a0
[17667518578.547817] Thread overran stack, or stack corrupted
[17667518578.547821] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518578.547825] Faulting instruction address: 0xc0000000002659a0
[17667518579.371665] Thread overran stack, or stack corrupted
[17667518579.371669] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518579.371673] Faulting instruction address: 0xc0000000002659a0
[17667518579.371677] Thread overran stack, or stack corrupted
[17667518579.371681] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518579.371685] Faulting instruction address: 0xc0000000002659a0
[17667518579.371689] Thread overran stack, or stack corrupted
[17667518579.371692] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518579.371697] Faulting instruction address: 0xc0000000002659a0
[17667518579.371700] Thread overran stack, or stack corrupted
[17667518579.371705] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518579.371709] Faulting instruction address: 0xc0000000002659a0
[17667518579.371713] Thread overran stack, or stack corrupted
[17667518580.194529] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518580.194534] Faulting instruction address: 0xc0000000002659a0
[17667518580.194537] Thread overran stack, or stack corrupted
[17667518580.194541] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518580.194546] Faulting instruction address: 0xc0000000002659a0
[17667518580.194550] Thread overran stack, or stack corrupted
[17667518580.194554] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518580.194558] Faulting instruction address: 0xc0000000002659a0
[17667518580.194561] Thread overran stack, or stack corrupted
[17667518580.194565] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518580.194570] Faulting instruction address: 0xc0000000002659a0
[17667518580.194573] Thread overran stack, or stack corrupted
[17667518580.194577] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518580.194581] Faulting instruction address: 0xc0000000002659a0
[17667518581.018714] Thread overran stack, or stack corrupted
[17667518581.018718] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518581.018723] Faulting instruction address: 0xc0000000002659a0
[17667518581.018726] Thread overran stack, or stack corrupted
[17667518581.018730] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518581.018734] Faulting instruction address: 0xc0000000002659a0
[17667518581.018737] Thread overran stack, or stack corrupted
[17667518581.018741] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518581.018745] Faulting instruction address: 0xc0000000002659a0
[17667518581.018749] Thread overran stack, or stack corrupted
[17667518581.018753] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518581.018757] Faulting instruction address: 0xc0000000002659a0
[17667518581.018761] Thread overran stack, or stack corrupted
[17667518581.843097] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518581.843101] Faulting instruction address: 0xc0000000002659a0
[17667518581.843105] Thread overran stack, or stack corrupted
[17667518581.843109] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518581.843113] Faulting instruction address: 0xc0000000002659a0
[17667518581.843116] Thread overran stack, or stack corrupted
[17667518581.843120] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518581.843125] Faulting instruction address: 0xc0000000002659a0
[17667518581.843128] Thread overran stack, or stack corrupted
[17667518581.843132] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518581.843136] Faulting instruction address: 0xc0000000002659a0
[17667518581.843139] Thread overran stack, or stack corrupted
[17667518581.843143] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518581.843147] Faulting instruction address: 0xc0000000002659a0
[17667518582.667850] Thread overran stack, or stack corrupted
[17667518582.667854] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518582.667858] Faulting instruction address: 0xc0000000002659a0
[17667518582.667862] Thread overran stack, or stack corrupted
[17667518582.667866] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518582.667870] Faulting instruction address: 0xc0000000002659a0
[17667518582.667874] Thread overran stack, or stack corrupted
[17667518582.667878] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518582.667882] Faulting instruction address: 0xc0000000002659a0
[17667518582.667885] Thread overran stack, or stack corrupted
[17667518582.667889] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518582.667893] Faulting instruction address: 0xc0000000002659a0
[17667518582.667897] Thread overran stack, or stack corrupted
[17667518583.496844] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518583.496848] Faulting instruction address: 0xc0000000002659a0
[17667518583.496852] Thread overran stack, or stack corrupted
[17667518583.496856] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518583.496860] Faulting instruction address: 0xc0000000002659a0
[17667518583.496864] Thread overran stack, or stack corrupted
[17667518583.496868] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518583.496872] Faulting instruction address: 0xc0000000002659a0
[17667518583.496876] Thread overran stack, or stack corrupted
[17667518583.496880] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518583.496884] Faulting instruction address: 0xc0000000002659a0
[17667518583.496888] Thread overran stack, or stack corrupted
[17667518583.496892] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518583.496896] Faulting instruction address: 0xc0000000002659a0
[17667518584.321780] Thread overran stack, or stack corrupted
[17667518584.321784] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518584.321788] Faulting instruction address: 0xc0000000002659a0
[17667518584.321791] Thread overran stack, or stack corrupted
[17667518584.321796] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518584.321800] Faulting instruction address: 0xc0000000002659a0
[17667518584.321803] Thread overran stack, or stack corrupted
[17667518584.321807] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518584.321811] Faulting instruction address: 0xc0000000002659a0
[17667518584.321815] Thread overran stack, or stack corrupted
[17667518584.321819] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518584.321823] Faulting instruction address: 0xc0000000002659a0
[17667518584.321827] Thread overran stack, or stack corrupted
[17667518584.981269] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518584.981273] Faulting instruction address: 0xc0000000002659a0
[17667518584.981277] Thread overran stack, or stack corrupted
[17667518584.981280] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518584.981284] Faulting instruction address: 0xc0000000002659a0
[17667518584.981288] Thread overran stack, or stack corrupted
[17667518584.981292] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518584.981296] Faulting instruction address: 0xc0000000002659a0
[17667518584.981300] Thread overran stack, or stack corrupted
[17667518584.981304] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518584.981308] Faulting instruction address: 0xc0000000002659a0
[17667518584.981312] Thread overran stack, or stack corrupted
[17667518584.981316] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518584.981320] Faulting instruction address: 0xc0000000002659a0
[17667518585.805488] Thread overran stack, or stack corrupted
[17667518585.805492] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518585.805496] Faulting instruction address: 0xc0000000002659a0
[17667518585.805500] Thread overran stack, or stack corrupted
[17667518585.805504] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518585.805508] Faulting instruction address: 0xc0000000002659a0
[17667518585.805511] Thread overran stack, or stack corrupted
[17667518585.805515] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518585.805520] Faulting instruction address: 0xc0000000002659a0
[17667518585.805523] Thread overran stack, or stack corrupted
[17667518585.805527] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518585.805531] Faulting instruction address: 0xc0000000002659a0
[17667518585.805534] Thread overran stack, or stack corrupted
[17667518586.630790] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518586.630794] Faulting instruction address: 0xc0000000002659a0
[17667518586.630797] Thread overran stack, or stack corrupted
[17667518586.630801] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518586.630806] Faulting instruction address: 0xc0000000002659a0
[17667518586.630809] Thread overran stack, or stack corrupted
[17667518586.630813] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518586.630817] Faulting instruction address: 0xc0000000002659a0
[17667518586.630821] Thread overran stack, or stack corrupted
[17667518586.630824] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518586.630829] Faulting instruction address: 0xc0000000002659a0
[17667518586.630832] Thread overran stack, or stack corrupted
[17667518586.630836] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518586.630840] Faulting instruction address: 0xc0000000002659a0
[17667518587.455364] Thread overran stack, or stack corrupted
[17667518587.455368] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518587.455372] Faulting instruction address: 0xc0000000002659a0
[17667518587.455376] Thread overran stack, or stack corrupted
[17667518587.455380] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518587.455384] Faulting instruction address: 0xc0000000002659a0
[17667518587.455388] Thread overran stack, or stack corrupted
[17667518587.455391] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518587.455395] Faulting instruction address: 0xc0000000002659a0
[17667518587.455399] Thread overran stack, or stack corrupted
[17667518587.455403] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518587.455407] Faulting instruction address: 0xc0000000002659a0
[17667518587.455410] Thread overran stack, or stack corrupted
[ 8159.952852] watchdog: CPU 0 detected hard LOCKUP on other CPUs 8,48
[17667518588.279715] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8160.238504] watchdog: CPU 0 TB:4230131381087, last SMP heartbeat TB:4221939491185 (15999ms ago)
[17667518588.279722] Faulting instruction address: 0xc0000000002659a0
[17667518588.279723] Thread overran stack, or stack corrupted
[17667518588.279734] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518588.279738] Faulting instruction address: 0xc0000000002659a0
[17667518588.279742] Thread overran stack, or stack corrupted
[17667518588.279746] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518588.279750] Faulting instruction address: 0xc0000000002659a0
[17667518588.279753] Thread overran stack, or stack corrupted
[17667518588.279758] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518588.279762] Faulting instruction address: 0xc0000000002659a0
[17667518589.103759] Thread overran stack, or stack corrupted
[17667518589.103762] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518589.103767] Faulting instruction address: 0xc0000000002659a0
[17667518589.103770] Thread overran stack, or stack corrupted
[17667518589.103774] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518589.103778] Faulting instruction address: 0xc0000000002659a0
[17667518589.103782] Thread overran stack, or stack corrupted
[17667518589.103786] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518589.103790] Faulting instruction address: 0xc0000000002659a0
[17667518589.103793] Thread overran stack, or stack corrupted
[17667518589.103797] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518589.103801] Faulting instruction address: 0xc0000000002659a0
[17667518589.103804] Thread overran stack, or stack corrupted
[17667518589.103808] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518589.928019] Faulting instruction address: 0xc0000000002659a0
[17667518589.928023] Thread overran stack, or stack corrupted
[17667518589.928026] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518589.928031] Faulting instruction address: 0xc0000000002659a0
[17667518589.928034] Thread overran stack, or stack corrupted
[17667518589.928038] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518589.928042] Faulting instruction address: 0xc0000000002659a0
[17667518589.928046] Thread overran stack, or stack corrupted
[17667518589.928049] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518589.928054] Faulting instruction address: 0xc0000000002659a0
[17667518589.928057] Thread overran stack, or stack corrupted
[17667518589.928061] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[17667518589.928065] Faulting instruction address: 0xc0000000002659a0
[ 8162.389382] watchdog: CPU 32 self-detected hard LOCKUP @ _raw_spin_lock+0x88/0x100
[ 8162.389383] watchdog: CPU 32 TB:4226720430412, last heartbeat TB:4219905863158 (13309ms ago)
[ 8162.389383] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8162.389404] multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8162.389407] CPU: 32 PID: 2586 Comm: CPU 15/KVM Tainted: G D E 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8162.389408] NIP: c000000000acc548 LR: c00000000017453c CTR: c0000000004a6d30
[ 8162.389408] REGS: c0000007ffd0fd70 TRAP: 0900 Tainted: G D E (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[ 8162.389409] MSR: 9000000002009033 <SF,HV,VEC,EE,ME,IR,DR,RI,LE> CR: 28000484 XER: 20000000
[ 8162.389412] CFAR: c000000000acc534 IRQMASK: 1
[ 8162.389413] GPR00: c00000000017453c c000000fe310ad40 c0000000012e0800 c0000007fc898f00
[ 8162.389415] GPR04: 0000000000000001 0000000000000000 0000000000000000 0000000000000001
[ 8162.389416] GPR08: c0000000011d2488 0000000000000000 0000000080000020 ffffffffffffffff
[ 8162.389418] GPR12: 0000000000000000 c0000007fffdb080 0000000000000000 c000000000c21fd0
[ 8162.389420] GPR16: 000000000000000b c000000fe310b870 c000000fe310b790 c000000000c21fd0
[ 8162.389421] GPR20: c0000000000294e4 c0000000012e0800 c0000000001fc560 0000000000000001
[ 8162.389423] GPR24: 0000076865feaf13 c000000fe0720a00 00000007fb9c0000 c00000000130df78
[ 8162.389424] GPR28: c000000000ed8f00 0000000000000100 c000000001311f80 c0000007fc898f00
[ 8162.389426] NIP [c000000000acc548] _raw_spin_lock+0x88/0x100
[ 8162.389426] LR [c00000000017453c] scheduler_tick+0x6c/0x1e0
[ 8162.389427] Call Trace:
[ 8162.389427] [c000000fe310ad40] [0000000000000004] 0x4 (unreliable)
[ 8162.389428] [c000000fe310ad70] [3031343665313230] 0x3031343665313230
[ 8162.389429] [c000000fe310add0] [c0000000001e2f1c] update_process_times+0x8c/0xb0
[ 8162.389429] [c000000fe310ae00] [c0000000001fc194] tick_sched_handle.isra.16+0x34/0xd0
[ 8162.389430] [c000000fe310ae30] [c0000000001fc5c8] tick_sched_timer+0x68/0xe0
[ 8162.389431] [c000000fe310ae70] [c0000000001e458c] __hrtimer_run_queues+0x17c/0x420
[ 8162.389432] [c000000fe310aef0] [c0000000001e5298] hrtimer_interrupt+0x128/0x300
[ 8162.389432] [c000000fe310afa0] [c000000000027da4] timer_interrupt+0x104/0x2e0
[ 8162.389433] [c000000fe310b000] [c000000000009408] decrementer_common+0x158/0x160
[ 8162.389434] --- interrupt: 901 at replay_interrupt_return+0x0/0x4
[ 8162.389434] LR = arch_local_irq_restore.part.10+0x54/0x70
[ 8162.389435] [c000000fe310b300] [c000000fe310b350] 0xc000000fe310b350 (unreliable)
[ 8162.389436] [c000000fe310b320] [c00000000014410c] exit_signals+0x18c/0x260
[ 8162.389436] [c000000fe310b370] [c00000000013137c] do_exit+0x10c/0xd20
[ 8162.389437] [c000000fe310b440] [c0000000000290a0] oops_end+0x130/0x1a0
[ 8162.389438] [c000000fe310b4c0] [c00000000007d894] bad_page_fault+0x174/0x1c0
[ 8162.389438] [c000000fe310b530] [c00000000000aef4] handle_page_fault+0x2c/0x30
[ 8162.389439] --- interrupt: 400 at 0x0
[ 8162.389439] LR = 0x0
[ 8162.389440] [c000000fe310b830] [c00000000146e120] 0xc00000000146e120 (unreliable)
[ 8162.389440] Instruction dump:
[ 8162.389441] 3bde1780 fbe1fff8 7c7f1b78 f821ffd1 7c210b78 e93e0000 75290010 41820014
[ 8162.389443] e92d0000 89290009 71290002 4082005c <813f0000> 2fa90000 409effd8 7c421378
[ 8163.400810] rcu: INFO: rcu_sched self-detected stall on CPU
[17667518591.577813] Thread overran stack, or stack corrupted
[ 8163.536611] rcu: 96-....: (4691 ticks this GP) idle=ee6/1/0x4000000000000002 softirq=78853/78853 fqs=2326
[17667518591.577831] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8163.536651] (t=5280 jiffies g=220569 q=31)
[ 8163.952798] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [CPU 18/KVM:2589]
[ 8163.952800] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8163.952825] multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8163.952831] CPU: 0 PID: 2589 Comm: CPU 18/KVM Tainted: G D E 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8163.952832] NIP: c000000000acc52c LR: c000000000370874 CTR: 0000000000000001
[ 8163.952834] REGS: c000000fe317f3b0 TRAP: 0901 Tainted: G D E (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[ 8163.952834] MSR: 9000000000009033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 28222824 XER: 00000000
[ 8163.952838] CFAR: c000000000acc550 IRQMASK: 0
[ 8163.952838] GPR00: c000000000370874 c000000fe317f640 c0000000012e0800 c00c000003f9c3a8
[ 8163.952838] GPR04: 00400ee70f000080 00000000e70e4000 000000000000000a 000000003b002386
[ 8163.952838] GPR08: 4000000000002000 0000000080000080 0000000080000000 00000000f1a70000
[ 8163.952838] GPR12: 0000000000008800 c0000000014a0000
[ 8163.952846] NIP [c000000000acc52c] _raw_spin_lock+0x6c/0x100
[ 8163.952849] LR [c000000000370874] follow_page_mask+0x754/0xf40
[ 8163.952850] Call Trace:
[ 8163.952852] [c000000fe317f640] [c000000fe317f830] 0xc000000fe317f830 (unreliable)
[ 8163.952854] [c000000fe317f670] [c0000007fa898f00] 0xc0000007fa898f00
[ 8163.952856] [c000000fe317f710] [c00000000037132c] __get_user_pages+0x2cc/0x5c0
[ 8163.952858] [c000000fe317f830] [c000000000371ccc] get_user_pages_unlocked+0xec/0x2f0
[ 8163.952860] [c000000fe317f8c0] [c0000000003736c4] get_user_pages_fast+0x1d4/0x210
[ 8163.952865] [c000000fe317f920] [c0080000082b16a8] kvmppc_book3s_hv_page_fault+0x3c0/0xd90 [kvm_hv]
[ 8163.952868] [c000000fe317fa10] [c0080000082ad234] kvmppc_vcpu_run_hv+0x94c/0xb20 [kvm_hv]
[ 8163.952874] [c000000fe317fae0] [c0080000081098cc] kvmppc_vcpu_run+0x34/0x48 [kvm]
[ 8163.952878] [c000000fe317fb00] [c00800000810587c] kvm_arch_vcpu_ioctl_run+0x2f4/0x400 [kvm]
[ 8163.952882] [c000000fe317fb90] [c0080000080f7ac8] kvm_vcpu_ioctl+0x340/0x7d0 [kvm]
[ 8163.952884] [c000000fe317fd00] [c000000000445410] do_vfs_ioctl+0xe0/0xac0
[ 8163.952886] [c000000fe317fdb0] [c000000000445eb4] ksys_ioctl+0xc4/0x110
[ 8163.952888] [c000000fe317fe00] [c000000000445f28] sys_ioctl+0x28/0x80
[ 8163.952890] [c000000fe317fe20] [c00000000000b9c8] system_call+0x5c/0x68
[ 8163.952891] Instruction dump:
[ 8163.952893] b12d1180 4e800020 60000000 60000000 60000000 fbc1fff0 3fc20003 3bde1780
[ 8163.952895] fbe1fff8 7c7f1b78 f821ffd1 7c210b78 <e93e0000> 75290010 41820014 e92d0000
[ 8164.060798] watchdog: BUG: soft lockup - CPU#72 stuck for 22s! [CPU 27/KVM:2598]
[ 8164.060800] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8164.060842] multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8164.060852] CPU: 72 PID: 2598 Comm: CPU 27/KVM Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8164.060854] NIP: c000000000acc52c LR: c0080000082a4428 CTR: c000000000acc4c0
[ 8164.060856] REGS: c000000fe31336e0 TRAP: 0901 Tainted: G D EL (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[ 8164.060857] MSR: 9000000002009033 <SF,HV,VEC,EE,ME,IR,DR,RI,LE> CR: 24224244 XER: 20000000
[ 8164.060861] CFAR: c000000000acc550 IRQMASK: 0
[ 8164.060861] GPR00: c0080000082a4428 c000000fe3133970 c0000000012e0800 c000000ff1f6bc70
[ 8164.060861] GPR04: 0000000000000000 000003d6cff6afea 000003d6d015bce0 0000000000000000
[ 8164.060861] GPR08: c000000fe0f23020 0000000080000030 0000000080000048 c0080000082bcc68
[ 8164.060861] GPR12: c000000000acc4c0 c000000ffffd9e00
[ 8164.060872] NIP [c000000000acc52c] _raw_spin_lock+0x6c/0x100
[ 8164.060876] LR [c0080000082a4428] kvmppc_wait_for_exec+0x110/0x140 [kvm_hv]
[ 8164.060877] Call Trace:
[ 8164.060879] [c000000fe3133970] [c000000000ac4748] schedule+0x58/0x120 (unreliable)
[ 8164.060883] [c000000fe31339a0] [c0080000082a441c] kvmppc_wait_for_exec+0x104/0x140 [kvm_hv]
[ 8164.060886] [c000000fe3133a10] [c0080000082acf3c] kvmppc_vcpu_run_hv+0x654/0xb20 [kvm_hv]
[ 8164.060892] [c000000fe3133ae0] [c0080000081098cc] kvmppc_vcpu_run+0x34/0x48 [kvm]
[ 8164.060897] [c000000fe3133b00] [c00800000810587c] kvm_arch_vcpu_ioctl_run+0x2f4/0x400 [kvm]
[ 8164.060901] [c000000fe3133b90] [c0080000080f7ac8] kvm_vcpu_ioctl+0x340/0x7d0 [kvm]
[ 8164.060904] [c000000fe3133d00] [c000000000445410] do_vfs_ioctl+0xe0/0xac0
[ 8164.060906] [c000000fe3133db0] [c000000000445eb4] ksys_ioctl+0xc4/0x110
[ 8164.060908] [c000000fe3133e00] [c000000000445f28] sys_ioctl+0x28/0x80
[ 8164.060911] [c000000fe3133e20] [c00000000000b9c8] system_call+0x5c/0x68
[ 8164.060912] Instruction dump:
[ 8164.060914] b12d1180 4e800020 60000000 60000000 60000000 fbc1fff0 3fc20003 3bde1780
[ 8164.060917] fbe1fff8 7c7f1b78 f821ffd1 7c210b78 <e93e0000> 75290010 41820014 e92d0000
[ 8164.240796] watchdog: BUG: soft lockup - CPU#112 stuck for 22s! [CPU 1/KVM:2572]
[ 8164.240798] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8164.240852] multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8164.240863] CPU: 112 PID: 2572 Comm: CPU 1/KVM Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8164.240865] NIP: c000000000acc52c LR: c0080000082a4428 CTR: c000000000acc4c0
[ 8164.240867] REGS: c000000fe31376e0 TRAP: 0901 Tainted: G D EL (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[ 8164.240868] MSR: 9000000000009033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 28224244 XER: 00000000
[ 8164.240872] CFAR: c000000000acc550 IRQMASK: 0
[ 8164.240872] GPR00: c0080000082a4428 c000000fe3137970 c0000000012e0800 c000000ff1035e70
[ 8164.240872] GPR04: 0000000000000000 000003d6d0161a93 000003d6d034fcc6 0000000000000000
[ 8164.240872] GPR08: c000000fe013f5d0 0000000080000030 0000000080000070 c0080000082bcc68
[ 8164.240872] GPR12: c000000000acc4c0 c0000017fffd9e00
[ 8164.240884] NIP [c000000000acc52c] _raw_spin_lock+0x6c/0x100
[ 8164.240890] LR [c0080000082a4428] kvmppc_wait_for_exec+0x110/0x140 [kvm_hv]
[ 8164.240891] Call Trace:
[ 8164.240893] [c000000fe3137970] [c000000000ac4748] schedule+0x58/0x120 (unreliable)
[ 8164.240897] [c000000fe31379a0] [c0080000082a441c] kvmppc_wait_for_exec+0x104/0x140 [kvm_hv]
[ 8164.240900] [c000000fe3137a10] [c0080000082acf3c] kvmppc_vcpu_run_hv+0x654/0xb20 [kvm_hv]
[ 8164.240908] [c000000fe3137ae0] [c0080000081098cc] kvmppc_vcpu_run+0x34/0x48 [kvm]
[ 8164.240914] [c000000fe3137b00] [c00800000810587c] kvm_arch_vcpu_ioctl_run+0x2f4/0x400 [kvm]
[ 8164.240919] [c000000fe3137b90] [c0080000080f7ac8] kvm_vcpu_ioctl+0x340/0x7d0 [kvm]
[ 8164.240922] [c000000fe3137d00] [c000000000445410] do_vfs_ioctl+0xe0/0xac0
[ 8164.240924] [c000000fe3137db0] [c000000000445eb4] ksys_ioctl+0xc4/0x110
[ 8164.240926] [c000000fe3137e00] [c000000000445f28] sys_ioctl+0x28/0x80
[ 8164.240929] [c000000fe3137e20] [c00000000000b9c8] system_call+0x5c/0x68
[ 8164.240930] Instruction dump:
[ 8164.240931] b12d1180 4e800020 60000000 60000000 60000000 fbc1fff0 3fc20003 3bde1780
[ 8164.240935] fbe1fff8 7c7f1b78 f821ffd1 7c210b78 <e93e0000> 75290010 41820014 e92d0000
[17667518592.401130] Faulting instruction address: 0xc0000000002659a0
[ 8164.359922] Sending NMI from CPU 96 to CPUs 0:
[17667518592.401140] Thread overran stack, or stack corrupted
[17667518592.401142] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8164.359935] NMI backtrace for cpu 0
[ 8164.359937] CPU: 0 PID: 2589 Comm: CPU 18/KVM Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8164.359938] CPU 0 didn't respond to backtrace IPI, inspecting paca.
[17667518592.401156] Faulting instruction address: 0xc0000000002659a0
[17667518592.401158] Thread overran stack, or stack corrupted
[ 8164.359944] irq_soft_mask: 0x01 in_mce: 0 in_nmi: 0 current: 2589 (CPU 18/KVM)
[ 8164.359948] NIP: c000000000acc52c LR: c000000000370874 CTR: 0000000000000001
[ 8164.359951] Back trace of paca->saved_r1 (0xc0000000012dfb90) (possibly stale):
[17667518592.401169] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8164.359954] Call Trace:
[ 8164.359956] REGS: c000000fe317f3b0 TRAP: 0501 Tainted: G D EL (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[ 8164.359958] MSR: 9000000000009033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 28222824 XER: 00000000
[ 8164.359961] CFAR: c000000000acc550 IRQMASK: 0
[ 8164.359961] GPR00: c000000000370874 c000000fe317f640 c0000000012e0800 c00c000003f9c3a8
[ 8164.359961] GPR04: 00400ee70f000080 00000000e70e4000 000000000000000a 000000003b002386
[ 8164.359961] GPR08: 4000000000002000 0000000080000080 0000000080000000 00000000f1a70000
[ 8164.359961] GPR12: 0000000000008800 c0000000014a0000
[ 8164.359969] NIP [c000000000acc52c] _raw_spin_lock+0x6c/0x100
[17667518592.401188] Faulting instruction address: 0xc0000000002659a0
[ 8164.360020] Sending NMI from CPU 96 to CPUs 8:
[ 8165.185488] LR [c000000000370874] follow_page_mask+0x754/0xf40
[ 8165.185489] Call Trace:
[17667518593.226709] Thread overran stack, or stack corrupted
[17667518593.226711] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8165.185498] [c000000fe317f640] [c000000fe317f830] 0xc000000fe317f830 (unreliable)
[ 8165.185500] [c000000fe317f670] [c0000007fa898f00] 0xc0000007fa898f00
[17667518593.226719] Faulting instruction address: 0xc0000000002659a0
[17667518593.226720] Thread overran stack, or stack corrupted
[ 8165.185508] [c000000fe317f710] [c00000000037132c] __get_user_pages+0x2cc/0x5c0
[ 8165.185511] [c000000fe317f830] [c000000000371ccc] get_user_pages_unlocked+0xec/0x2f0
[17667518593.226730] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8165.185517] [c000000fe317f8c0] [c0000000003736c4] get_user_pages_fast+0x1d4/0x210
[17667518593.226736] Faulting instruction address: 0xc0000000002659a0
[ 8165.185525] [c000000fe317f920] [c0080000082b16a8] kvmppc_book3s_hv_page_fault+0x3c0/0xd90 [kvm_hv]
[ 8165.185527] [c000000fe317fa10] [c0080000082ad234] kvmppc_vcpu_run_hv+0x94c/0xb20 [kvm_hv]
[17667518593.226745] Thread overran stack, or stack corrupted
[17667518593.226746] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8165.185536] [c000000fe317fae0] [c0080000081098cc] kvmppc_vcpu_run+0x34/0x48 [kvm]
[ 8165.185541] [c000000fe317fb00] [c00800000810587c] kvm_arch_vcpu_ioctl_run+0x2f4/0x400 [kvm]
[17667518594.050689] Faulting instruction address: 0xc0000000002659a0
[17667518594.050690] Thread overran stack, or stack corrupted
[ 8166.009480] [c000000fe317fb90] [c0080000080f7ac8] kvm_vcpu_ioctl+0x340/0x7d0 [kvm]
[ 8166.009482] [c000000fe317fd00] [c000000000445410] do_vfs_ioctl+0xe0/0xac0
[17667518594.050700] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8166.009486] [c000000fe317fdb0] [c000000000445eb4] ksys_ioctl+0xc4/0x110
[ 8166.009488] [c000000fe317fe00] [c000000000445f28] sys_ioctl+0x28/0x80
[17667518594.050707] Faulting instruction address: 0xc0000000002659a0
[17667518594.050708] Thread overran stack, or stack corrupted
[ 8166.009495] [c000000fe317fe20] [c00000000000b9c8] system_call+0x5c/0x68
[17667518594.050714] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8166.009502] Instruction dump:
[17667518594.050721] Faulting instruction address: 0xc0000000002659a0
[ 8166.009508] b12d1180 4e800020 60000000 60000000 60000000 fbc1fff0 3fc20003 3bde1780
[17667518594.050727] Thread overran stack, or stack corrupted
[17667518594.050729] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8166.009516] fbe1fff8 7c7f1b78 f821ffd1 7c210b78 <e93e0000> 75290010 41820014 e92d0000
[ 8167.964747] watchdog: BUG: soft lockup - CPU#16 stuck for 23s! [CPU 9/KVM:2580]
[ 8168.196745] watchdog: BUG: soft lockup - CPU#104 stuck for 23s! [CPU 4/KVM:2575]
[ 8168.196746] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8168.196782] multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8168.196791] CPU: 104 PID: 2575 Comm: CPU 4/KVM Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8168.196793] NIP: c000000000acc52c LR: c0080000082a4428 CTR: c000000000acc4c0
[ 8168.196795] REGS: c000000fe31536e0 TRAP: 0901 Tainted: G D EL (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[ 8168.196796] MSR: 9000000000009033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 28224244 XER: 20000000
[ 8168.196801] CFAR: c000000000acc550 IRQMASK: 0
[ 8168.196801] GPR00: c0080000082a4428 c000000fe3153970 c0000000012e0800 c000000ff1f63170
[ 8168.196801] GPR04: 0000000000000000 000003d6d0003311 000003d6d015bce6 0000000000000000
[ 8168.196801] GPR08: c000000fedc49fd0 0000000080000050 0000000080000068 c0080000082bcc68
[ 8168.196801] GPR12: c000000000acc4c0 c0000017fffe3200
[ 8168.196812] NIP [c000000000acc52c] _raw_spin_lock+0x6c/0x100
[ 8168.196816] LR [c0080000082a4428] kvmppc_wait_for_exec+0x110/0x140 [kvm_hv]
[ 8168.196817] Call Trace:
[ 8168.196820] [c000000fe3153970] [c000000000ac4748] schedule+0x58/0x120 (unreliable)
[ 8168.196824] [c000000fe31539a0] [c0080000082a441c] kvmppc_wait_for_exec+0x104/0x140 [kvm_hv]
[ 8168.196828] [c000000fe3153a10] [c0080000082acf3c] kvmppc_vcpu_run_hv+0x654/0xb20 [kvm_hv]
[ 8168.196834] [c000000fe3153ae0] [c0080000081098cc] kvmppc_vcpu_run+0x34/0x48 [kvm]
[ 8168.196840] [c000000fe3153b00] [c00800000810587c] kvm_arch_vcpu_ioctl_run+0x2f4/0x400 [kvm]
[ 8168.196846] [c000000fe3153b90] [c0080000080f7ac8] kvm_vcpu_ioctl+0x340/0x7d0 [kvm]
[ 8168.196849] [c000000fe3153d00] [c000000000445410] do_vfs_ioctl+0xe0/0xac0
[ 8168.196851] [c000000fe3153db0] [c000000000445eb4] ksys_ioctl+0xc4/0x110
[ 8168.196853] [c000000fe3153e00] [c000000000445f28] sys_ioctl+0x28/0x80
[ 8168.196857] [c000000fe3153e20] [c00000000000b9c8] system_call+0x5c/0x68
[ 8168.196858] Instruction dump:
[ 8168.196859] b12d1180 4e800020 60000000 60000000 60000000 fbc1fff0 3fc20003 3bde1780
[ 8168.196863] fbe1fff8 7c7f1b78 f821ffd1 7c210b78 <e93e0000> 75290010 41820014 e92d0000
[ 8168.348742] watchdog: BUG: soft lockup - CPU#128 stuck for 22s! [qemu-system-ppc:2567]
[ 8168.348744] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8168.348800] multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8168.348811] CPU: 128 PID: 2567 Comm: qemu-system-ppc Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8168.348813] NIP: c000000000205328 LR: c0000000002052dc CTR: c0000000000b00d0
[ 8168.348815] REGS: c000000fe559f6e0 TRAP: 0901 Tainted: G D EL (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[ 8168.348816] MSR: 900000000280b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE> CR: 44224824 XER: 00000000
[ 8168.348822] CFAR: c000000000205330 IRQMASK: 0
[ 8168.348822] GPR00: c0000000002052dc c000000fe559f970 c0000000012e0800 0000000000000008
[ 8168.348822] GPR04: 0000000000000008 0000000000000008 c00000000130df78 c00000000130df78
[ 8168.348822] GPR08: 0000000000000008 0000000000000001 c0000007fb09e020 c0000000013121d8
[ 8168.348822] GPR12: c0000000000b00d0 c000001ffff89a80
[ 8168.348834] NIP [c000000000205328] smp_call_function_many+0x368/0x400
[ 8168.348836] LR [c0000000002052dc] smp_call_function_many+0x31c/0x400
[ 8168.348838] Call Trace:
[ 8168.348840] [c000000fe559f970] [c0000000002052dc] smp_call_function_many+0x31c/0x400 (unreliable)
[ 8168.348844] [c000000fe559f9e0] [c000000000087324] pmdp_invalidate+0xa4/0x110
[ 8168.348847] [c000000fe559fa20] [c0000000003f3998] change_huge_pmd+0x148/0x3d0
[ 8168.348850] [c000000fe559fa80] [c00000000038b2c8] change_protection+0x838/0xf00
[ 8168.348853] [c000000fe559fbf0] [c0000000003ccdc8] change_prot_numa+0x38/0xb0
[ 8168.348856] [c000000fe559fc20] [c00000000017bfe0] task_numa_work+0x2a0/0x440
[ 8168.348859] [c000000fe559fce0] [c00000000015bc78] task_work_run+0x148/0x1a0
[ 8168.348862] [c000000fe559fd30] [c00000000001fcb4] do_notify_resume+0x3f4/0x440
[ 8168.348864] [c000000fe559fe20] [c00000000000e430] ret_from_except_lite+0x5c/0x60
[ 8168.348866] Instruction dump:
[ 8168.348867] 79091f24 e95f0000 7d27482a 7d4a4a14 812a0018 71290001 41820024 60000000
[ 8168.348871] 60000000 60000000 7c210b78 7c421378 <812a0018> 71290001 4082fff0 7c2004ac
[17667518596.522731] Faulting instruction address: 0xc0000000002659a0
[ 8168.481520] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8168.481552] multipath(E)
[17667518596.522771] Thread overran stack, or stack corrupted
[17667518596.522772] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8169.140080] linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[17667518597.181303] Faulting instruction address: 0xc0000000002659a0
[ 8169.140092] CPU: 16 PID: 2580 Comm: CPU 9/KVM Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[17667518597.181310] Thread overran stack, or stack corrupted
[17667518597.181311] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8169.140097] NIP: c000000000acc52c LR: c0080000082a4428 CTR: c000000000acc4c0
[ 8169.140099] REGS: c000000fe31076e0 TRAP: 0901 Tainted: G D EL (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[17667518597.181318] Faulting instruction address: 0xc0000000002659a0
[ 8169.140106] MSR: 9000000000009033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 28224284 XER: 20000000
[ 8169.140110] CFAR: c000000000acc550 IRQMASK: 0
[ 8169.140110] GPR00: c0080000082a4428 c000000fe3107970 c0000000012e0800 c000000ff1f63f70
[ 8169.140110] GPR04: 0000000000000000 000003d6cfcb30f5 000003d6cfd73d24 00000000001ac18a
[ 8169.140110] GPR08: c000000fe42b55b0 0000000080000008 0000000080000010 c0080000082bcc68
[ 8169.140110] GPR12: c000000000acc4c0 c0000007fffed880
[ 8169.140121] NIP [c000000000acc52c] _raw_spin_lock+0x6c/0x100
[17667518598.005216] Thread overran stack, or stack corrupted
[ 8169.964007] LR [c0080000082a4428] kvmppc_wait_for_exec+0x110/0x140 [kvm_hv]
[ 8169.964008] Call Trace:
[17667518598.005230] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8169.964017] Instruction dump:
[ 8170.000795] CPU 8 didn't respond to backtrace IPI, inspecting paca.
[ 8170.000797] irq_soft_mask: 0x01 in_mce: 0 in_nmi: 0 current: 2582 (CPU 11/KVM)
[ 8170.000799] Back trace of paca->saved_r1 (0xc0000007fff8bf60) (possibly stale):
[ 8170.000800] Call Trace:
[ 8170.000804] [c0000007fff8bf60] [c00000000001a564] __do_irq+0x74/0x200 (unreliable)
[ 8170.000808] [c0000007fff8bf90] [c00000000002d23c] call_do_irq+0x14/0x24
[ 8170.000811] [c000000fe311f4f0] [c000000000048f98] doorbell_exception+0xc8/0x210
[ 8170.000815] [c000000fe311f530] [c00000000000a128] h_doorbell_common+0x158/0x160
[ 8170.000817] [c000000fe311f830] [c000000ff1f63f00] 0xc000000ff1f63f00
[ 8170.000862] Sending NMI from CPU 96 to CPUs 16:
[17667518598.829353] Faulting instruction address: 0xc0000000002659a0
[ 8170.788142] b12d1180 4e800020 60000000 60000000 60000000 fbc1fff0 3fc20003 3bde1780
[17667518598.829369] Thread overran stack, or stack corrupted
[17667518598.829371] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8170.788157] fbe1fff8 7c7f1b78 f821ffd1 7c210b78 <e93e0000> 75290010 41820014 e92d0000
[ 8170.788167] NMI backtrace for cpu 16
[ 8170.788169] CPU 16 didn't respond to backtrace IPI, inspecting paca.
[17667518598.829390] Faulting instruction address: 0xc0000000002659a0
[ 8170.788180] CPU: 16 PID: 2580 Comm: CPU 9/KVM Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8170.788182] NIP: c000000000acc52c LR: c0080000082a4428 CTR: c000000000acc4c0
[ 8170.788227] irq_soft_mask: 0x01 in_mce: 0 in_nmi: 0 current: 2580 (CPU 9/KVM)
[ 8170.788230] Back trace of paca->saved_r1 (0xc000000fe312f530) (possibly stale):
[ 8170.788231] Call Trace:
[ 8170.788275] Sending NMI from CPU 96 to CPUs 48:
[17667518599.652331] Thread overran stack, or stack corrupted
[ 8171.611119] REGS: c000000fe31076e0 TRAP: 0501 Tainted: G D EL (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[17667518599.652339] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8171.611125] MSR: 9000000000009033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 28224284 XER: 20000000
[ 8171.611130] CFAR: c00000000000e5c8 IRQMASK: 0
[ 8171.611130] GPR00: c0080000082a4428 c000000fe3107970 c0000000012e0800 c000000ff1f63f70
[ 8171.611130] GPR04: 0000000000000000 000003d6cfcb30f5 000003d6cfd73d24 00000000001ac18a
[ 8171.611130] GPR08: c000000fe42b55b0 0000000080000008 0000000080000010 c0080000082bcc68
[ 8171.611130] GPR12: c000000000acc4c0 c0000007fffed880
[17667518599.652355] Faulting instruction address: 0xc0000000002659a0
[ 8171.611143] NIP [c000000000acc52c] _raw_spin_lock+0x6c/0x100
[ 8171.611146] LR [c0080000082a4428] kvmppc_wait_for_exec+0x110/0x140 [kvm_hv]
[17667518599.652363] Thread overran stack, or stack corrupted
[17667518599.652365] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8171.611151] Call Trace:
[17667518599.652371] Faulting instruction address: 0xc0000000002659a0
[ 8171.611158] Instruction dump:
[17667518599.652378] Thread overran stack, or stack corrupted
[17667518599.652380] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8172.434134] b12d1180 4e800020 60000000 60000000 60000000 fbc1fff0 3fc20003 3bde1780
[17667518601.299124] Faulting instruction address: 0xc0000000002659a0
[17667518601.299126] Thread overran stack, or stack corrupted
[ 8173.257915] fbe1fff8 7c7f1b78 f821ffd1 7c210b78 <e93e0000> 75290010 41820014 e92d0000
[17667518601.299135] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8175.952645] watchdog: CPU 0 detected hard LOCKUP on other CPUs 96
[ 8176.425098] CPU 48 didn't respond to backtrace IPI, inspecting paca.
[ 8176.425100] irq_soft_mask: 0x01 in_mce: 0 in_nmi: 0 current: 2595 (CPU 24/KVM)
[ 8176.425102] Back trace of paca->saved_r1 (0xc000000fe313b830) (possibly stale):
[ 8176.425103] Call Trace:
[ 8176.425105] [c000000fe313b830] [c000000ff1f6bc00] 0xc000000ff1f6bc00 (unreliable)
[ 8176.425109] [c000000fe313b8d0] [c00000000019712c] autoremove_wake_function+0x2c/0xc0
[ 8176.425111] [c000000fe313b910] [c000000000196b9c] __wake_up_common+0xcc/0x290
[ 8176.425114] [c000000fe313b990] [c000000000196e0c] __wake_up_common_lock+0xac/0x110
[ 8176.425119] [c000000fe313ba10] [c0080000082acce8] kvmppc_vcpu_run_hv+0x400/0xb20 [kvm_hv]
[ 8176.425125] [c000000fe313bae0] [c0080000081098cc] kvmppc_vcpu_run+0x34/0x48 [kvm]
[ 8176.425132] [c000000fe313bb00] [c00800000810587c] kvm_arch_vcpu_ioctl_run+0x2f4/0x400 [kvm]
[ 8176.425138] [c000000fe313bb90] [c0080000080f7ac8] kvm_vcpu_ioctl+0x340/0x7d0 [kvm]
[ 8176.425141] [c000000fe313bd00] [c000000000445410] do_vfs_ioctl+0xe0/0xac0
[ 8176.425143] [c000000fe313bdb0] [c000000000445eb4] ksys_ioctl+0xc4/0x110
[ 8176.425146] [c000000fe313be00] [c000000000445f28] sys_ioctl+0x28/0x80
[ 8176.425149] [c000000fe313be20] [c00000000000b9c8] system_call+0x5c/0x68
[ 8176.425193] NMI backtrace for cpu 96
[ 8176.425196] CPU: 96 PID: 2573 Comm: CPU 2/KVM Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8176.425197] Call Trace:
[ 8176.425201] [c000000fe3127190] [c000000000aa5548] dump_stack+0xbc/0x104 (unreliable)
[ 8176.425204] [c000000fe31271d0] [c000000000ab04f0] nmi_cpu_backtrace+0xc0/0x120
[ 8176.425207] [c000000fe3127250] [c000000000ab06e8] nmi_trigger_cpumask_backtrace+0x198/0x1f0
[ 8176.425210] [c000000fe31272f0] [c000000000062c48] arch_trigger_cpumask_backtrace+0x28/0x40
[ 8176.425213] [c000000fe3127310] [c0000000001d4f50] rcu_dump_cpu_stacks+0xf8/0x154
[ 8176.425216] [c000000fe3127360] [c0000000001d39d8] rcu_sched_clock_irq+0x8b8/0xab0
[ 8176.425219] [c000000fe3127440] [c0000000001e2ed4] update_process_times+0x44/0xb0
[ 8176.425222] [c000000fe3127470] [c0000000001fc194] tick_sched_handle.isra.16+0x34/0xd0
[ 8176.425224] [c000000fe31274a0] [c0000000001fc5c8] tick_sched_timer+0x68/0xe0
[ 8176.425227] [c000000fe31274e0] [c0000000001e458c] __hrtimer_run_queues+0x17c/0x420
[ 8176.425230] [c000000fe3127560] [c0000000001e5298] hrtimer_interrupt+0x128/0x300
[ 8176.425233] [c000000fe3127610] [c000000000027da4] timer_interrupt+0x104/0x2e0
[ 8176.425236] [c000000fe3127670] [c000000000009408] decrementer_common+0x158/0x160
[ 8176.425241] --- interrupt: 901 at _raw_spin_lock+0x88/0x100
[ 8176.425241] LR = kvmppc_wait_for_exec+0x110/0x140 [kvm_hv]
[ 8176.425243] [c000000fe3127970] [c000000000ac4748] schedule+0x58/0x120 (unreliable)
[ 8176.425247] [c000000fe31279a0] [c0080000082a441c] kvmppc_wait_for_exec+0x104/0x140 [kvm_hv]
[ 8176.425251] [c000000fe3127a10] [c0080000082acf3c] kvmppc_vcpu_run_hv+0x654/0xb20 [kvm_hv]
[ 8176.425257] [c000000fe3127ae0] [c0080000081098cc] kvmppc_vcpu_run+0x34/0x48 [kvm]
[ 8176.425263] [c000000fe3127b00] [c00800000810587c] kvm_arch_vcpu_ioctl_run+0x2f4/0x400 [kvm]
[ 8176.425269] [c000000fe3127b90] [c0080000080f7ac8] kvm_vcpu_ioctl+0x340/0x7d0 [kvm]
[ 8176.425271] [c000000fe3127d00] [c000000000445410] do_vfs_ioctl+0xe0/0xac0
[ 8176.425273] [c000000fe3127db0] [c000000000445eb4] ksys_ioctl+0xc4/0x110
[ 8176.425276] [c000000fe3127e00] [c000000000445f28] sys_ioctl+0x28/0x80
[ 8176.425279] [c000000fe3127e20] [c00000000000b9c8] system_call+0x5c/0x68
[ 8176.425321] Sending NMI from CPU 96 to CPUs 128:
[17667518604.591966] Faulting instruction address: 0xc0000000002659a0
[ 8176.550754] watchdog: CPU 0 TB:4238323275375, last SMP heartbeat TB:4230131381087 (15999ms ago)
[17667518604.591971] Thread overran stack, or stack corrupted
[17667518604.591972] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8183.655643] CPU 128 didn't respond to backtrace IPI, inspecting paca.
[17667518611.840688] Faulting instruction address: 0xc0000000002659a0
[17667518611.840690] Thread overran stack, or stack corrupted
[ 8183.799480] irq_soft_mask: 0x01 in_mce: 0 in_nmi: 0 current: 2567 (qemu-system-ppc)
[17667518611.840701] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8183.799490] Back trace of paca->saved_r1 (0xc000001e54907e10) (possibly stale):
[ 8183.799491] Call Trace:
[17667518611.840710] Faulting instruction address: 0xc0000000002659a0
[17667518611.840712] Thread overran stack, or stack corrupted
[ 8184.730689] watchdog: BUG: soft lockup - CPU#120 stuck for 26s! [CPU 4/KVM:2635]
[17667518613.488533] BUG: Unable to handle kernel data access at 0xc0000007f9070c08
[ 8185.447326] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8185.447368] multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8185.447378] CPU: 120 PID: 2635 Comm: CPU 4/KVM Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8185.447381] NIP: c000000000205328 LR: c0000000002052dc CTR: c0000000000b00d0
[17667518613.488601] Faulting instruction address: 0xc0000000002659a0
[ 8185.996591] watchdog: CPU 40 self-detected hard LOCKUP @ rcu_dynticks_eqs_exit+0x38/0x70
[ 8185.996592] watchdog: CPU 40 TB:4243465734905, last heartbeat TB:4238343754479 (10003ms ago)
[ 8185.996593] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8185.996619] multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8185.996624] CPU: 40 PID: 0 Comm: swapper/40 Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8185.996624] NIP: c0000000001cd598 LR: c0000000001d2f58 CTR: c00000000084f030
[ 8185.996625] REGS: c000000fffe8fd70 TRAP: 0900 Tainted: G D EL (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[ 8185.996625] MSR: 900000000280b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE> CR: 28004422 XER: 00000000
[ 8185.996630] CFAR: c0000000001d2f54 IRQMASK: 1
[ 8185.996631] GPR00: c0000000001d2f58 c000000ff89fbe10 c0000000012e0800 0000000000000000
[ 8185.996633] GPR04: 0000000000000000 0000000000000000 c000000ffa897918 0000000000000002
[ 8185.996635] GPR08: 0000000001bb18c6 c000000ffa899d00 c000000ffa899de0 0000000000000002
[ 8185.996637] GPR12: c00000000084f030 c000000fffffee00 c000001fe07c7f90 0000000000000000
[ 8185.996639] GPR16: 0000000000000000 0000000000000000 0000000000000028 0000000000000030
[ 8185.996641] GPR20: c00000000004cdb0 c00000000004cd80 c0000000013120e0 c0000000013126a0
[ 8185.996643] GPR24: c00000000123b978 0000000000000001 0000000000080000 c000000ffa8978c0
[ 8185.996645] GPR28: c000000001312540 0000000000000001 0000000000000001 c000000ffa899d00
[ 8185.996647] NIP [c0000000001cd598] rcu_dynticks_eqs_exit+0x38/0x70
[ 8185.996647] LR [c0000000001d2f58] rcu_idle_exit+0x88/0xe0
[ 8185.996648] Call Trace:
[ 8185.996648] [c000000ff89fbe10] [0000010000000000] 0x10000000000 (unreliable)
[ 8185.996649] [c000000ff89fbe50] [c000000000178548] do_idle+0x1d8/0x3d0
[ 8185.996650] [c000000ff89fbed0] [c000000000178988] cpu_startup_entry+0x38/0x40
[ 8185.996651] [c000000ff89fbf00] [c00000000004f554] start_secondary+0x664/0x690
[ 8185.996652] [c000000ff89fbf90] [c00000000000b354] start_secondary_prolog+0x10/0x14
[ 8185.996653] Instruction dump:
[ 8185.996653] 7c0802a6 60000000 e94d0030 3d22ffc0 39299500 7d295214 394900e0 7c0004ac
[ 8185.996656] 38e00002 7d005028 7d074214 7d00512d <40c2fff4> 7c0004ac 71080001 4d820020
[ 8186.016579] watchdog: CPU 24 self-detected hard LOCKUP @ __switch_to+0x50/0x2c0
[ 8186.016580] watchdog: CPU 24 TB:4243475974736, last heartbeat TB:4238333515104 (10043ms ago)
[ 8186.016581] Modules linked in: vhost_net(E) vhost(E) tap(E) xt_CHECKSUM(E) nft_chain_nat(E) xt_MASQUERADE(E) nf_nat(E) xt_conntrack(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) ipt_REJECT(E) nf_reject_ipv4(E) nft_counter(E) xt_tcpudp(E) nft_compat(E) tun(E) kvm_hv(E) kvm_pr(E) kvm(E) nf_tables_set(E) nf_tables(E) nfnetlink(E) bridge(E) stp(E) llc(E) xfs(E) sg(E) ctr(E) vmx_crypto(E) gf128mul(E) ipmi_powernv(E) ipmi_devintf(E) powernv_rng(E) rng_core(E) ipmi_msghandler(E) powernv_op_panel(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_core(E) configfs(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) sunrpc(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) sr_mod(E) ses(E) cdrom(E) enclosure(E) scsi_transport_sas(E) sd_mod(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid1(E) raid0(E)
[ 8186.016602] multipath(E) linear(E) md_mod(E) xhci_pci(E) xhci_hcd(E) e1000e(E) usbcore(E) ptp(E) pps_core(E) ipr(E) usb_common(E)
[ 8186.016606] CPU: 24 PID: 0 Comm: swapper/24 Tainted: G D EL 5.4.0-0.bpo.3-powerpc64le #1 Debian 5.4.13-1~bpo10+1
[ 8186.016606] NIP: c00000000001de20 LR: c000000000ac4104 CTR: c000000000177f90
[ 8186.016607] REGS: c0000007ffd6fd70 TRAP: 0900 Tainted: G D EL (5.4.0-0.bpo.3-powerpc64le Debian 5.4.13-1~bpo10+1)
[ 8186.016607] MSR: 900000000280b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE> CR: 48008228 XER: 20000000
[ 8186.016611] CFAR: c000000000ac4100 IRQMASK: 1
[ 8186.016612] GPR00: c000000000ac4104 c0000007f6147cf0 c0000000012e0800 c0000007f6059e00
[ 8186.016613] GPR04: c000000fe0702400 c000000fe0702400 0000000000000000 0000000000000000
[ 8186.016615] GPR08: 0000000000000018 0000000000000000 c000000ff196b400 00000000000002c2
[ 8186.016617] GPR12: 0000000048004822 c0000007fffe4480 c000001fe0787f90 0000000000000000
[ 8186.016618] GPR16: 0000000000000000 0000000000000000 0000000000000018 0000000000000020
[ 8186.016620] GPR20: c00000000004cdb0 c0000007f605a5e8 00000007fb1c0000 c0000007fc098f00
[ 8186.016621] GPR24: c000000fe0703080 c0000007f605aa80 c000000000ed8f00 c0000007f6059e80
[ 8186.016623] GPR28: 0000000000000000 c000000fe0702400 c0000007f6059e00 c0000007f6059e00
[ 8186.016625] NIP [c00000000001de20] __switch_to+0x50/0x2c0
[ 8186.016625] LR [c000000000ac4104] __schedule+0x334/0x920
[ 8186.016625] Call Trace:
[ 8186.016626] [c0000007f6147cf0] [c000000000189e1c] pick_next_task_fair+0x1bc/0x4b0 (unreliable)
[ 8186.016627] [c0000007f6147d50] [c000000000ac4104] __schedule+0x334/0x920
[ 8186.016628] [c0000007f6147e30] [c000000000ac4d08] schedule_idle+0x38/0x70
[ 8186.016628] [c0000007f6147e50] [c0000000001785bc] do_idle+0x24c/0x3d0
[ 8186.016629] [c0000007f6147ed0] [c00000000017898c] cpu_startup_entry+0x3c/0x40
[ 8186.016630] [c0000007f6147f00] [c00000000004f554] start_secondary+0x664/0x690
[ 8186.016630] [c0000007f6147f90] [c00000000000b354] start_secondary_prolog+0x10/0x14
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
^ permalink raw reply
* Re: [PATCH] serial: cpm_uart: call cpm_muram_init before registering console
From: Christophe Leroy @ 2020-02-13 11:55 UTC (permalink / raw)
To: Rasmus Villemoes, Greg Kroah-Hartman, Jiri Slaby, Timur Tabi,
Li Yang
Cc: Scott Wood, linuxppc-dev, linux-kernel, linux-serial, Qiang Zhao
In-Reply-To: <20200213114342.21712-1-linux@rasmusvillemoes.dk>
Le 13/02/2020 à 12:43, Rasmus Villemoes a écrit :
> Christophe reports that powerpc 8xx silently fails to 5.6-rc1. It turns
> out I was wrong about nobody relying on the lazy initialization of the
> cpm/qe muram in commit b6231ea2b3c6 (soc: fsl: qe: drop broken lazy
> call of cpm_muram_init()).
>
> Rather than reinstating the somewhat dubious lazy call (initializing a
> currently held spinlock, and implicitly doing a GFP_KERNEL under that
> spinlock), make sure that cpm_muram_init() is called early enough - I
> thought the calls from the subsys_initcalls were good enough, but when
> used by console drivers, that's obviously not the
> case. cpm_muram_init() is safe to call twice (there's an early return
> if it is already initialized), so keep the call from cpm_init() - in
> case SERIAL_CPM_CONSOLE=n.
>
> Reported-by: Christophe Leroy <christophe.leroy@c-s.fr>
> Fixes: b6231ea2b3c6 (soc: fsl: qe: drop broken lazy call of cpm_muram_init())
> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Tested-by: Christophe Leroy <christophe.leroy@c-s.fr>
> ---
>
> Christophe, can I get you to add a formal Tested-by?
>
> I'm not sure which tree this should go through.
>
> drivers/tty/serial/cpm_uart/cpm_uart_core.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/tty/serial/cpm_uart/cpm_uart_core.c b/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> index 19d5a4cf29a6..d4b81b06e0cb 100644
> --- a/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> +++ b/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> @@ -1373,6 +1373,7 @@ static struct console cpm_scc_uart_console = {
>
> static int __init cpm_uart_console_init(void)
> {
> + cpm_muram_init();
> register_console(&cpm_scc_uart_console);
> return 0;
> }
>
^ permalink raw reply
* [PATCH] serial: cpm_uart: call cpm_muram_init before registering console
From: Rasmus Villemoes @ 2020-02-13 11:43 UTC (permalink / raw)
To: Greg Kroah-Hartman, Jiri Slaby, Timur Tabi, Li Yang,
Rasmus Villemoes
Cc: linux-kernel, Scott Wood, linux-serial, linuxppc-dev, Qiang Zhao
Christophe reports that powerpc 8xx silently fails to 5.6-rc1. It turns
out I was wrong about nobody relying on the lazy initialization of the
cpm/qe muram in commit b6231ea2b3c6 (soc: fsl: qe: drop broken lazy
call of cpm_muram_init()).
Rather than reinstating the somewhat dubious lazy call (initializing a
currently held spinlock, and implicitly doing a GFP_KERNEL under that
spinlock), make sure that cpm_muram_init() is called early enough - I
thought the calls from the subsys_initcalls were good enough, but when
used by console drivers, that's obviously not the
case. cpm_muram_init() is safe to call twice (there's an early return
if it is already initialized), so keep the call from cpm_init() - in
case SERIAL_CPM_CONSOLE=n.
Reported-by: Christophe Leroy <christophe.leroy@c-s.fr>
Fixes: b6231ea2b3c6 (soc: fsl: qe: drop broken lazy call of cpm_muram_init())
Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
---
Christophe, can I get you to add a formal Tested-by?
I'm not sure which tree this should go through.
drivers/tty/serial/cpm_uart/cpm_uart_core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/tty/serial/cpm_uart/cpm_uart_core.c b/drivers/tty/serial/cpm_uart/cpm_uart_core.c
index 19d5a4cf29a6..d4b81b06e0cb 100644
--- a/drivers/tty/serial/cpm_uart/cpm_uart_core.c
+++ b/drivers/tty/serial/cpm_uart/cpm_uart_core.c
@@ -1373,6 +1373,7 @@ static struct console cpm_scc_uart_console = {
static int __init cpm_uart_console_init(void)
{
+ cpm_muram_init();
register_console(&cpm_scc_uart_console);
return 0;
}
--
2.23.0
^ permalink raw reply related
* Re: [PATCH v7 4/4] powerpc: Book3S 64-bit "heavyweight" KASAN support
From: Christophe Leroy @ 2020-02-13 11:36 UTC (permalink / raw)
To: Daniel Axtens, linux-kernel, linux-mm, linuxppc-dev, kasan-dev,
aneesh.kumar, bsingharora
In-Reply-To: <20200213004752.11019-5-dja@axtens.net>
Le 13/02/2020 à 01:47, Daniel Axtens a écrit :
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index 497b7d0b2d7e..f1c54c08a88e 100644
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@ -169,7 +169,9 @@ config PPC
> select HAVE_ARCH_HUGE_VMAP if PPC_BOOK3S_64 && PPC_RADIX_MMU
> select HAVE_ARCH_JUMP_LABEL
> select HAVE_ARCH_KASAN if PPC32
> + select HAVE_ARCH_KASAN if PPC_BOOK3S_64 && PPC_RADIX_MMU
That's probably detail, but as it is necessary to deeply define the HW
when selecting that (I mean giving the exact amount of memory and with
restrictions like having a wholeblock memory), should it also depend of
EXPERT ?
> select HAVE_ARCH_KASAN_VMALLOC if PPC32
> + select HAVE_ARCH_KASAN_VMALLOC if PPC_BOOK3S_64 && PPC_RADIX_MMU
Maybe we could have
- select HAVE_ARCH_KASAN_VMALLOC if PPC32
+ select HAVE_ARCH_KASAN_VMALLOC if HAVE_ARCH_KASAN
> select HAVE_ARCH_KGDB
> select HAVE_ARCH_MMAP_RND_BITS
> select HAVE_ARCH_MMAP_RND_COMPAT_BITS if COMPAT
Christophe
^ permalink raw reply
* [Bug 206501] Kernel 5.6-rc1 fails to boot on a PowerMac G4 3,6 with CONFIG_VMAP_STACK=y: Oops! Machine check, sig: 7 [#1]
From: bugzilla-daemon @ 2020-02-13 11:34 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <bug-206501-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206501
--- Comment #8 from Erhard F. (erhard_f@mailbox.org) ---
(In reply to Christophe Leroy from comment #7)
> Can you try version v2 of the patch,
> https://patchwork.ozlabs.org/patch/1237387/
I can confirm that v2 works as intended. The G4 completes booting with
VMAP_STACK enabled and without producing further stack traces. Thanks!
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply
* Re: Problem booting a PowerBook G4 Aluminum after commit cd08f109 with CONFIG_VMAP_STACK=y
From: Christophe Leroy @ 2020-02-13 11:23 UTC (permalink / raw)
To: Larry Finger; +Cc: linuxppc-dev@lists.ozlabs.org
In-Reply-To: <1787b507-dfbf-7801-f7d4-a1547e9bd588@lwfinger.net>
On 02/12/2020 11:02 PM, Larry Finger wrote:
> On 2/11/20 1:23 PM, Christophe Leroy wrote:
>>
>> Can you send me a picture of that BUG Unable to handle kernel data
>> access with all the registers values etc..., together with the
>> matching vmlinux ?
>
> The vmlinux file was too big for your mailbox. You can download it from
> http://www.lwfinger.com/download/vmlinux.gz
>
Hi,
Is that the vmlinux that corresponds to:
BUG Unable to handle kernel data access at 0x007a84fc.
The faulting instruction address was 0x00013674
Nevertheless, do you have a picture of the said BUG/Oops to see all
registers ?
Because here, the address 0x13674 is not a data access:
c00135ec <ppc6xx_idle>:
c00135ec: 3c 60 00 00 lis r3,0
c00135f0: 3c 60 00 80 lis r3,128
c00135f4: 3c 80 c0 83 lis r4,-16253
c00135f8: 80 84 f2 80 lwz r4,-3456(r4)
c00135fc: 80 84 00 0c lwz r4,12(r4)
c0013600: 70 80 00 08 andi. r0,r4,8
c0013604: 41 82 00 18 beq c001361c <ppc6xx_idle+0x30>
c0013608: 3c 80 c0 84 lis r4,-16252
c001360c: 80 84 30 34 lwz r4,12340(r4)
c0013610: 2c 04 00 00 cmpwi r4,0
c0013614: 41 82 00 08 beq c001361c <ppc6xx_idle+0x30>
c0013618: 3c 60 00 40 lis r3,64
c001361c: 2c 03 00 00 cmpwi r3,0
c0013620: 4d 82 00 20 beqlr
c0013624: 74 60 00 40 andis. r0,r3,64
c0013628: 41 82 00 30 beq c0013658 <ppc6xx_idle+0x6c>
c001362c: 7c 96 fa a6 mfspr r4,1014
c0013630: 54 84 00 3a rlwinm r4,r4,0,0,29
c0013634: 7c 00 04 ac hwsync
c0013638: 7c 96 fb a6 mtspr 1014,r4
c001363c: 7c 00 04 ac hwsync
c0013640: 4c 00 01 2c isync
c0013644: 3c 80 c0 00 lis r4,-16384
c0013648: 7c 00 20 ac dcbf 0,r4
c001364c: 7c 00 20 ac dcbf 0,r4
c0013650: 7c 00 20 ac dcbf 0,r4
c0013654: 7c 00 20 ac dcbf 0,r4
c0013658: 3c 80 c0 7c lis r4,-16260
c001365c: 80 84 92 64 lwz r4,-28060(r4)
c0013660: 2c 04 00 00 cmpwi r4,0
c0013664: 41 82 00 10 beq c0013674 <ppc6xx_idle+0x88>
c0013668: 7c 91 fa a6 mfspr r4,1009
c001366c: 64 84 00 01 oris r4,r4,1
c0013670: 7c 91 fb a6 mtspr 1009,r4
>> c0013674: 7c 90 fa a6 mfspr r4,1008
c0013678: 3c a0 00 60 lis r5,96
c001367c: 64 a5 00 80 oris r5,r5,128
c0013680: 7c 84 28 78 andc r4,r4,r5
c0013684: 7c 84 1b 78 or r4,r4,r3
c0013688: 64 84 00 10 oris r4,r4,16
c001368c: 7c 90 fb a6 mtspr 1008,r4
c0013690: 7e 00 06 6c dssall
c0013694: 7c 00 04 ac hwsync
c0013698: 81 02 00 04 lwz r8,4(r2)
c001369c: 61 08 00 01 ori r8,r8,1
c00136a0: 91 02 00 04 stw r8,4(r2)
c00136a4: 7c e0 00 a6 mfmsr r7
c00136a8: 60 e7 80 00 ori r7,r7,32768
c00136ac: 64 e7 00 04 oris r7,r7,4
c00136b0: 7c 00 04 ac hwsync
c00136b4: 7c e0 01 24 mtmsr r7
c00136b8: 4c 00 01 2c isync
c00136bc: 4b ff ff f4 b c00136b0 <ppc6xx_idle+0xc4>
Thanks
Christophe
^ permalink raw reply
* Re: [PATCH 10/18] powerpc: Replace setup_irq() by request_irq()
From: Christophe Leroy @ 2020-02-13 10:59 UTC (permalink / raw)
To: afzal mohammed, linuxppc-dev, linux-kernel
Cc: Scott Wood, Thomas Gleixner, Paul Mackerras
In-Reply-To: <303393f75ede6d36241d41f501d9ad2a23897c3f.1581478324.git.afzal.mohd.ma@gmail.com>
Le 12/02/2020 à 09:04, afzal mohammed a écrit :
> request_irq() is preferred over setup_irq(). Existing callers of
> setup_irq() reached mostly via 'init_IRQ()' & 'time_init()', while
> memory allocators are ready by 'mm_init()'.
>
> Per tglx[1], setup_irq() existed in olden days when allocators were not
> ready by the time early interrupts were initialized.
>
> Hence replace setup_irq() by request_irq().
>
> Seldom remove_irq() usage has been observed coupled with setup_irq(),
> wherever that has been found, it too has been replaced by free_irq().
>
> [1] https://lkml.kernel.org/r/alpine.DEB.2.20.1710191609480.1971@nanos
>
> Signed-off-by: afzal mohammed <afzal.mohd.ma@gmail.com>
Tested-by: Christophe Leroy <christophe.leroy@c-s.fr> # for the 8xx parts
> ---
>
> Since cc'ing cover letter to all maintainers/reviewers would be too
> many, refer for cover letter,
> https://lkml.kernel.org/r/cover.1581478323.git.afzal.mohd.ma@gmail.com
>
> arch/powerpc/platforms/85xx/mpc85xx_cds.c | 10 +++-----
> arch/powerpc/platforms/8xx/cpm1.c | 9 ++-----
> arch/powerpc/platforms/8xx/m8xx_setup.c | 9 ++-----
> arch/powerpc/platforms/chrp/setup.c | 14 ++++------
> arch/powerpc/platforms/powermac/pic.c | 31 ++++++++++-------------
> arch/powerpc/platforms/powermac/smp.c | 9 ++-----
> 6 files changed, 27 insertions(+), 55 deletions(-)
>
^ permalink raw reply
* Re: [Regression 5.6-rc1][Bisected b6231ea2b3c6] Powerpc 8xx doesn't boot anymore
From: Christophe Leroy @ 2020-02-13 10:50 UTC (permalink / raw)
To: Rasmus Villemoes, Li Yang, Qiang Zhao, Greg Kroah-Hartman
Cc: Scott Wood, linuxppc-dev@lists.ozlabs.org, LKML, linux-arm-kernel
In-Reply-To: <59487f8a-fd2e-703d-d954-d263f756a3a0@rasmusvillemoes.dk>
Le 13/02/2020 à 10:37, Rasmus Villemoes a écrit :
> On 12/02/2020 15.50, Christophe Leroy wrote:
>>
>>
>> On 02/12/2020 02:24 PM, Christophe Leroy wrote:
>
>>> In your commit text you explain that cpm_muram_init() is called via
>>> subsys_initcall. But console init is done before that, so it cannot work.
>>>
>>> Do you have a fix for that ?
>>>
>>
>> The following patch allows powerpc 8xx to boot again. Don't know if
>> that's the good place and way to do the fix though.
>>
>> ---
>> diff --git a/drivers/tty/serial/cpm_uart/cpm_uart_core.c
>> b/drivers/tty/serial/cpm_uart/cpm_uart_core.c
>> index 4cabded8390b..341d682ec6eb 100644
>> --- a/drivers/tty/serial/cpm_uart/cpm_uart_core.c
>> +++ b/drivers/tty/serial/cpm_uart/cpm_uart_core.c
>> @@ -1351,6 +1351,7 @@ static int __init cpm_uart_console_setup(struct
>> console *co, char *options)
>> clrbits32(&pinfo->sccp->scc_gsmrl, SCC_GSMRL_ENR | SCC_GSMRL_ENT);
>> }
>>
>> + cpm_muram_init();
>> ret = cpm_uart_allocbuf(pinfo, 1);
>>
>> if (ret)
>
> Hmm, that seems to be a somewhat random place, making it hard to see
> that it is indeed early enough. Would it work to put it inside the
> console_initcall that registers the cpm console? I.e.
>
> static int __init cpm_uart_console_init(void)
> {
> + cpm_muram_init();
> register_console(&cpm_scc_uart_console);
> return 0;
> }
>
> console_initcall(cpm_uart_console_init);
>
Yes that works too.
Thanks
Christophe
^ permalink raw reply
* [Bug 206501] Kernel 5.6-rc1 fails to boot on a PowerMac G4 3,6 with CONFIG_VMAP_STACK=y: Oops! Machine check, sig: 7 [#1]
From: bugzilla-daemon @ 2020-02-13 10:45 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <bug-206501-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206501
--- Comment #7 from Christophe Leroy (christophe.leroy@c-s.fr) ---
Can you try version v2 of the patch,
https://patchwork.ozlabs.org/patch/1237387/
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply
* Re: [Regression 5.6-rc1][Bisected b6231ea2b3c6] Powerpc 8xx doesn't boot anymore
From: Christophe Leroy @ 2020-02-13 10:40 UTC (permalink / raw)
To: Rasmus Villemoes, Li Yang, Qiang Zhao, Greg Kroah-Hartman
Cc: Scott Wood, linuxppc-dev@lists.ozlabs.org, LKML, linux-arm-kernel
In-Reply-To: <f67f7566-24f2-9c71-36be-2e55ec436097@rasmusvillemoes.dk>
On 02/13/2020 07:45 AM, Rasmus Villemoes wrote:
> On 12/02/2020 15.24, Christophe Leroy wrote:
>> Hi Rasmus,
>>
>> Kernel 5.6-rc1 silently fails on boot.
>>
>> I bisected the problem to commit b6231ea2b3c6 ("soc: fsl: qe: drop
>> broken lazy call of cpm_muram_init()")
>>
>> I get a bad_page_fault() for an access at address 8 in
>> cpm_muram_alloc_common(), called from cpm_uart_console_setup() via
>> cpm_uart_allocbuf()
>
> Sorry about that. But I'm afraid I don't see what I could have done
> differently - the patch series, including b6231ea2b3c6, has been in
> -next since 20191210, both you and ppc-dev were cc'ed on the entire
> series (last revision sent November 28). And I've been dogfooding the
> patches on both arm- and ppc-derived boards ever since (but obviously
> only for a few cpus).
Yes, this patch series should have ringed a bell in my head, looks like
I'm the one who introduced this 4 years ago through commit 4d486e008379
("soc/fsl/qe: fix Oops on CPM1 (and likely CPM2)")
But I had completely forgotten that patch until I did some git blame
this morning on this lazy call.
>
>> Reverting the guilty commit on top of 5.6-rc1 is not trivial.
>>
>> In your commit text you explain that cpm_muram_init() is called via
>> subsys_initcall. But console init is done before that, so it cannot work.
>
> No, but neither did the code I removed seem to work - how does doing
> spin_lock_init on a held spinlock, and then unlocking it, work? Is
> everything-spinlock always a no-op in your configuration? And even so,
> I'd think a GFP_KERNEL allocation under spin_lock_irqsave() would
> trigger some splat somewhere?
>
> Please note I'm not claiming my patch is not at fault, it clearly is, I
> just want to try to understand how I could have been wrong about the
> "nobody can have been relying on it" part.
>
It seems spin_lock_init() does just nothing.
spin_lock_irqsave() just disable IRQs and increases preempt_count.
spin_lock_irqrestore() restore IRQ state, decreace preempt_count and
call preempt_schedule if preempt_count reaches 0.
Maybe with some debugging options like DEBUG_ATOMIC_SLEEP could detect it ?
>> Do you have a fix for that ?
>
> Not right now, but I'll have a look. It's true that the patch probably
> doesn't revert cleanly, but it shouldn't be hard to add back those few
> lines in the appropriate spot, with a big fat comment that this does
> something very fishy (at least as a temporary measure if we don't find a
> proper solution soonish).
>
Thanks
Christophe
^ permalink raw reply
* [PATCH v2] powerpc/32s: Fix DSI and ISI exceptions for CONFIG_VMAP_STACK
From: Christophe Leroy @ 2020-02-13 10:04 UTC (permalink / raw)
To: Benjamin Herrenschmidt, Paul Mackerras, Michael Ellerman,
Erhard F.
Cc: linuxppc-dev, linux-kernel
hash_page() needs to read page tables from kernel memory. When entire
kernel memory is mapped by BATs, which is normally the case when
CONFIG_STRICT_KERNEL_RWX is not set, it works even if the page hosting
the page table is not referenced in the MMU hash table.
However, if the page where the page table resides is not covered by
a BAT, a DSI fault can be encountered from hash_page(), and it loops
forever. This can happen when CONFIG_STRICT_KERNEL_RWX is selected
and the alignment of the different regions is too small to allow
covering the entire memory with BATs. This also happens when
CONFIG_DEBUG_PAGEALLOC is selected or when booting with 'nobats'
flag.
Also, if the page containing the kernel stack is not present in the
MMU hash table, registers cannot be saved and a recursive DSI fault
is encountered.
To allow hash_page() to properly do its job at all time and load the
MMU hash table whenever needed, it must run with data MMU disabled.
This means it must be called before re-enabling data MMU. To allow
this, registers clobbered by hash_page() and create_hpte() have to
be saved in the thread struct together with SRR0, SSR1, DAR and DSISR.
It is also necessary to ensure that DSI prolog doesn't overwrite
regs saved by prolog of the current running exception. That means:
- DSI can only use SPRN_SPRG_SCRATCH0
- Exceptions must free SPRN_SPRG_SCRATCH0 before writing to the stack.
This also fixes the Oops reported by Erhard when create_hpte() is
called by add_hash_page().
Fixes: cd08f109e262 ("powerpc/32s: Enable CONFIG_VMAP_STACK")
Reported-by: Erhard F. <erhard_f@mailbox.org>
Link: https://bugzilla.kernel.org/show_bug.cgi?id=206501
Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
---
v2: Reworked the DSI to call hash_page() even earlier and without
cloberring what ongoing exception saved in SPRG registers and
thread struct.
Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
---
arch/powerpc/include/asm/processor.h | 4 +
arch/powerpc/kernel/asm-offsets.c | 12 +++
arch/powerpc/kernel/head_32.S | 138 ++++++++++++++++++++++++++-
arch/powerpc/kernel/head_32.h | 13 ++-
arch/powerpc/mm/book3s32/hash_low.S | 52 +++++-----
arch/powerpc/mm/book3s32/mmu.c | 7 +-
6 files changed, 189 insertions(+), 37 deletions(-)
diff --git a/arch/powerpc/include/asm/processor.h b/arch/powerpc/include/asm/processor.h
index 8387698bd5b6..eedcbfb9a6ff 100644
--- a/arch/powerpc/include/asm/processor.h
+++ b/arch/powerpc/include/asm/processor.h
@@ -168,6 +168,10 @@ struct thread_struct {
unsigned long srr1;
unsigned long dar;
unsigned long dsisr;
+#ifdef CONFIG_PPC_BOOK3S_32
+ unsigned long r0, r3, r4, r5, r6, r8, r9, r11;
+ unsigned long lr, ctr;
+#endif
#endif
/* Debug Registers */
struct debug_reg debug;
diff --git a/arch/powerpc/kernel/asm-offsets.c b/arch/powerpc/kernel/asm-offsets.c
index c25e562f1cd9..fcf24a365fc0 100644
--- a/arch/powerpc/kernel/asm-offsets.c
+++ b/arch/powerpc/kernel/asm-offsets.c
@@ -132,6 +132,18 @@ int main(void)
OFFSET(SRR1, thread_struct, srr1);
OFFSET(DAR, thread_struct, dar);
OFFSET(DSISR, thread_struct, dsisr);
+#ifdef CONFIG_PPC_BOOK3S_32
+ OFFSET(THR0, thread_struct, r0);
+ OFFSET(THR3, thread_struct, r3);
+ OFFSET(THR4, thread_struct, r4);
+ OFFSET(THR5, thread_struct, r5);
+ OFFSET(THR6, thread_struct, r6);
+ OFFSET(THR8, thread_struct, r8);
+ OFFSET(THR9, thread_struct, r9);
+ OFFSET(THR11, thread_struct, r11);
+ OFFSET(THLR, thread_struct, lr);
+ OFFSET(THCTR, thread_struct, ctr);
+#endif
#endif
#ifdef CONFIG_SPE
OFFSET(THREAD_EVR0, thread_struct, evr[0]);
diff --git a/arch/powerpc/kernel/head_32.S b/arch/powerpc/kernel/head_32.S
index 0493fcac6409..5e1f0a796ec6 100644
--- a/arch/powerpc/kernel/head_32.S
+++ b/arch/powerpc/kernel/head_32.S
@@ -301,6 +301,39 @@ MachineCheck:
. = 0x300
DO_KVM 0x300
DataAccess:
+#ifdef CONFIG_VMAP_STACK
+ mtspr SPRN_SPRG_SCRATCH0,r10
+ mfspr r10, SPRN_SPRG_THREAD
+BEGIN_MMU_FTR_SECTION
+ stw r11, THR11(r10)
+ mfspr r10, SPRN_DSISR
+ mfcr r11
+#ifdef CONFIG_PPC_KUAP
+ andis. r10, r10, (DSISR_BAD_FAULT_32S | DSISR_DABRMATCH | DSISR_PROTFAULT)@h
+#else
+ andis. r10, r10, (DSISR_BAD_FAULT_32S | DSISR_DABRMATCH)@h
+#endif
+ mfspr r10, SPRN_SPRG_THREAD
+ beq hash_page_dsi
+.Lhash_page_dsi_cont:
+ mtcr r11
+ lwz r11, THR11(r10)
+END_MMU_FTR_SECTION_IFSET(MMU_FTR_HPTE_TABLE)
+ mtspr SPRN_SPRG_SCRATCH1,r11
+ mfspr r11, SPRN_DAR
+ stw r11, DAR(r10)
+ mfspr r11, SPRN_DSISR
+ stw r11, DSISR(r10)
+ mfspr r11, SPRN_SRR0
+ stw r11, SRR0(r10)
+ mfspr r11, SPRN_SRR1 /* check whether user or kernel */
+ stw r11, SRR1(r10)
+ mfcr r10
+ andi. r11, r11, MSR_PR
+
+ EXCEPTION_PROLOG_1
+ b handle_page_fault_tramp_1
+#else /* CONFIG_VMAP_STACK */
EXCEPTION_PROLOG handle_dar_dsisr=1
get_and_save_dar_dsisr_on_stack r4, r5, r11
BEGIN_MMU_FTR_SECTION
@@ -316,11 +349,32 @@ BEGIN_MMU_FTR_SECTION
FTR_SECTION_ELSE
b handle_page_fault_tramp_2
ALT_MMU_FTR_SECTION_END_IFSET(MMU_FTR_HPTE_TABLE)
+#endif /* CONFIG_VMAP_STACK */
/* Instruction access exception. */
. = 0x400
DO_KVM 0x400
InstructionAccess:
+#ifdef CONFIG_VMAP_STACK
+ mtspr SPRN_SPRG_SCRATCH0,r10
+ mtspr SPRN_SPRG_SCRATCH1,r11
+ mfspr r10, SPRN_SPRG_THREAD
+ mfspr r11, SPRN_SRR0
+ stw r11, SRR0(r10)
+ mfspr r11, SPRN_SRR1 /* check whether user or kernel */
+ stw r11, SRR1(r10)
+ mfcr r10
+BEGIN_MMU_FTR_SECTION
+ andis. r11, r11, SRR1_ISI_NOPT@h /* no pte found? */
+ bne hash_page_isi
+.Lhash_page_isi_cont:
+ mfspr r11, SPRN_SRR1 /* check whether user or kernel */
+END_MMU_FTR_SECTION_IFSET(MMU_FTR_HPTE_TABLE)
+ andi. r11, r11, MSR_PR
+
+ EXCEPTION_PROLOG_1
+ EXCEPTION_PROLOG_2
+#else /* CONFIG_VMAP_STACK */
EXCEPTION_PROLOG
andis. r0,r9,SRR1_ISI_NOPT@h /* no pte found? */
beq 1f /* if so, try to put a PTE */
@@ -329,6 +383,7 @@ InstructionAccess:
BEGIN_MMU_FTR_SECTION
bl hash_page
END_MMU_FTR_SECTION_IFSET(MMU_FTR_HPTE_TABLE)
+#endif /* CONFIG_VMAP_STACK */
1: mr r4,r12
andis. r5,r9,DSISR_SRR1_MATCH_32S@h /* Filter relevant SRR1 bits */
stw r4, _DAR(r11)
@@ -344,7 +399,7 @@ Alignment:
EXCEPTION_PROLOG handle_dar_dsisr=1
save_dar_dsisr_on_stack r4, r5, r11
addi r3,r1,STACK_FRAME_OVERHEAD
- EXC_XFER_STD(0x600, alignment_exception)
+ b alignment_exception_tramp
/* Program check exception */
EXCEPTION(0x700, ProgramCheck, program_check_exception, EXC_XFER_STD)
@@ -645,15 +700,96 @@ END_MMU_FTR_SECTION_IFSET(MMU_FTR_NEED_DTLB_SW_LRU)
. = 0x3000
+alignment_exception_tramp:
+ EXC_XFER_STD(0x600, alignment_exception)
+
handle_page_fault_tramp_1:
+#ifdef CONFIG_VMAP_STACK
+ EXCEPTION_PROLOG_2 handle_dar_dsisr=1
+#endif
lwz r4, _DAR(r11)
lwz r5, _DSISR(r11)
/* fall through */
handle_page_fault_tramp_2:
EXC_XFER_LITE(0x300, handle_page_fault)
+#ifdef CONFIG_VMAP_STACK
+.macro save_regs_thread thread
+ stw r0, THR0(\thread)
+ stw r3, THR3(\thread)
+ stw r4, THR4(\thread)
+ stw r5, THR5(\thread)
+ stw r6, THR6(\thread)
+ stw r8, THR8(\thread)
+ stw r9, THR9(\thread)
+ mflr r0
+ stw r0, THLR(\thread)
+ mfctr r0
+ stw r0, THCTR(\thread)
+.endm
+
+.macro restore_regs_thread thread
+ lwz r0, THLR(\thread)
+ mtlr r0
+ lwz r0, THCTR(\thread)
+ mtctr r0
+ lwz r0, THR0(\thread)
+ lwz r3, THR3(\thread)
+ lwz r4, THR4(\thread)
+ lwz r5, THR5(\thread)
+ lwz r6, THR6(\thread)
+ lwz r8, THR8(\thread)
+ lwz r9, THR9(\thread)
+.endm
+
+hash_page_dsi:
+ save_regs_thread r10
+ mfdsisr r3
+ mfdar r4
+ mfsrr1 r9
+ rlwinm r3, r3, 32 - 15, _PAGE_RW /* DSISR_STORE -> _PAGE_RW */
+ bl hash_page
+ mfspr r10, SPRN_SPRG_THREAD
+ restore_regs_thread r10
+ b .Lhash_page_dsi_cont
+
+hash_page_isi:
+ mr r11, r10
+ mfspr r10, SPRN_SPRG_THREAD
+ save_regs_thread r10
+ li r3, 0
+ lwz r4, SRR0(r10)
+ lwz r9, SRR1(r10)
+ bl hash_page
+ mfspr r10, SPRN_SPRG_THREAD
+ restore_regs_thread r10
+ mr r10, r11
+ b .Lhash_page_isi_cont
+
+ .globl fast_hash_page_return
+fast_hash_page_return:
+ andis. r10, r9, SRR1_ISI_NOPT@h /* Set on ISI, cleared on DSI */
+ mfspr r10, SPRN_SPRG_THREAD
+ restore_regs_thread r10
+ bne 1f
+
+ /* DSI */
+ mtcr r11
+ lwz r11, THR11(r10)
+ mfspr r10, SPRN_SPRG_SCRATCH0
+ SYNC
+ RFI
+
+1: /* ISI */
+ mtcr r11
+ mfspr r11, SPRN_SPRG_SCRATCH1
+ mfspr r10, SPRN_SPRG_SCRATCH0
+ SYNC
+ RFI
+
stack_overflow:
vmap_stack_overflow_exception
+#endif
AltiVecUnavailable:
EXCEPTION_PROLOG
diff --git a/arch/powerpc/kernel/head_32.h b/arch/powerpc/kernel/head_32.h
index a6a5fbbf8504..82bc0826108a 100644
--- a/arch/powerpc/kernel/head_32.h
+++ b/arch/powerpc/kernel/head_32.h
@@ -64,11 +64,19 @@
.endm
.macro EXCEPTION_PROLOG_2 handle_dar_dsisr=0
+#if defined(CONFIG_VMAP_STACK) && defined(CONFIG_PPC_BOOK3S)
+ mtcr r10
+#else
stw r10,_CCR(r11) /* save registers */
+#endif
+ mfspr r10,SPRN_SPRG_SCRATCH0
stw r12,GPR12(r11)
stw r9,GPR9(r11)
- mfspr r10,SPRN_SPRG_SCRATCH0
stw r10,GPR10(r11)
+#if defined(CONFIG_VMAP_STACK) && defined(CONFIG_PPC_BOOK3S)
+ mfcr r10
+ stw r10,_CCR(r11) /* save registers */
+#endif
mfspr r12,SPRN_SPRG_SCRATCH1
stw r12,GPR11(r11)
mflr r10
@@ -83,6 +91,9 @@
stw r10, _DSISR(r11)
.endif
lwz r9, SRR1(r12)
+#if defined(CONFIG_VMAP_STACK) && defined(CONFIG_PPC_BOOK3S)
+ andi. r10, r9, MSR_PR
+#endif
lwz r12, SRR0(r12)
#else
mfspr r12,SPRN_SRR0
diff --git a/arch/powerpc/mm/book3s32/hash_low.S b/arch/powerpc/mm/book3s32/hash_low.S
index c11b0a005196..2015c4f96238 100644
--- a/arch/powerpc/mm/book3s32/hash_low.S
+++ b/arch/powerpc/mm/book3s32/hash_low.S
@@ -25,12 +25,6 @@
#include <asm/feature-fixups.h>
#include <asm/code-patching-asm.h>
-#ifdef CONFIG_VMAP_STACK
-#define ADDR_OFFSET 0
-#else
-#define ADDR_OFFSET PAGE_OFFSET
-#endif
-
#ifdef CONFIG_SMP
.section .bss
.align 2
@@ -53,8 +47,8 @@ mmu_hash_lock:
.text
_GLOBAL(hash_page)
#ifdef CONFIG_SMP
- lis r8, (mmu_hash_lock - ADDR_OFFSET)@h
- ori r8, r8, (mmu_hash_lock - ADDR_OFFSET)@l
+ lis r8, (mmu_hash_lock - PAGE_OFFSET)@h
+ ori r8, r8, (mmu_hash_lock - PAGE_OFFSET)@l
lis r0,0x0fff
b 10f
11: lwz r6,0(r8)
@@ -72,12 +66,9 @@ _GLOBAL(hash_page)
cmplw 0,r4,r0
ori r3,r3,_PAGE_USER|_PAGE_PRESENT /* test low addresses as user */
mfspr r5, SPRN_SPRG_PGDIR /* phys page-table root */
-#ifdef CONFIG_VMAP_STACK
- tovirt(r5, r5)
-#endif
blt+ 112f /* assume user more likely */
- lis r5, (swapper_pg_dir - ADDR_OFFSET)@ha /* if kernel address, use */
- addi r5 ,r5 ,(swapper_pg_dir - ADDR_OFFSET)@l /* kernel page table */
+ lis r5, (swapper_pg_dir - PAGE_OFFSET)@ha /* if kernel address, use */
+ addi r5 ,r5 ,(swapper_pg_dir - PAGE_OFFSET)@l /* kernel page table */
rlwimi r3,r9,32-12,29,29 /* MSR_PR -> _PAGE_USER */
112:
#ifndef CONFIG_PTE_64BIT
@@ -89,9 +80,6 @@ _GLOBAL(hash_page)
lwzx r8,r8,r5 /* Get L1 entry */
rlwinm. r8,r8,0,0,20 /* extract pt base address */
#endif
-#ifdef CONFIG_VMAP_STACK
- tovirt(r8, r8)
-#endif
#ifdef CONFIG_SMP
beq- hash_page_out /* return if no mapping */
#else
@@ -143,30 +131,36 @@ retry:
bne- retry /* retry if someone got there first */
mfsrin r3,r4 /* get segment reg for segment */
+#ifndef CONFIG_VMAP_STACK
mfctr r0
stw r0,_CTR(r11)
+#endif
bl create_hpte /* add the hash table entry */
#ifdef CONFIG_SMP
eieio
- lis r8, (mmu_hash_lock - ADDR_OFFSET)@ha
+ lis r8, (mmu_hash_lock - PAGE_OFFSET)@ha
li r0,0
- stw r0, (mmu_hash_lock - ADDR_OFFSET)@l(r8)
+ stw r0, (mmu_hash_lock - PAGE_OFFSET)@l(r8)
#endif
+#ifdef CONFIG_VMAP_STACK
+ b fast_hash_page_return
+#else
/* Return from the exception */
lwz r5,_CTR(r11)
mtctr r5
lwz r0,GPR0(r11)
lwz r8,GPR8(r11)
b fast_exception_return
+#endif
#ifdef CONFIG_SMP
hash_page_out:
eieio
- lis r8, (mmu_hash_lock - ADDR_OFFSET)@ha
+ lis r8, (mmu_hash_lock - PAGE_OFFSET)@ha
li r0,0
- stw r0, (mmu_hash_lock - ADDR_OFFSET)@l(r8)
+ stw r0, (mmu_hash_lock - PAGE_OFFSET)@l(r8)
blr
#endif /* CONFIG_SMP */
@@ -341,7 +335,7 @@ END_FTR_SECTION_IFCLR(CPU_FTR_NEED_COHERENT)
patch_site 1f, patch__hash_page_A1
patch_site 2f, patch__hash_page_A2
/* Get the address of the primary PTE group in the hash table (r3) */
-0: lis r0, (Hash_base - ADDR_OFFSET)@h /* base address of hash table */
+0: lis r0, (Hash_base - PAGE_OFFSET)@h /* base address of hash table */
1: rlwimi r0,r3,LG_PTEG_SIZE,HASH_LEFT,HASH_RIGHT /* VSID -> hash */
2: rlwinm r3,r4,20+LG_PTEG_SIZE,HASH_LEFT,HASH_RIGHT /* PI -> hash */
xor r3,r3,r0 /* make primary hash */
@@ -355,10 +349,10 @@ END_FTR_SECTION_IFCLR(CPU_FTR_NEED_COHERENT)
beq+ 10f /* no PTE: go look for an empty slot */
tlbie r4
- lis r4, (htab_hash_searches - ADDR_OFFSET)@ha
- lwz r6, (htab_hash_searches - ADDR_OFFSET)@l(r4)
+ lis r4, (htab_hash_searches - PAGE_OFFSET)@ha
+ lwz r6, (htab_hash_searches - PAGE_OFFSET)@l(r4)
addi r6,r6,1 /* count how many searches we do */
- stw r6, (htab_hash_searches - ADDR_OFFSET)@l(r4)
+ stw r6, (htab_hash_searches - PAGE_OFFSET)@l(r4)
/* Search the primary PTEG for a PTE whose 1st (d)word matches r5 */
mtctr r0
@@ -390,10 +384,10 @@ END_FTR_SECTION_IFCLR(CPU_FTR_NEED_COHERENT)
beq+ found_empty
/* update counter of times that the primary PTEG is full */
- lis r4, (primary_pteg_full - ADDR_OFFSET)@ha
- lwz r6, (primary_pteg_full - ADDR_OFFSET)@l(r4)
+ lis r4, (primary_pteg_full - PAGE_OFFSET)@ha
+ lwz r6, (primary_pteg_full - PAGE_OFFSET)@l(r4)
addi r6,r6,1
- stw r6, (primary_pteg_full - ADDR_OFFSET)@l(r4)
+ stw r6, (primary_pteg_full - PAGE_OFFSET)@l(r4)
patch_site 0f, patch__hash_page_C
/* Search the secondary PTEG for an empty slot */
@@ -427,8 +421,8 @@ END_FTR_SECTION_IFCLR(CPU_FTR_NEED_COHERENT)
* lockup here but that shouldn't happen
*/
-1: lis r4, (next_slot - ADDR_OFFSET)@ha /* get next evict slot */
- lwz r6, (next_slot - ADDR_OFFSET)@l(r4)
+1: lis r4, (next_slot - PAGE_OFFSET)@ha /* get next evict slot */
+ lwz r6, (next_slot - PAGE_OFFSET)@l(r4)
addi r6,r6,HPTE_SIZE /* search for candidate */
andi. r6,r6,7*HPTE_SIZE
stw r6,next_slot@l(r4)
diff --git a/arch/powerpc/mm/book3s32/mmu.c b/arch/powerpc/mm/book3s32/mmu.c
index 0a1c65a2c565..b47c75f5386d 100644
--- a/arch/powerpc/mm/book3s32/mmu.c
+++ b/arch/powerpc/mm/book3s32/mmu.c
@@ -413,7 +413,7 @@ void __init MMU_init_hw(void)
void __init MMU_init_hw_patch(void)
{
unsigned int hmask = Hash_mask >> (16 - LG_HPTEG_SIZE);
- unsigned int hash;
+ unsigned int hash = (unsigned int)Hash - PAGE_OFFSET;
if (ppc_md.progress)
ppc_md.progress("hash:patch", 0x345);
@@ -425,11 +425,6 @@ void __init MMU_init_hw_patch(void)
/*
* Patch up the instructions in hashtable.S:create_hpte
*/
- if (IS_ENABLED(CONFIG_VMAP_STACK))
- hash = (unsigned int)Hash;
- else
- hash = (unsigned int)Hash - PAGE_OFFSET;
-
modify_instruction_site(&patch__hash_page_A0, 0xffff, hash >> 16);
modify_instruction_site(&patch__hash_page_A1, 0x7c0, hash_mb << 6);
modify_instruction_site(&patch__hash_page_A2, 0x7c0, hash_mb2 << 6);
--
2.25.0
^ permalink raw reply related
* [PATCH v2] powerpc/time: Replace <linux/clk-provider.h> by <linux/of_clk.h>
From: Geert Uytterhoeven @ 2020-02-13 8:38 UTC (permalink / raw)
To: Benjamin Herrenschmidt, Paul Mackerras, Michael Ellerman
Cc: linuxppc-dev, linux-clk, Geert Uytterhoeven, linux-kernel
The PowerPC time code is not a clock provider, and just needs to call
of_clk_init().
Hence it can include <linux/of_clk.h> instead of <linux/clk-provider.h>.
Remove the #ifdef protecting the of_clk_init() call, as a stub is
available for the !CONFIG_COMMON_CLK case.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
---
v2:
- Add Reviewed-by,
- Remove #ifdef.
---
arch/powerpc/kernel/time.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/powerpc/kernel/time.c b/arch/powerpc/kernel/time.c
index 1168e8b37e30696d..8ce3fa8a8c0a2d63 100644
--- a/arch/powerpc/kernel/time.c
+++ b/arch/powerpc/kernel/time.c
@@ -50,7 +50,7 @@
#include <linux/irq.h>
#include <linux/delay.h>
#include <linux/irq_work.h>
-#include <linux/clk-provider.h>
+#include <linux/of_clk.h>
#include <linux/suspend.h>
#include <linux/sched/cputime.h>
#include <linux/processor.h>
@@ -1158,9 +1158,7 @@ void __init time_init(void)
init_decrementer_clockevent();
tick_setup_hrtimer_broadcast();
-#ifdef CONFIG_COMMON_CLK
of_clk_init(NULL);
-#endif
}
/*
--
2.17.1
^ permalink raw reply related
* Re: [Regression 5.6-rc1][Bisected b6231ea2b3c6] Powerpc 8xx doesn't boot anymore
From: Rasmus Villemoes @ 2020-02-13 9:37 UTC (permalink / raw)
To: Christophe Leroy, Li Yang, Qiang Zhao, Greg Kroah-Hartman
Cc: Scott Wood, linuxppc-dev@lists.ozlabs.org, LKML, linux-arm-kernel
In-Reply-To: <aee10440-c244-7c93-d3bb-fd29d8a83be4@c-s.fr>
On 12/02/2020 15.50, Christophe Leroy wrote:
>
>
> On 02/12/2020 02:24 PM, Christophe Leroy wrote:
>> In your commit text you explain that cpm_muram_init() is called via
>> subsys_initcall. But console init is done before that, so it cannot work.
>>
>> Do you have a fix for that ?
>>
>
> The following patch allows powerpc 8xx to boot again. Don't know if
> that's the good place and way to do the fix though.
>
> ---
> diff --git a/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> b/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> index 4cabded8390b..341d682ec6eb 100644
> --- a/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> +++ b/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> @@ -1351,6 +1351,7 @@ static int __init cpm_uart_console_setup(struct
> console *co, char *options)
> clrbits32(&pinfo->sccp->scc_gsmrl, SCC_GSMRL_ENR | SCC_GSMRL_ENT);
> }
>
> + cpm_muram_init();
> ret = cpm_uart_allocbuf(pinfo, 1);
>
> if (ret)
Hmm, that seems to be a somewhat random place, making it hard to see
that it is indeed early enough. Would it work to put it inside the
console_initcall that registers the cpm console? I.e.
static int __init cpm_uart_console_init(void)
{
+ cpm_muram_init();
register_console(&cpm_scc_uart_console);
return 0;
}
console_initcall(cpm_uart_console_init);
Rasmus
^ permalink raw reply
* Re: [PATCH v5 01/10] capabilities: introduce CAP_PERFMON to kernel and user space
From: Alexey Budankov @ 2020-02-13 9:05 UTC (permalink / raw)
To: Stephen Smalley
Cc: Mark Rutland, Song Liu, Peter Zijlstra,
joonas.lahtinen@linux.intel.com, Will Deacon, Alexei Starovoitov,
Stephane Eranian, james.bottomley@hansenpartnership.com,
Paul Mackerras, Jiri Olsa, Alexei Starovoitov, Andi Kleen,
Igor Lubashev, James Morris, Alexander Shishkin, Ingo Molnar,
oprofile-list, Serge Hallyn, Robert Richter,
selinux@vger.kernel.org, intel-gfx@lists.freedesktop.org,
jani.nikula@linux.intel.com, Arnaldo Carvalho de Melo,
rodrigo.vivi@intel.com, Namhyung Kim, Thomas Gleixner,
linux-arm-kernel, linux-parisc@vger.kernel.org, linux-kernel,
Lionel Landwerlin, Andy Lutomirski,
linux-perf-users@vger.kernel.org,
linux-security-module@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
In-Reply-To: <46751eb9-deca-53cc-95fb-1602cfdf62a2@tycho.nsa.gov>
On 12.02.2020 20:09, Stephen Smalley wrote:
> On 2/12/20 11:56 AM, Alexey Budankov wrote:
>>
>>
>> On 12.02.2020 18:45, Stephen Smalley wrote:
>>> On 2/12/20 10:21 AM, Stephen Smalley wrote:
>>>> On 2/12/20 8:53 AM, Alexey Budankov wrote:
>>>>> On 12.02.2020 16:32, Stephen Smalley wrote:
>>>>>> On 2/12/20 3:53 AM, Alexey Budankov wrote:
>>>>>>> Hi Stephen,
>>>>>>>
>>>>>>> On 22.01.2020 17:07, Stephen Smalley wrote:
>>>>>>>> On 1/22/20 5:45 AM, Alexey Budankov wrote:
>>>>>>>>>
>>>>>>>>> On 21.01.2020 21:27, Alexey Budankov wrote:
>>>>>>>>>>
>>>>>>>>>> On 21.01.2020 20:55, Alexei Starovoitov wrote:
>>>>>>>>>>> On Tue, Jan 21, 2020 at 9:31 AM Alexey Budankov
>>>>>>>>>>> <alexey.budankov@linux.intel.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 21.01.2020 17:43, Stephen Smalley wrote:
>>>>>>>>>>>>> On 1/20/20 6:23 AM, Alexey Budankov wrote:
>>>>>>>>>>>>>>
>>>>>>> <SNIP>
>>>>>>>>>>>>>> Introduce CAP_PERFMON capability designed to secure system performance
>>>>>>>>>>>>>
>>>>>>>>>>>>> Why _noaudit()? Normally only used when a permission failure is non-fatal to the operation. Otherwise, we want the audit message.
>>>>>>>>>
>>>>>>>>> So far so good, I suggest using the simplest version for v6:
>>>>>>>>>
>>>>>>>>> static inline bool perfmon_capable(void)
>>>>>>>>> {
>>>>>>>>> return capable(CAP_PERFMON) || capable(CAP_SYS_ADMIN);
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> It keeps the implementation simple and readable. The implementation is more
>>>>>>>>> performant in the sense of calling the API - one capable() call for CAP_PERFMON
>>>>>>>>> privileged process.
>>>>>>>>>
>>>>>>>>> Yes, it bloats audit log for CAP_SYS_ADMIN privileged and unprivileged processes,
>>>>>>>>> but this bloating also advertises and leverages using more secure CAP_PERFMON
>>>>>>>>> based approach to use perf_event_open system call.
>>>>>>>>
>>>>>>>> I can live with that. We just need to document that when you see both a CAP_PERFMON and a CAP_SYS_ADMIN audit message for a process, try only allowing CAP_PERFMON first and see if that resolves the issue. We have a similar issue with CAP_DAC_READ_SEARCH versus CAP_DAC_OVERRIDE.
>>>>>>>
>>>>>>> I am trying to reproduce this double logging with CAP_PERFMON.
>>>>>>> I am using the refpolicy version with enabled perf_event tclass [1], in permissive mode.
>>>>>>> When running perf stat -a I am observing this AVC audit messages:
>>>>>>>
>>>>>>> type=AVC msg=audit(1581496695.666:8691): avc: denied { open } for pid=2779 comm="perf" scontext=user_u:user_r:user_systemd_t tcontext=user_u:user_r:user_systemd_t tclass=perf_event permissive=1
>>>>>>> type=AVC msg=audit(1581496695.666:8691): avc: denied { kernel } for pid=2779 comm="perf" scontext=user_u:user_r:user_systemd_t tcontext=user_u:user_r:user_systemd_t tclass=perf_event permissive=1
>>>>>>> type=AVC msg=audit(1581496695.666:8691): avc: denied { cpu } for pid=2779 comm="perf" scontext=user_u:user_r:user_systemd_t tcontext=user_u:user_r:user_systemd_t tclass=perf_event permissive=1
>>>>>>> type=AVC msg=audit(1581496695.666:8692): avc: denied { write } for pid=2779 comm="perf" scontext=user_u:user_r:user_systemd_t tcontext=user_u:user_r:user_systemd_t tclass=perf_event permissive=1
>>>>>>>
>>>>>>> However there is no capability related messages around. I suppose my refpolicy should
>>>>>>> be modified somehow to observe capability related AVCs.
>>>>>>>
>>>>>>> Could you please comment or clarify on how to enable caps related AVCs in order
>>>>>>> to test the concerned logging.
>>>>>>
>>>>>> The new perfmon permission has to be defined in your policy; you'll have a message in dmesg about "Permission perfmon in class capability2 not defined in policy.". You can either add it to the common cap2 definition in refpolicy/policy/flask/access_vectors and rebuild your policy or extract your base module as CIL, add it there, and insert the updated module.
>>>>>
>>>>> Yes, I already have it like this:
>>>>> common cap2
>>>>> {
>>>>> <------>mac_override<--># unused by SELinux
>>>>> <------>mac_admin
>>>>> <------>syslog
>>>>> <------>wake_alarm
>>>>> <------>block_suspend
>>>>> <------>audit_read
>>>>> <------>perfmon
>>>>> }
>>>>>
>>>>> dmesg stopped reporting perfmon as not defined but audit.log still doesn't report CAP_PERFMON denials.
>>>>> BTW, audit even doesn't report CAP_SYS_ADMIN denials, however perfmon_capable() does check for it.
>>>>
>>>> Some denials may be silenced by dontaudit rules; semodule -DB will strip those and semodule -B will restore them. Other possibility is that the process doesn't have CAP_PERFMON in its effective set and therefore never reaches SELinux at all; denied first by the capability module.
>>>
>>> Also, the fact that your denials are showing up in user_systemd_t suggests that something is off in your policy or userspace/distro; I assume that is a domain type for the systemd --user instance, but your shell and commands shouldn't be running in that domain (user_t would be more appropriate for that).
>>
>> It is user_t for local terminal session:
>> ps -Z
>> LABEL PID TTY TIME CMD
>> user_u:user_r:user_t 11317 pts/9 00:00:00 bash
>> user_u:user_r:user_t 11796 pts/9 00:00:00 ps
>>
>> For local terminal root session:
>> ps -Z
>> LABEL PID TTY TIME CMD
>> user_u:user_r:user_su_t 2926 pts/3 00:00:00 bash
>> user_u:user_r:user_su_t 10995 pts/3 00:00:00 ps
>>
>> For remote ssh session:
>> ps -Z
>> LABEL PID TTY TIME CMD
>> user_u:user_r:user_t 7540 pts/8 00:00:00 ps
>> user_u:user_r:user_systemd_t 8875 pts/8 00:00:00 bash
>
> That's a bug in either your policy or your userspace/distro integration. In any event, unless user_systemd_t is allowed all capability2 permissions by your policy, you should see the denials if CAP_PERFMON is set in the effective capability set of the process.
>
That all seems to be true. After instrumentation, rebuilding and rebooting, in CAP_PERFMON case:
$ getcap perf
perf = cap_sys_ptrace,cap_syslog,cap_perfmon+ep
$ perf stat -a
type=AVC msg=audit(1581580399.165:784): avc: denied { open } for pid=8859 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580399.165:785): avc: denied { perfmon } for pid=8859 comm="perf" capability=38 scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=capability2 permissive=1
type=AVC msg=audit(1581580399.165:786): avc: denied { kernel } for pid=8859 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580399.165:787): avc: denied { cpu } for pid=8859 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580399.165:788): avc: denied { write } for pid=8859 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580408.078:791): avc: denied { read } for pid=8859 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
dmesg:
[ 137.877713] security_capable(0000000071f7ee6e, 000000009dd7a5fc, CAP_PERFMON, 0) = ?
[ 137.877774] cread_has_capability(CAP_PERFMON) = 0
[ 137.877775] prior avc_audit(CAP_PERFMON)
[ 137.877779] security_capable(0000000071f7ee6e, 000000009dd7a5fc, CAP_PERFMON, 0) = 0
[ 137.877784] security_capable(0000000071f7ee6e, 000000009dd7a5fc, CAP_PERFMON, 0) = ?
[ 137.877785] cread_has_capability(CAP_PERFMON) = 0
[ 137.877786] security_capable(0000000071f7ee6e, 000000009dd7a5fc, CAP_PERFMON, 0) = 0
[ 137.877794] security_capable(0000000071f7ee6e, 000000009dd7a5fc, CAP_PERFMON, 0) = ?
[ 137.877795] cread_has_capability(CAP_PERFMON) = 0
[ 137.877796] security_capable(0000000071f7ee6e, 000000009dd7a5fc, CAP_PERFMON, 0) = 0
...
in CAP_SYS_ADMIN case:
$ getcap perf
perf = cap_sys_ptrace,cap_sys_admin,cap_syslog+ep
$ perf stat -a
type=AVC msg=audit(1581580747.928:835): avc: denied { open } for pid=8927 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580747.928:836): avc: denied { cpu } for pid=8927 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580747.928:837): avc: denied { kernel } for pid=8927 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580747.928:838): avc: denied { read } for pid=8927 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580747.928:839): avc: denied { write } for pid=8927 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
...
$ perf record -- ls
...
type=AVC msg=audit(1581580747.930:843): avc: denied { sys_ptrace } for pid=8927 comm="perf" capability=19 scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=capability permissive=1
...
dmesg:
[ 276.714266] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_PERFMON, 0) = ?
[ 276.714268] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_PERFMON, 0) = -1
[ 276.714269] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_SYS_ADMIN, 0) = ?
[ 276.714270] cread_has_capability(CAP_SYS_ADMIN) = 0
[ 276.714270] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_SYS_ADMIN, 0) = 0
[ 276.714287] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_PERFMON, 0) = ?
[ 276.714287] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_PERFMON, 0) = -1
[ 276.714288] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_SYS_ADMIN, 0) = ?
[ 276.714288] cread_has_capability(CAP_SYS_ADMIN) = 0
[ 276.714289] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_SYS_ADMIN, 0) = 0
[ 276.714294] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_PERFMON, 0) = ?
[ 276.714295] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_PERFMON, 0) = -1
[ 276.714295] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_SYS_ADMIN, 0) = ?
[ 276.714296] cread_has_capability(CAP_SYS_ADMIN) = 0
[ 276.714296] security_capable(000000006b09ad8a, 000000009dd7a5fc, CAP_SYS_ADMIN, 0) = 0
...
in unprivileged case:
$ getcap perf
perf =
$ perf stat -a; perf record -a
...
dmesg:
[ 947.275611] security_capable(00000000d3a75377, 000000009dd7a5fc, CAP_PERFMON, 0) = ?
[ 947.275613] security_capable(00000000d3a75377, 000000009dd7a5fc, CAP_PERFMON, 0) = -1
[ 947.275614] security_capable(00000000d3a75377, 000000009dd7a5fc, CAP_SYS_ADMIN, 0) = ?
[ 947.275615] security_capable(00000000d3a75377, 000000009dd7a5fc, CAP_SYS_ADMIN, 0) = -1
[ 947.275636] security_capable(00000000d3a75377, 000000009dd7a5fc, CAP_PERFMON, 0) = ?
[ 947.275637] security_capable(00000000d3a75377, 000000009dd7a5fc, CAP_PERFMON, 0) = -1
[ 947.275638] security_capable(00000000d3a75377, 000000009dd7a5fc, CAP_SYS_ADMIN, 0) = ?
[ 947.275638] security_capable(00000000d3a75377, 000000009dd7a5fc, CAP_SYS_ADMIN, 0) = -1
...
So it looks like CAP_PERFMON and CAP_SYS_ADMIN are not ever logged by AVC simultaneously,
in the current LSM and perfmon_capable() implementations.
If perfmon is granted:
perfmon is not logged by capabilities, perfmon is logged by AVC,
no check for sys_admin by perfmon_capable().
If perfmon is not granted but sys_admin is granted:
perfmon is not logged by capabilities, AVC logging is not called for perfmon,
sys_admin is not logged by capabilities, sys_admin is not logged by AVC, for some intended reason?
No caps are granted:
AVC logging is not called either for perfmon or for sys_admin.
BTW, is there a way to may be drop some AV cache so denials would appear in audit in the next AV access?
Well, I guess you have initially mentioned some case similar to this (note that ids are not the same but pids= are):
type=AVC msg=audit(1581580399.165:784): avc: denied { open } for pid=8859 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580399.165:785): avc: denied { perfmon } for pid=8859 comm="perf" capability=38 scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=capability2 permissive=1
type=AVC msg=audit( . : ): avc: denied { sys_admin } for pid=8859 comm="perf" capability=21 scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=capability2 permissive=1
type=AVC msg=audit(1581580399.165:786): avc: denied { kernel } for pid=8859 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580399.165:787): avc: denied { cpu } for pid=8859 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580399.165:788): avc: denied { write } for pid=8859 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
type=AVC msg=audit(1581580408.078:791): avc: denied { read } for pid=8859 comm="perf" scontext=user_u:user_r:user_t tcontext=user_u:user_r:user_t tclass=perf_event permissive=1
So the message could be like this:
"If audit logs for a process using perf_events related syscalls i.e. perf_event_open(), read(), write(),
ioctl(), mmap() contain denials both for CAP_PERFMON and CAP_SYS_ADMIN capabilities then providing the
process with CAP_PERFMON capability singly is the secure preferred approach to resolve access denials
to performance monitoring and observability operations."
~Alexey
^ permalink raw reply
* Re: [Regression 5.6-rc1][Bisected b6231ea2b3c6] Powerpc 8xx doesn't boot anymore
From: Rasmus Villemoes @ 2020-02-13 7:45 UTC (permalink / raw)
To: Christophe Leroy, Li Yang, Qiang Zhao, Greg Kroah-Hartman
Cc: Scott Wood, linuxppc-dev@lists.ozlabs.org, LKML, linux-arm-kernel
In-Reply-To: <0d45fa64-51ee-0052-cb34-58c770c5b3ce@c-s.fr>
On 12/02/2020 15.24, Christophe Leroy wrote:
> Hi Rasmus,
>
> Kernel 5.6-rc1 silently fails on boot.
>
> I bisected the problem to commit b6231ea2b3c6 ("soc: fsl: qe: drop
> broken lazy call of cpm_muram_init()")
>
> I get a bad_page_fault() for an access at address 8 in
> cpm_muram_alloc_common(), called from cpm_uart_console_setup() via
> cpm_uart_allocbuf()
Sorry about that. But I'm afraid I don't see what I could have done
differently - the patch series, including b6231ea2b3c6, has been in
-next since 20191210, both you and ppc-dev were cc'ed on the entire
series (last revision sent November 28). And I've been dogfooding the
patches on both arm- and ppc-derived boards ever since (but obviously
only for a few cpus).
> Reverting the guilty commit on top of 5.6-rc1 is not trivial.
>
> In your commit text you explain that cpm_muram_init() is called via
> subsys_initcall. But console init is done before that, so it cannot work.
No, but neither did the code I removed seem to work - how does doing
spin_lock_init on a held spinlock, and then unlocking it, work? Is
everything-spinlock always a no-op in your configuration? And even so,
I'd think a GFP_KERNEL allocation under spin_lock_irqsave() would
trigger some splat somewhere?
Please note I'm not claiming my patch is not at fault, it clearly is, I
just want to try to understand how I could have been wrong about the
"nobody can have been relying on it" part.
> Do you have a fix for that ?
Not right now, but I'll have a look. It's true that the patch probably
doesn't revert cleanly, but it shouldn't be hard to add back those few
lines in the appropriate spot, with a big fat comment that this does
something very fishy (at least as a temporary measure if we don't find a
proper solution soonish).
Rasmus
^ permalink raw reply
* RE: [Regression 5.6-rc1][Bisected b6231ea2b3c6] Powerpc 8xx doesn't boot anymore
From: Qiang Zhao @ 2020-02-13 6:36 UTC (permalink / raw)
To: Christophe Leroy, Rasmus Villemoes, Leo Li, Greg Kroah-Hartman
Cc: Scott Wood, linuxppc-dev@lists.ozlabs.org, LKML,
linux-arm-kernel@lists.infradead.org
In-Reply-To: <0c217693-7c73-1696-8a86-e81dbabefe02@c-s.fr>
On 02/13/2020 14:17 PM, Christophe Leroy wrote:
> -----Original Message-----
> From: Christophe Leroy <christophe.leroy@c-s.fr>
> Sent: 2020年2月13日 14:17
> To: Qiang Zhao <qiang.zhao@nxp.com>; Rasmus Villemoes
> <linux@rasmusvillemoes.dk>; Leo Li <leoyang.li@nxp.com>; Greg
> Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Scott Wood <oss@buserror.net>; linuxppc-dev@lists.ozlabs.org; LKML
> <linux-kernel@vger.kernel.org>; linux-arm-kernel@lists.infradead.org
> Subject: Re: [Regression 5.6-rc1][Bisected b6231ea2b3c6] Powerpc 8xx doesn't
> boot anymore
>
>
>
> Le 13/02/2020 à 04:35, Qiang Zhao a écrit :
> > On 02/12/2020 22:50 PM, Christophe Leroy wrote:
> >> -----Original Message-----
> >> From: Christophe Leroy <christophe.leroy@c-s.fr>
> >> Sent: 2020年2月12日 22:50
> >> To: Rasmus Villemoes <linux@rasmusvillemoes.dk>; Leo Li
> >> <leoyang.li@nxp.com>; Qiang Zhao <qiang.zhao@nxp.com>; Greg
> >> Kroah-Hartman <gregkh@linuxfoundation.org>
> >> Cc: Scott Wood <oss@buserror.net>; linuxppc-dev@lists.ozlabs.org;
> >> LKML <linux-kernel@vger.kernel.org>;
> >> linux-arm-kernel@lists.infradead.org
> >> Subject: Re: [Regression 5.6-rc1][Bisected b6231ea2b3c6] Powerpc 8xx
> >> doesn't boot anymore
> >>
> >> ---
> >> diff --git a/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> >> b/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> >> index 4cabded8390b..341d682ec6eb 100644
> >> --- a/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> >> +++ b/drivers/tty/serial/cpm_uart/cpm_uart_core.c
> >> @@ -1351,6 +1351,7 @@ static int __init cpm_uart_console_setup(struct
> >> console *co, char *options)
> >> clrbits32(&pinfo->sccp->scc_gsmrl, SCC_GSMRL_ENR |
> >> SCC_GSMRL_ENT);
> >> }
> >>
> >> + cpm_muram_init();
> >> ret = cpm_uart_allocbuf(pinfo, 1);
> >>
> >> if (ret)
> >>
> > How about the patch like below? Just a draft.
>
> Yes, I see the idea. I think we could go for something like that.
> But in the powerpc 8xx case, we are talking about cpm_init(), not qe_init().
Yes, cpm_init.
Best Regards
Qiang Zhao
^ permalink raw reply
* Re: [PATCH v2] powerpc: setup_64: set up PACA earlier to avoid kcov problems
From: Christophe Leroy @ 2020-02-13 6:23 UTC (permalink / raw)
To: Daniel Axtens, linuxppc-dev; +Cc: ajd
In-Reply-To: <20200213052327.24207-1-dja@axtens.net>
Le 13/02/2020 à 06:23, Daniel Axtens a écrit :
> diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c
> index e05e6dd67ae6..ef455da7efa3 100644
> --- a/arch/powerpc/kernel/setup_64.c
> +++ b/arch/powerpc/kernel/setup_64.c
> @@ -285,18 +285,25 @@ void __init early_setup(unsigned long dt_ptr)
>
> /* -------- printk is _NOT_ safe to use here ! ------- */
>
> - /* Try new device tree based feature discovery ... */
> - if (!dt_cpu_ftrs_init(__va(dt_ptr)))
> - /* Otherwise use the old style CPU table */
> - identify_cpu(0, mfspr(SPRN_PVR));
> + /* Assume we're on cpu 0 for now. Don't write to the paca yet!
> + *
> + * We need to load a PACA very early if we are using kcov. kcov will
> + * call in_task() in its instrumentation, which relies on the current
> + * task from the PACA. dt_cpu_ftrs_init is coveraged-enabled and also
> + * calls into the coverage-enabled generic dt library.
> + */
Checkpatch won't be happy I guess. For multiline comments, there should
be no text on the first line starting with /*
Christophe
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox