* xfs: system fails to boot up due to Internal error xfs_trans_cancel
@ 2023-02-17 11:15 shrikanth hegde
2023-02-17 11:25 ` shrikanth hegde
` (3 more replies)
0 siblings, 4 replies; 28+ messages in thread
From: shrikanth hegde @ 2023-02-17 11:15 UTC (permalink / raw)
To: djwong, dchinner; +Cc: linux-xfs, Srikar Dronamraju, ojaswin, shrikanth hegde
We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in
one of our systems. System fails to come up. System was booting well
with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel.
Panic Log is below.
[ 333.390539] ------------[ cut here ]------------
[ 333.390552] WARNING: CPU: 56 PID: 12450 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
[ 333.390615] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
[ 333.390645] CPU: 56 PID: 12450 Comm: rm Not tainted 6.2.0-rc4ssh+ #4
[ 333.390649] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
[ 333.390652] NIP: c0080000004bfa80 LR: c0080000004bfa4c CTR: c000000000ea28d0
[ 333.390655] REGS: c0000000442bb8c0 TRAP: 0700 Not tainted (6.2.0-rc4ssh+)
[ 333.390658] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24002842 XER: 00000000
[ 333.390666] CFAR: c0080000004bfa54 IRQMASK: 0
[ 333.390666] GPR00: c00000003b69c0c8 c0000000442bbb60 c008000000568300 0000000000000000
[ 333.390666] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000004b27d78
[ 333.390666] GPR08: 0000000000000000 c000000004b27e28 0000000000000000 fffffffffffffffd
[ 333.390666] GPR12: 0000000000000040 c000004afecc5880 0000000106620918 0000000000000001
[ 333.390666] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
[ 333.390666] GPR20: 0000000106620e30 c0000000880ba938 0000000000200000 00000000002ec44d
[ 333.390666] GPR24: 000000000008170d 000000000000000d c0000000519f4800 00000000002ec44d
[ 333.390666] GPR28: c0000000880ba800 c00000003b69c000 c0000000833edd20 000000000008170d
[ 333.390702] NIP [c0080000004bfa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
[ 333.390756] LR [c0080000004bfa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
[ 333.390810] Call Trace:
[ 333.390811] [c0000000442bbb60] [c0000000833edd20] 0xc0000000833edd20 (unreliable)
[ 333.390816] [c0000000442bbb80] [c0080000004c0094] xfs_iunlink+0x1bc/0x280 [xfs]
[ 333.390869] [c0000000442bbc00] [c0080000004c3f84] xfs_remove+0x1dc/0x310 [xfs]
[ 333.390922] [c0000000442bbc70] [c0080000004be180] xfs_vn_unlink+0x68/0xf0 [xfs]
[ 333.390975] [c0000000442bbcd0] [c000000000576b24] vfs_unlink+0x1b4/0x3d0
[ 333.390981] [c0000000442bbd20] [c00000000057e5d8] do_unlinkat+0x2b8/0x390
[ 333.390985] [c0000000442bbde0] [c00000000057e708] sys_unlinkat+0x58/0xb0
[ 333.390989] [c0000000442bbe10] [c0000000000335d0] system_call_exception+0x150/0x3b0
[ 333.390994] [c0000000442bbe50] [c00000000000c554] system_call_common+0xf4/0x258
[ 333.390999] --- interrupt: c00 at 0x7fffa47230a0
[ 333.391001] NIP: 00007fffa47230a0 LR: 00000001066138ac CTR: 0000000000000000
[ 333.391004] REGS: c0000000442bbe80 TRAP: 0c00 Not tainted (6.2.0-rc4ssh+)
[ 333.391007] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 22002202 XER: 00000000
[ 333.391016] IRQMASK: 0
[ 333.391016] GPR00: 0000000000000124 00007fffdb9330b0 00007fffa4807300 0000000000000008
[ 333.391016] GPR04: 000000010bd36f18 0000000000000000 0000000000000000 0000000000000003
[ 333.391016] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 333.391016] GPR12: 0000000000000000 00007fffa48ba340 0000000106620918 0000000000000001
[ 333.391016] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
[ 333.391016] GPR20: 0000000106620e30 0000000106620e00 0000000106620c40 0000000000000002
[ 333.391016] GPR24: 0000000106620c38 00000001066208d8 0000000000000000 0000000106620d20
[ 333.391016] GPR28: 00007fffdb933408 000000010bd24cec 00007fffdb933408 000000010bd36e10
[ 333.391050] NIP [00007fffa47230a0] 0x7fffa47230a0
[ 333.391052] LR [00000001066138ac] 0x1066138ac
[ 333.391054] --- interrupt: c00
[ 333.391056] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
[ 333.391069] ---[ end trace 0000000000000000 ]---
[ 333.391072] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_remove+0x1a0/0x310 [xfs]
[ 333.391128] CPU: 56 PID: 12450 Comm: rm Tainted: G W 6.2.0-rc4ssh+ #4
[ 333.391131] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
[ 333.391135] Call Trace:
[ 333.391136] [c0000000442bbb10] [c000000000e84f4c] dump_stack_lvl+0x70/0xa4 (unreliable)
[ 333.391142] [c0000000442bbb50] [c0080000004a6a84] xfs_error_report+0x5c/0x80 [xfs]
[ 333.391194] [c0000000442bbbb0] [c0080000004d67b0] xfs_trans_cancel+0x178/0x1b0 [xfs]
[ 333.391249] [c0000000442bbc00] [c0080000004c3f48] xfs_remove+0x1a0/0x310 [xfs]
[ 333.391302] [c0000000442bbc70] [c0080000004be180] xfs_vn_unlink+0x68/0xf0 [xfs]
[ 333.391355] [c0000000442bbcd0] [c000000000576b24] vfs_unlink+0x1b4/0x3d0
[ 333.391359] [c0000000442bbd20] [c00000000057e5d8] do_unlinkat+0x2b8/0x390
[ 333.391363] [c0000000442bbde0] [c00000000057e708] sys_unlinkat+0x58/0xb0
[ 333.391367] [c0000000442bbe10] [c0000000000335d0] system_call_exception+0x150/0x3b0
[ 333.391371] [c0000000442bbe50] [c00000000000c554] system_call_common+0xf4/0x258
[ 333.391376] --- interrupt: c00 at 0x7fffa47230a0
[ 333.391378] NIP: 00007fffa47230a0 LR: 00000001066138ac CTR: 0000000000000000
[ 333.391381] REGS: c0000000442bbe80 TRAP: 0c00 Tainted: G W (6.2.0-rc4ssh+)
[ 333.391385] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 22002202 XER: 00000000
[ 333.391393] IRQMASK: 0
[ 333.391393] GPR00: 0000000000000124 00007fffdb9330b0 00007fffa4807300 0000000000000008
[ 333.391393] GPR04: 000000010bd36f18 0000000000000000 0000000000000000 0000000000000003
[ 333.391393] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 333.391393] GPR12: 0000000000000000 00007fffa48ba340 0000000106620918 0000000000000001
[ 333.391393] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
[ 333.391393] GPR20: 0000000106620e30 0000000106620e00 0000000106620c40 0000000000000002
[ 333.391393] GPR24: 0000000106620c38 00000001066208d8 0000000000000000 0000000106620d20
[ 333.391393] GPR28: 00007fffdb933408 000000010bd24cec 00007fffdb933408 000000010bd36e10
[ 333.391427] NIP [00007fffa47230a0] 0x7fffa47230a0
[ 333.391429] LR [00000001066138ac] 0x1066138ac
[ 333.391431] --- interrupt: c00
[ 333.394067] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
[ 333.394125] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
as the bad commit.
Short description of commit:
commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad)
Author: Dave Chinner <dchinner@redhat.com>
Date: Thu Jul 14 11:42:39 2022 +1000
xfs: refactor xlog_recover_process_iunlinks()
Git bisect log:
git bisect start
# good: [26291c54e111ff6ba87a164d85d4a4e134b7315c] Linux 5.17-rc2
git bisect good 26291c54e111ff6ba87a164d85d4a4e134b7315c
# bad: [4fe89d07dcc2804c8b562f6c7896a45643d34b2f] Linux 6.0
git bisect bad 4fe89d07dcc2804c8b562f6c7896a45643d34b2f
# good: [d7227785e384d4422b3ca189aa5bf19f462337cc] Merge tag 'sound-5.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
git bisect good d7227785e384d4422b3ca189aa5bf19f462337cc
# good: [526942b8134cc34d25d27f95dfff98b8ce2f6fcd] Merge tag 'ata-5.20-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
git bisect good 526942b8134cc34d25d27f95dfff98b8ce2f6fcd
# good: [328141e51e6fc79d21168bfd4e356dddc2ec7491] Merge tag 'mmc-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
git bisect good 328141e51e6fc79d21168bfd4e356dddc2ec7491
# bad: [eb555cb5b794f4e12a9897f3d46d5a72104cd4a7] Merge tag '5.20-rc-ksmbd-server-fixes' of git://git.samba.org/ksmbd
git bisect bad eb555cb5b794f4e12a9897f3d46d5a72104cd4a7
# bad: [f20c95b46b8fa3ad34b3ea2e134337f88591468b] Merge tag 'tpmdd-next-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd
git bisect bad f20c95b46b8fa3ad34b3ea2e134337f88591468b
# bad: [fad235ed4338749a66ddf32971d4042b9ef47f44] Merge tag 'arm-late-6.0' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
git bisect bad fad235ed4338749a66ddf32971d4042b9ef47f44
# good: [e495274793ea602415d050452088a496abcd9e6c] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
git bisect good e495274793ea602415d050452088a496abcd9e6c
# good: [9daee913dc8d15eb65e0ff560803ab1c28bb480b] Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
git bisect good 9daee913dc8d15eb65e0ff560803ab1c28bb480b
# bad: [29b1d469f3f6842ee4115f0b21f018fc44176468] Merge tag 'trace-rtla-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
git bisect bad 29b1d469f3f6842ee4115f0b21f018fc44176468
# good: [932b42c66cb5d0ca9800b128415b4ad6b1952b3e] xfs: replace XFS_IFORK_Q with a proper predicate function
git bisect good 932b42c66cb5d0ca9800b128415b4ad6b1952b3e
# bad: [35c5a09f5346e690df7ff2c9075853e340ee10b3] Merge tag 'xfs-buf-lockless-lookup-5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs into xfs-5.20-mergeB
git bisect bad 35c5a09f5346e690df7ff2c9075853e340ee10b3
# bad: [fad743d7cd8bd92d03c09e71f29eace860f50415] xfs: add log item precommit operation
git bisect bad fad743d7cd8bd92d03c09e71f29eace860f50415
# bad: [04755d2e5821b3afbaadd09fe5df58d04de36484] xfs: refactor xlog_recover_process_iunlinks()
git bisect bad 04755d2e5821b3afbaadd09fe5df58d04de36484
# good: [a4454cd69c66bf3e3bbda352b049732f836fc6b2] xfs: factor the xfs_iunlink functions
git bisect good a4454cd69c66bf3e3bbda352b049732f836fc6b2
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[4fcc94d653270fcc7800dbaf3b11f78cb462b293] xfs: track the iunlink list pointer in the xfs_inode
Please reach out, in case any more details are needed. sent with very limited
knowledge of xfs system. these logs are from 5.19 kernel.
# xfs_info /home
meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=13107200 blks
= sectsz=4096 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1 bigtime=0 inobtcount=0
data = bsize=4096 blocks=52428800, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=25600, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
# xfs_info -V
xfs_info version 5.0.0
# uname -a
5.19.0-rc2
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-02-17 11:15 xfs: system fails to boot up due to Internal error xfs_trans_cancel shrikanth hegde
@ 2023-02-17 11:25 ` shrikanth hegde
2023-02-17 11:30 ` shrikanth hegde
` (2 subsequent siblings)
3 siblings, 0 replies; 28+ messages in thread
From: shrikanth hegde @ 2023-02-17 11:25 UTC (permalink / raw)
To: djwong, dchinner; +Cc: linux-xfs, Srikar Dronamraju, ojaswin
On 2/17/23 4:45 PM, shrikanth hegde wrote:
> We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in
> one of our systems. System fails to come up. System was booting well
> with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel.
.config file on 5.19
#
# Automatically generated file; DO NOT EDIT.
# Linux/powerpc 5.19.0-rc2 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10)"
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=80500
CONFIG_CLANG_VERSION=0
CONFIG_AS_IS_GNU=y
CONFIG_AS_VERSION=23000
CONFIG_LD_IS_BFD=y
CONFIG_LD_VERSION=23000
CONFIG_LLD_VERSION=0
CONFIG_CC_CAN_LINK=y
CONFIG_CC_HAS_ASM_GOTO=y
CONFIG_CC_HAS_ASM_INLINE=y
CONFIG_CC_HAS_NO_PROFILE_FN_ATTR=y
CONFIG_PAHOLE_VERSION=122
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_TABLE_SORT=y
CONFIG_THREAD_INFO_IN_TASK=y
#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not set
# CONFIG_WERROR is not set
CONFIG_LOCALVERSION="ssh"
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_BUILD_SALT=""
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_XZ is not set
CONFIG_DEFAULT_INIT=""
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
# CONFIG_WATCH_QUEUE is not set
CONFIG_CROSS_MEMORY_ATTACH=y
# CONFIG_USELIB is not set
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_SHOW_LEVEL=y
CONFIG_GENERIC_IRQ_MIGRATION=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_GENERIC_MSI_IRQ_DOMAIN=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
# CONFIG_GENERIC_IRQ_DEBUGFS is not set
# end of IRQ subsystem
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_ARCH_HAS_TICK_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CMOS_UPDATE=y
#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
# CONFIG_NO_HZ_IDLE is not set
CONFIG_NO_HZ_FULL=y
CONFIG_CONTEXT_TRACKING=y
# CONFIG_CONTEXT_TRACKING_FORCE is not set
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
# end of Timers subsystem
CONFIG_BPF=y
CONFIG_HAVE_EBPF_JIT=y
#
# BPF subsystem
#
CONFIG_BPF_SYSCALL=y
CONFIG_BPF_JIT=y
CONFIG_BPF_JIT_ALWAYS_ON=y
CONFIG_BPF_JIT_DEFAULT_ON=y
CONFIG_BPF_UNPRIV_DEFAULT_OFF=y
# CONFIG_BPF_PRELOAD is not set
CONFIG_BPF_LSM=y
# end of BPF subsystem
CONFIG_PREEMPT_VOLUNTARY_BUILD=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
# CONFIG_SCHED_CORE is not set
#
# CPU/Task time and stats accounting
#
CONFIG_VIRT_CPU_ACCOUNTING=y
CONFIG_VIRT_CPU_ACCOUNTING_GEN=y
# CONFIG_IRQ_TIME_ACCOUNTING is not set
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_PSI=y
CONFIG_PSI_DEFAULT_DISABLED=y
# end of CPU/Task time and stats accounting
CONFIG_CPU_ISOLATION=y
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
CONFIG_TREE_SRCU=y
CONFIG_TASKS_RCU_GENERIC=y
CONFIG_TASKS_RUDE_RCU=y
CONFIG_TASKS_TRACE_RCU=y
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_NEED_SEGCBLIST=y
CONFIG_RCU_NOCB_CPU=y
# end of RCU Subsystem
CONFIG_BUILD_BIN2C=y
CONFIG_IKCONFIG=m
# CONFIG_IKCONFIG_PROC is not set
# CONFIG_IKHEADERS is not set
CONFIG_LOG_BUF_SHIFT=20
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
# CONFIG_PRINTK_INDEX is not set
#
# Scheduler features
#
# CONFIG_UCLAMP_TASK is not set
# end of Scheduler features
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_CC_HAS_INT128=y
CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5"
CONFIG_GCC12_NO_ARRAY_BOUNDS=y
CONFIG_NUMA_BALANCING=y
CONFIG_NUMA_BALANCING_DEFAULT_ENABLED=y
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
CONFIG_MEMCG_KMEM=y
CONFIG_BLK_CGROUP=y
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_CFS_BANDWIDTH=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_CGROUP_PIDS=y
CONFIG_CGROUP_RDMA=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_HUGETLB=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
CONFIG_CGROUP_BPF=y
# CONFIG_CGROUP_MISC is not set
# CONFIG_CGROUP_DEBUG is not set
CONFIG_SOCK_CGROUP_DATA=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_TIME_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_CHECKPOINT_RESTORE=y
CONFIG_SCHED_AUTOGROUP=y
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_RD_LZ4=y
CONFIG_RD_ZSTD=y
# CONFIG_BOOT_CONFIG is not set
CONFIG_INITRAMFS_PRESERVE_MTIME=y
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_HAVE_LD_DEAD_CODE_DATA_ELIMINATION=y
CONFIG_LD_ORPHAN_WARN=y
CONFIG_SYSCTL=y
CONFIG_SYSCTL_EXCEPTION_TRACE=y
CONFIG_HAVE_PCSPKR_PLATFORM=y
# CONFIG_EXPERT is not set
CONFIG_MULTIUSER=y
CONFIG_SGETMASK_SYSCALL=y
CONFIG_SYSFS_SYSCALL=y
CONFIG_FHANDLE=y
CONFIG_POSIX_TIMERS=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_FUTEX_PI=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_IO_URING=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_MEMBARRIER=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_BASE_RELATIVE=y
CONFIG_ARCH_HAS_MEMBARRIER_CALLBACKS=y
CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y
CONFIG_KCMP=y
CONFIG_RSEQ=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# end of Kernel Performance Events And Counters
CONFIG_SYSTEM_DATA_VERIFICATION=y
CONFIG_PROFILING=y
CONFIG_TRACEPOINTS=y
# end of General setup
CONFIG_PPC64=y
#
# Processor support
#
CONFIG_PPC_BOOK3S_64=y
# CONFIG_PPC_BOOK3E_64 is not set
CONFIG_GENERIC_CPU=y
# CONFIG_POWER7_CPU is not set
# CONFIG_POWER8_CPU is not set
# CONFIG_POWER9_CPU is not set
CONFIG_PPC_BOOK3S=y
CONFIG_PPC_FPU_REGS=y
CONFIG_PPC_FPU=y
CONFIG_ALTIVEC=y
CONFIG_VSX=y
CONFIG_PPC_64S_HASH_MMU=y
CONFIG_PPC_RADIX_MMU=y
CONFIG_PPC_RADIX_MMU_DEFAULT=y
CONFIG_PPC_KUEP=y
CONFIG_PPC_KUAP=y
# CONFIG_PPC_KUAP_DEBUG is not set
CONFIG_PPC_PKEY=y
CONFIG_PPC_HAVE_PMU_SUPPORT=y
CONFIG_PMU_SYSFS=y
CONFIG_PPC_PERF_CTRS=y
CONFIG_FORCE_SMP=y
CONFIG_SMP=y
CONFIG_NR_CPUS=2048
CONFIG_PPC_DOORBELL=y
# end of Processor support
CONFIG_VDSO32=y
# CONFIG_CPU_BIG_ENDIAN is not set
CONFIG_CPU_LITTLE_ENDIAN=y
CONFIG_PPC64_ELF_ABI_V2=y
CONFIG_PPC64_BOOT_WRAPPER=y
CONFIG_64BIT=y
CONFIG_LIVEPATCH_64=y
CONFIG_MMU=y
CONFIG_ARCH_MMAP_RND_BITS_MAX=29
CONFIG_ARCH_MMAP_RND_BITS_MIN=14
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=13
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=7
CONFIG_NR_IRQS=512
CONFIG_NMI_IPI=y
CONFIG_PPC_WATCHDOG=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_PPC=y
CONFIG_PPC_BARRIER_NOSPEC=y
CONFIG_EARLY_PRINTK=y
CONFIG_PANIC_TIMEOUT=180
CONFIG_COMPAT=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_PPC_UDBG_16550=y
CONFIG_AUDIT_ARCH=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_EPAPR_BOOT=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_SUSPEND_NONZERO_CPU=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_PPC_DAWR=y
CONFIG_PGTABLE_LEVELS=4
CONFIG_PPC_MSI_BITMAP=y
CONFIG_PPC_XICS=y
CONFIG_PPC_ICP_NATIVE=y
CONFIG_PPC_ICP_HV=y
CONFIG_PPC_ICS_RTAS=y
CONFIG_PPC_XIVE=y
CONFIG_PPC_XIVE_NATIVE=y
CONFIG_PPC_XIVE_SPAPR=y
#
# Platform support
#
CONFIG_PPC_POWERNV=y
# CONFIG_OPAL_PRD is not set
# CONFIG_PPC_MEMTRACE is not set
CONFIG_SCOM_DEBUGFS=y
CONFIG_PPC_PSERIES=y
CONFIG_PARAVIRT_SPINLOCKS=y
CONFIG_PPC_SPLPAR=y
CONFIG_DTL=y
# CONFIG_PSERIES_ENERGY is not set
CONFIG_IO_EVENT_IRQ=y
CONFIG_LPARCFG=y
CONFIG_PPC_SMLPAR=y
CONFIG_CMM=y
CONFIG_HV_PERF_CTRS=y
CONFIG_IBMVIO=y
CONFIG_PPC_SVM=y
CONFIG_PPC_VAS=y
CONFIG_KVM_GUEST=y
CONFIG_EPAPR_PARAVIRT=y
CONFIG_PPC_HASH_MMU_NATIVE=y
CONFIG_PPC_OF_BOOT_TRAMPOLINE=y
CONFIG_PPC_DT_CPU_FTRS=y
# CONFIG_UDBG_RTAS_CONSOLE is not set
CONFIG_PPC_SMP_MUXED_IPI=y
CONFIG_MPIC=y
# CONFIG_MPIC_MSGR is not set
CONFIG_PPC_I8259=y
CONFIG_PPC_RTAS=y
CONFIG_RTAS_ERROR_LOGGING=y
CONFIG_PPC_RTAS_DAEMON=y
CONFIG_RTAS_PROC=y
CONFIG_RTAS_FLASH=y
CONFIG_EEH=y
CONFIG_PPC_P7_NAP=y
CONFIG_PPC_BOOK3S_IDLE=y
CONFIG_PPC_INDIRECT_PIO=y
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_GOV_ATTR_SET=y
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
#
# CPU frequency scaling drivers
#
CONFIG_POWERNV_CPUFREQ=y
# end of CPU Frequency scaling
#
# CPUIdle driver
#
#
# CPU Idle
#
CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_GOV_LADDER is not set
CONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_CPU_IDLE_GOV_TEO is not set
CONFIG_CPU_IDLE_GOV_HALTPOLL=y
#
# POWERPC CPU Idle Drivers
#
CONFIG_PSERIES_CPUIDLE=y
CONFIG_POWERNV_CPUIDLE=y
# end of POWERPC CPU Idle Drivers
# end of CPU Idle
# end of CPUIdle driver
# CONFIG_GEN_RTC is not set
# end of Platform support
#
# Kernel options
#
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
CONFIG_SCHED_HRTICK=y
CONFIG_PPC_TRANSACTIONAL_MEM=y
CONFIG_MPROFILE_KERNEL=y
CONFIG_HOTPLUG_CPU=y
CONFIG_PPC_QUEUED_SPINLOCKS=y
CONFIG_ARCH_CPU_PROBE_RELEASE=y
CONFIG_PPC64_SUPPORTS_MEMORY_FAILURE=y
CONFIG_KEXEC=y
CONFIG_KEXEC_FILE=y
CONFIG_ARCH_HAS_KEXEC_PURGATORY=y
CONFIG_RELOCATABLE=y
# CONFIG_RELOCATABLE_TEST is not set
CONFIG_CRASH_DUMP=y
CONFIG_FA_DUMP=y
CONFIG_OPAL_CORE=y
CONFIG_IRQ_ALL_CPUS=y
CONFIG_NUMA=y
CONFIG_NODES_SHIFT=8
CONFIG_HAVE_MEMORYLESS_NODES=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ILLEGAL_POINTER_VALUE=0x5deadbeef0000000
CONFIG_ARCH_MEMORY_PROBE=y
# CONFIG_PPC_4K_PAGES is not set
CONFIG_PPC_64K_PAGES=y
CONFIG_PAGE_SIZE_64KB=y
CONFIG_PPC_PAGE_SHIFT=16
CONFIG_THREAD_SHIFT=14
CONFIG_DATA_SHIFT=24
CONFIG_FORCE_MAX_ZONEORDER=9
CONFIG_PPC_SUBPAGE_PROT=y
# CONFIG_PPC_PROT_SAO_LPAR is not set
CONFIG_SCHED_SMT=y
CONFIG_PPC_DENORMALISATION=y
CONFIG_CMDLINE=""
CONFIG_EXTRA_TARGETS=""
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_HIBERNATION is not set
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP_SMP_NONZERO_CPU=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
CONFIG_PM=y
CONFIG_PM_DEBUG=y
# CONFIG_PM_ADVANCED_DEBUG is not set
# CONFIG_PM_TEST_SUSPEND is not set
CONFIG_PM_SLEEP_DEBUG=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
CONFIG_ENERGY_MODEL=y
CONFIG_PPC_MEM_KEYS=y
CONFIG_PPC_SECURE_BOOT=y
CONFIG_PPC_SECVAR_SYSFS=y
CONFIG_PPC_RTAS_FILTER=y
# end of Kernel options
CONFIG_ISA_DMA_API=y
#
# Bus options
#
CONFIG_GENERIC_ISA_DMA=y
# CONFIG_FSL_LBC is not set
# end of Bus options
CONFIG_NONSTATIC_KERNEL=y
CONFIG_PAGE_OFFSET=0xc000000000000000
CONFIG_KERNEL_START=0xc000000000000000
CONFIG_PHYSICAL_START=0x00000000
CONFIG_ARCH_RANDOM=y
CONFIG_VIRTUALIZATION=y
# CONFIG_KVM_BOOK3S_64 is not set
CONFIG_HAVE_LIVEPATCH=y
CONFIG_LIVEPATCH=y
#
# General architecture-dependent options
#
CONFIG_CRASH_CORE=y
CONFIG_KEXEC_CORE=y
CONFIG_KEXEC_ELF=y
CONFIG_HAVE_IMA_KEXEC=y
CONFIG_KPROBES=y
CONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not set
CONFIG_OPTPROBES=y
CONFIG_KPROBES_ON_FTRACE=y
CONFIG_UPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_ARCH_USE_BUILTIN_BSWAP=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_KPROBES_ON_FTRACE=y
CONFIG_HAVE_FUNCTION_ERROR_INJECTION=y
CONFIG_HAVE_NMI=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_ARCH_HAS_FORTIFY_SOURCE=y
CONFIG_ARCH_HAS_SET_MEMORY=y
CONFIG_ARCH_WANTS_NO_INSTR=y
CONFIG_HAVE_ASM_MODVERSIONS=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_RSEQ=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_NMI_WATCHDOG=y
CONFIG_HAVE_HARDLOCKUP_DETECTOR_ARCH=y
CONFIG_HAVE_PERF_REGS=y
CONFIG_HAVE_PERF_USER_STACK_DUMP=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_HAVE_ARCH_JUMP_LABEL_RELATIVE=y
CONFIG_MMU_GATHER_TABLE_FREE=y
CONFIG_MMU_GATHER_RCU_TABLE_FREE=y
CONFIG_MMU_GATHER_PAGE_SIZE=y
CONFIG_ARCH_WANT_IRQS_OFF_ACTIVATE_MM=y
CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
CONFIG_ARCH_WEAK_RELEASE_ACQUIRE=y
CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y
CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y
CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y
CONFIG_HAVE_ARCH_SECCOMP=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP=y
CONFIG_SECCOMP_FILTER=y
# CONFIG_SECCOMP_CACHE_DEBUG is not set
CONFIG_HAVE_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR_STRONG=y
CONFIG_LTO_NONE=y
CONFIG_HAVE_CONTEXT_TRACKING=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_MOVE_PUD=y
CONFIG_HAVE_MOVE_PMD=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
CONFIG_HAVE_ARCH_HUGE_VMAP=y
CONFIG_HAVE_ARCH_HUGE_VMALLOC=y
CONFIG_HAVE_ARCH_SOFT_DIRTY=y
CONFIG_HAVE_MOD_ARCH_SPECIFIC=y
CONFIG_MODULES_USE_ELF_RELA=y
CONFIG_HAVE_SOFTIRQ_ON_OWN_STACK=y
CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
CONFIG_HAVE_ARCH_MMAP_RND_BITS=y
CONFIG_ARCH_MMAP_RND_BITS=14
CONFIG_HAVE_ARCH_MMAP_RND_COMPAT_BITS=y
CONFIG_ARCH_MMAP_RND_COMPAT_BITS=7
CONFIG_PAGE_SIZE_LESS_THAN_256KB=y
CONFIG_ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT=y
CONFIG_HAVE_RELIABLE_STACKTRACE=y
CONFIG_HAVE_ARCH_NVRAM_OPS=y
CONFIG_CLONE_BACKWARDS=y
CONFIG_OLD_SIGSUSPEND=y
CONFIG_COMPAT_OLD_SIGACTION=y
CONFIG_COMPAT_32BIT_TIME=y
CONFIG_ARCH_OPTIONAL_KERNEL_RWX=y
CONFIG_ARCH_OPTIONAL_KERNEL_RWX_DEFAULT=y
CONFIG_ARCH_HAS_STRICT_KERNEL_RWX=y
CONFIG_STRICT_KERNEL_RWX=y
CONFIG_ARCH_HAS_STRICT_MODULE_RWX=y
CONFIG_STRICT_MODULE_RWX=y
CONFIG_ARCH_HAS_PHYS_TO_DMA=y
# CONFIG_LOCK_EVENT_COUNTS is not set
CONFIG_ARCH_HAS_MEM_ENCRYPT=y
CONFIG_ARCH_HAS_CC_PLATFORM=y
CONFIG_ARCH_WANT_LD_ORPHAN_WARN=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# end of GCOV-based kernel profiling
CONFIG_HAVE_GCC_PLUGINS=y
# end of General architecture-dependent options
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULE_SIG_FORMAT=y
CONFIG_MODULES=y
CONFIG_MODULE_FORCE_LOAD=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODULE_UNLOAD_TAINT_TRACKING is not set
CONFIG_MODVERSIONS=y
CONFIG_ASM_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set
CONFIG_MODULE_SIG_ALL=y
# CONFIG_MODULE_SIG_SHA1 is not set
# CONFIG_MODULE_SIG_SHA224 is not set
CONFIG_MODULE_SIG_SHA256=y
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not set
CONFIG_MODULE_SIG_HASH="sha256"
CONFIG_MODULE_COMPRESS_NONE=y
# CONFIG_MODULE_COMPRESS_GZIP is not set
# CONFIG_MODULE_COMPRESS_XZ is not set
# CONFIG_MODULE_COMPRESS_ZSTD is not set
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set
CONFIG_MODPROBE_PATH="/sbin/modprobe"
CONFIG_MODULES_TREE_LOOKUP=y
CONFIG_BLOCK=y
CONFIG_BLOCK_LEGACY_AUTOLOAD=y
CONFIG_BLK_CGROUP_RWSTAT=y
CONFIG_BLK_DEV_BSG_COMMON=y
CONFIG_BLK_ICQ=y
CONFIG_BLK_DEV_BSGLIB=y
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLK_DEV_INTEGRITY_T10=m
# CONFIG_BLK_DEV_ZONED is not set
CONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_DEV_THROTTLING_LOW is not set
CONFIG_BLK_WBT=y
CONFIG_BLK_WBT_MQ=y
CONFIG_BLK_CGROUP_IOLATENCY=y
# CONFIG_BLK_CGROUP_IOCOST is not set
# CONFIG_BLK_CGROUP_IOPRIO is not set
CONFIG_BLK_DEBUG_FS=y
# CONFIG_BLK_SED_OPAL is not set
# CONFIG_BLK_INLINE_ENCRYPTION is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_AIX_PARTITION is not set
CONFIG_OSF_PARTITION=y
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
# CONFIG_CMDLINE_PARTITION is not set
# end of Partition Types
CONFIG_BLOCK_COMPAT=y
CONFIG_BLK_MQ_PCI=y
CONFIG_BLK_MQ_VIRTIO=y
CONFIG_BLK_PM=y
CONFIG_BLOCK_HOLDER_DEPRECATED=y
CONFIG_BLK_MQ_STACKING=y
#
# IO Schedulers
#
CONFIG_MQ_IOSCHED_DEADLINE=y
CONFIG_MQ_IOSCHED_KYBER=y
CONFIG_IOSCHED_BFQ=y
CONFIG_BFQ_GROUP_IOSCHED=y
# CONFIG_BFQ_CGROUP_DEBUG is not set
# end of IO Schedulers
CONFIG_ASN1=y
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
CONFIG_INLINE_READ_UNLOCK=y
CONFIG_INLINE_READ_UNLOCK_IRQ=y
CONFIG_INLINE_WRITE_UNLOCK=y
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_RWSEM_SPIN_ON_OWNER=y
CONFIG_LOCK_SPIN_ON_OWNER=y
CONFIG_ARCH_USE_QUEUED_SPINLOCKS=y
CONFIG_QUEUED_SPINLOCKS=y
CONFIG_ARCH_USE_QUEUED_RWLOCKS=y
CONFIG_QUEUED_RWLOCKS=y
CONFIG_ARCH_HAS_MMIOWB=y
CONFIG_MMIOWB=y
CONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE=y
CONFIG_FREEZER=y
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_ELFCORE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_BINFMT_SCRIPT=y
# CONFIG_BINFMT_MISC is not set
CONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#
CONFIG_ZPOOL=y
CONFIG_SWAP=y
CONFIG_ZSWAP=y
# CONFIG_ZSWAP_DEFAULT_ON is not set
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_DEFLATE is not set
CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZO=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_842 is not set
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4 is not set
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4HC is not set
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_ZSTD is not set
CONFIG_ZSWAP_COMPRESSOR_DEFAULT="lzo"
CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD=y
# CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD is not set
# CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC is not set
CONFIG_ZSWAP_ZPOOL_DEFAULT="zbud"
CONFIG_ZBUD=y
# CONFIG_Z3FOLD is not set
CONFIG_ZSMALLOC=y
CONFIG_ZSMALLOC_STAT=y
#
# SLAB allocator options
#
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLAB_MERGE_DEFAULT is not set
CONFIG_SLAB_FREELIST_RANDOM=y
CONFIG_SLAB_FREELIST_HARDENED=y
# CONFIG_SLUB_STATS is not set
CONFIG_SLUB_CPU_PARTIAL=y
# end of SLAB allocator options
CONFIG_SHUFFLE_PAGE_ALLOCATOR=y
# CONFIG_COMPAT_BRK is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_HAVE_FAST_GUP=y
CONFIG_ARCH_KEEP_MEMBLOCK=y
CONFIG_NUMA_KEEP_MEMINFO=y
CONFIG_MEMORY_ISOLATION=y
CONFIG_EXCLUSIVE_SYSTEM_RAM=y
CONFIG_HAVE_BOOTMEM_INFO_NODE=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
CONFIG_MEMORY_HOTPLUG=y
# CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is not set
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y
CONFIG_MEMORY_BALLOON=y
CONFIG_BALLOON_COMPACTION=y
CONFIG_COMPACTION=y
CONFIG_PAGE_REPORTING=y
CONFIG_MIGRATION=y
CONFIG_DEVICE_MIGRATION=y
CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=y
CONFIG_ARCH_ENABLE_THP_MIGRATION=y
CONFIG_HUGETLB_PAGE_SIZE_VARIABLE=y
CONFIG_CONTIG_ALLOC=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_MMU_NOTIFIER=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
CONFIG_MEMORY_FAILURE=y
# CONFIG_HWPOISON_INJECT is not set
CONFIG_TRANSPARENT_HUGEPAGE=y
# CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is not set
CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y
# CONFIG_READ_ONLY_THP_FOR_FS is not set
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_USE_PERCPU_NUMA_NODE_ID=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_FRONTSWAP=y
CONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not set
# CONFIG_CMA_SYSFS is not set
CONFIG_CMA_AREAS=7
CONFIG_MEM_SOFT_DIRTY=y
CONFIG_GENERIC_EARLY_IOREMAP=y
# CONFIG_DEFERRED_STRUCT_PAGE_INIT is not set
CONFIG_PAGE_IDLE_FLAG=y
CONFIG_IDLE_PAGE_TRACKING=y
CONFIG_ARCH_HAS_CURRENT_STACK_POINTER=y
CONFIG_ARCH_HAS_VM_GET_PAGE_PROT=y
CONFIG_ARCH_HAS_PTE_DEVMAP=y
CONFIG_ZONE_DEVICE=y
CONFIG_DEVICE_PRIVATE=y
CONFIG_ARCH_USES_HIGH_VMA_FLAGS=y
CONFIG_ARCH_HAS_PKEYS=y
CONFIG_VM_EVENT_COUNTERS=y
# CONFIG_PERCPU_STATS is not set
# CONFIG_GUP_TEST is not set
CONFIG_ARCH_HAS_PTE_SPECIAL=y
CONFIG_ARCH_HAS_HUGEPD=y
# CONFIG_ANON_VMA_NAME is not set
CONFIG_USERFAULTFD=y
#
# Data Access Monitoring
#
CONFIG_DAMON=y
CONFIG_DAMON_VADDR=y
CONFIG_DAMON_PADDR=y
# CONFIG_DAMON_SYSFS is not set
CONFIG_DAMON_DBGFS=y
CONFIG_DAMON_RECLAIM=y
# end of Data Access Monitoring
# end of Memory Management options
CONFIG_NET=y
CONFIG_NET_INGRESS=y
CONFIG_NET_EGRESS=y
CONFIG_SKB_EXTENSIONS=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_DIAG is not set
CONFIG_UNIX=y
CONFIG_UNIX_SCM=y
CONFIG_AF_UNIX_OOB=y
# CONFIG_UNIX_DIAG is not set
# CONFIG_TLS is not set
CONFIG_XFRM=y
CONFIG_XFRM_ALGO=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_INTERFACE is not set
CONFIG_XFRM_SUB_POLICY=y
CONFIG_XFRM_MIGRATE=y
CONFIG_XFRM_STATISTICS=y
# CONFIG_NET_KEY is not set
CONFIG_XDP_SOCKETS=y
# CONFIG_XDP_SOCKETS_DIAG is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_FIB_TRIE_STATS=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE_DEMUX is not set
CONFIG_IP_MROUTE_COMMON=y
CONFIG_IP_MROUTE=y
CONFIG_IP_MROUTE_MULTIPLE_TABLES=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_SYN_COOKIES=y
# CONFIG_NET_IPVTI is not set
# CONFIG_NET_FOU is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_DIAG is not set
CONFIG_TCP_CONG_ADVANCED=y
# CONFIG_TCP_CONG_BIC is not set
CONFIG_TCP_CONG_CUBIC=y
# CONFIG_TCP_CONG_WESTWOOD is not set
# CONFIG_TCP_CONG_HTCP is not set
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
# CONFIG_TCP_CONG_VEGAS is not set
# CONFIG_TCP_CONG_NV is not set
# CONFIG_TCP_CONG_SCALABLE is not set
# CONFIG_TCP_CONG_LP is not set
# CONFIG_TCP_CONG_VENO is not set
# CONFIG_TCP_CONG_YEAH is not set
# CONFIG_TCP_CONG_ILLINOIS is not set
# CONFIG_TCP_CONG_DCTCP is not set
# CONFIG_TCP_CONG_CDG is not set
# CONFIG_TCP_CONG_BBR is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_IPV6_ILA is not set
# CONFIG_IPV6_VTI is not set
# CONFIG_IPV6_SIT is not set
# CONFIG_IPV6_TUNNEL is not set
CONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not set
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
CONFIG_IPV6_PIMSM_V2=y
# CONFIG_IPV6_SEG6_LWTUNNEL is not set
# CONFIG_IPV6_SEG6_HMAC is not set
# CONFIG_IPV6_RPL_LWTUNNEL is not set
# CONFIG_IPV6_IOAM6_LWTUNNEL is not set
CONFIG_NETLABEL=y
CONFIG_MPTCP=y
CONFIG_MPTCP_IPV6=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NET_PTP_CLASSIFY=y
CONFIG_NETWORK_PHY_TIMESTAMPING=y
CONFIG_NETFILTER=y
CONFIG_NETFILTER_ADVANCED=y
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_INGRESS=y
CONFIG_NETFILTER_EGRESS=y
CONFIG_NETFILTER_SKIP_EGRESS=y
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_FAMILY_ARP=y
# CONFIG_NETFILTER_NETLINK_HOOK is not set
# CONFIG_NETFILTER_NETLINK_ACCT is not set
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
# CONFIG_NETFILTER_NETLINK_LOG is not set
# CONFIG_NETFILTER_NETLINK_OSF is not set
CONFIG_NF_CONNTRACK=m
# CONFIG_NF_LOG_SYSLOG is not set
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_ZONES=y
CONFIG_NF_CONNTRACK_PROCFS=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CONNTRACK_TIMEOUT=y
CONFIG_NF_CONNTRACK_TIMESTAMP=y
CONFIG_NF_CONNTRACK_LABELS=y
CONFIG_NF_CT_PROTO_DCCP=y
CONFIG_NF_CT_PROTO_SCTP=y
CONFIG_NF_CT_PROTO_UDPLITE=y
# CONFIG_NF_CONNTRACK_AMANDA is not set
# CONFIG_NF_CONNTRACK_FTP is not set
# CONFIG_NF_CONNTRACK_H323 is not set
# CONFIG_NF_CONNTRACK_IRC is not set
# CONFIG_NF_CONNTRACK_NETBIOS_NS is not set
# CONFIG_NF_CONNTRACK_SNMP is not set
# CONFIG_NF_CONNTRACK_PPTP is not set
# CONFIG_NF_CONNTRACK_SANE is not set
# CONFIG_NF_CONNTRACK_SIP is not set
# CONFIG_NF_CONNTRACK_TFTP is not set
# CONFIG_NF_CT_NETLINK is not set
# CONFIG_NF_CT_NETLINK_TIMEOUT is not set
CONFIG_NF_NAT=m
CONFIG_NF_TABLES=m
CONFIG_NF_TABLES_INET=y
CONFIG_NF_TABLES_NETDEV=y
# CONFIG_NFT_NUMGEN is not set
CONFIG_NFT_CT=m
# CONFIG_NFT_CONNLIMIT is not set
# CONFIG_NFT_LOG is not set
# CONFIG_NFT_LIMIT is not set
# CONFIG_NFT_MASQ is not set
# CONFIG_NFT_REDIR is not set
CONFIG_NFT_NAT=m
# CONFIG_NFT_TUNNEL is not set
# CONFIG_NFT_OBJREF is not set
# CONFIG_NFT_QUOTA is not set
CONFIG_NFT_REJECT=m
CONFIG_NFT_REJECT_INET=m
# CONFIG_NFT_COMPAT is not set
# CONFIG_NFT_HASH is not set
CONFIG_NFT_FIB=m
CONFIG_NFT_FIB_INET=m
# CONFIG_NFT_XFRM is not set
# CONFIG_NFT_SOCKET is not set
# CONFIG_NFT_OSF is not set
# CONFIG_NFT_TPROXY is not set
# CONFIG_NFT_SYNPROXY is not set
# CONFIG_NF_DUP_NETDEV is not set
# CONFIG_NFT_DUP_NETDEV is not set
# CONFIG_NFT_FWD_NETDEV is not set
# CONFIG_NFT_FIB_NETDEV is not set
# CONFIG_NFT_REJECT_NETDEV is not set
# CONFIG_NF_FLOW_TABLE is not set
CONFIG_NETFILTER_XTABLES=y
CONFIG_NETFILTER_XTABLES_COMPAT=y
#
# Xtables combined modules
#
# CONFIG_NETFILTER_XT_MARK is not set
# CONFIG_NETFILTER_XT_CONNMARK is not set
# CONFIG_NETFILTER_XT_SET is not set
#
# Xtables targets
#
# CONFIG_NETFILTER_XT_TARGET_AUDIT is not set
# CONFIG_NETFILTER_XT_TARGET_CLASSIFY is not set
# CONFIG_NETFILTER_XT_TARGET_CONNMARK is not set
# CONFIG_NETFILTER_XT_TARGET_CONNSECMARK is not set
# CONFIG_NETFILTER_XT_TARGET_HMARK is not set
# CONFIG_NETFILTER_XT_TARGET_IDLETIMER is not set
# CONFIG_NETFILTER_XT_TARGET_LED is not set
# CONFIG_NETFILTER_XT_TARGET_LOG is not set
# CONFIG_NETFILTER_XT_TARGET_MARK is not set
# CONFIG_NETFILTER_XT_NAT is not set
# CONFIG_NETFILTER_XT_TARGET_NETMAP is not set
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
# CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set
# CONFIG_NETFILTER_XT_TARGET_RATEEST is not set
# CONFIG_NETFILTER_XT_TARGET_REDIRECT is not set
# CONFIG_NETFILTER_XT_TARGET_MASQUERADE is not set
# CONFIG_NETFILTER_XT_TARGET_TEE is not set
# CONFIG_NETFILTER_XT_TARGET_SECMARK is not set
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set
#
# Xtables matches
#
# CONFIG_NETFILTER_XT_MATCH_ADDRTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_BPF is not set
# CONFIG_NETFILTER_XT_MATCH_CGROUP is not set
# CONFIG_NETFILTER_XT_MATCH_CLUSTER is not set
# CONFIG_NETFILTER_XT_MATCH_COMMENT is not set
# CONFIG_NETFILTER_XT_MATCH_CONNBYTES is not set
# CONFIG_NETFILTER_XT_MATCH_CONNLABEL is not set
# CONFIG_NETFILTER_XT_MATCH_CONNLIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_CONNMARK is not set
# CONFIG_NETFILTER_XT_MATCH_CONNTRACK is not set
# CONFIG_NETFILTER_XT_MATCH_CPU is not set
# CONFIG_NETFILTER_XT_MATCH_DCCP is not set
# CONFIG_NETFILTER_XT_MATCH_DEVGROUP is not set
# CONFIG_NETFILTER_XT_MATCH_DSCP is not set
# CONFIG_NETFILTER_XT_MATCH_ECN is not set
# CONFIG_NETFILTER_XT_MATCH_ESP is not set
# CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_HELPER is not set
# CONFIG_NETFILTER_XT_MATCH_HL is not set
# CONFIG_NETFILTER_XT_MATCH_IPCOMP is not set
# CONFIG_NETFILTER_XT_MATCH_IPRANGE is not set
# CONFIG_NETFILTER_XT_MATCH_L2TP is not set
# CONFIG_NETFILTER_XT_MATCH_LENGTH is not set
# CONFIG_NETFILTER_XT_MATCH_LIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_MAC is not set
# CONFIG_NETFILTER_XT_MATCH_MARK is not set
# CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set
# CONFIG_NETFILTER_XT_MATCH_NFACCT is not set
# CONFIG_NETFILTER_XT_MATCH_OSF is not set
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
# CONFIG_NETFILTER_XT_MATCH_POLICY is not set
# CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_QUOTA is not set
# CONFIG_NETFILTER_XT_MATCH_RATEEST is not set
# CONFIG_NETFILTER_XT_MATCH_REALM is not set
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
# CONFIG_NETFILTER_XT_MATCH_SCTP is not set
# CONFIG_NETFILTER_XT_MATCH_SOCKET is not set
# CONFIG_NETFILTER_XT_MATCH_STATE is not set
# CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set
# CONFIG_NETFILTER_XT_MATCH_STRING is not set
# CONFIG_NETFILTER_XT_MATCH_TCPMSS is not set
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
# end of Core Netfilter Configuration
CONFIG_IP_SET=m
CONFIG_IP_SET_MAX=256
# CONFIG_IP_SET_BITMAP_IP is not set
# CONFIG_IP_SET_BITMAP_IPMAC is not set
# CONFIG_IP_SET_BITMAP_PORT is not set
# CONFIG_IP_SET_HASH_IP is not set
# CONFIG_IP_SET_HASH_IPMARK is not set
# CONFIG_IP_SET_HASH_IPPORT is not set
# CONFIG_IP_SET_HASH_IPPORTIP is not set
# CONFIG_IP_SET_HASH_IPPORTNET is not set
# CONFIG_IP_SET_HASH_IPMAC is not set
# CONFIG_IP_SET_HASH_MAC is not set
# CONFIG_IP_SET_HASH_NETPORTNET is not set
# CONFIG_IP_SET_HASH_NET is not set
# CONFIG_IP_SET_HASH_NETNET is not set
# CONFIG_IP_SET_HASH_NETPORT is not set
# CONFIG_IP_SET_HASH_NETIFACE is not set
# CONFIG_IP_SET_LIST_SET is not set
# CONFIG_IP_VS is not set
#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
# CONFIG_NF_SOCKET_IPV4 is not set
# CONFIG_NF_TPROXY_IPV4 is not set
CONFIG_NF_TABLES_IPV4=y
CONFIG_NFT_REJECT_IPV4=m
# CONFIG_NFT_DUP_IPV4 is not set
CONFIG_NFT_FIB_IPV4=m
CONFIG_NF_TABLES_ARP=y
# CONFIG_NF_DUP_IPV4 is not set
# CONFIG_NF_LOG_ARP is not set
# CONFIG_NF_LOG_IPV4 is not set
CONFIG_NF_REJECT_IPV4=m
# CONFIG_IP_NF_IPTABLES is not set
# CONFIG_IP_NF_ARPTABLES is not set
# end of IP: Netfilter Configuration
#
# IPv6: Netfilter Configuration
#
# CONFIG_NF_SOCKET_IPV6 is not set
# CONFIG_NF_TPROXY_IPV6 is not set
CONFIG_NF_TABLES_IPV6=y
CONFIG_NFT_REJECT_IPV6=m
# CONFIG_NFT_DUP_IPV6 is not set
CONFIG_NFT_FIB_IPV6=m
# CONFIG_NF_DUP_IPV6 is not set
CONFIG_NF_REJECT_IPV6=m
# CONFIG_NF_LOG_IPV6 is not set
# CONFIG_IP6_NF_IPTABLES is not set
# end of IPv6: Netfilter Configuration
CONFIG_NF_DEFRAG_IPV6=m
# CONFIG_NF_CONNTRACK_BRIDGE is not set
# CONFIG_BPFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
# CONFIG_6LOWPAN is not set
# CONFIG_IEEE802154 is not set
CONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#
# CONFIG_NET_SCH_CBQ is not set
# CONFIG_NET_SCH_HTB is not set
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_MULTIQ is not set
# CONFIG_NET_SCH_RED is not set
# CONFIG_NET_SCH_SFB is not set
# CONFIG_NET_SCH_SFQ is not set
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not set
# CONFIG_NET_SCH_CBS is not set
# CONFIG_NET_SCH_ETF is not set
# CONFIG_NET_SCH_TAPRIO is not set
# CONFIG_NET_SCH_GRED is not set
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_NETEM is not set
# CONFIG_NET_SCH_DRR is not set
# CONFIG_NET_SCH_MQPRIO is not set
# CONFIG_NET_SCH_SKBPRIO is not set
# CONFIG_NET_SCH_CHOKE is not set
# CONFIG_NET_SCH_QFQ is not set
# CONFIG_NET_SCH_CODEL is not set
CONFIG_NET_SCH_FQ_CODEL=y
# CONFIG_NET_SCH_CAKE is not set
# CONFIG_NET_SCH_FQ is not set
# CONFIG_NET_SCH_HHF is not set
# CONFIG_NET_SCH_PIE is not set
# CONFIG_NET_SCH_INGRESS is not set
# CONFIG_NET_SCH_PLUG is not set
# CONFIG_NET_SCH_ETS is not set
CONFIG_NET_SCH_DEFAULT=y
CONFIG_DEFAULT_FQ_CODEL=y
# CONFIG_DEFAULT_PFIFO_FAST is not set
CONFIG_DEFAULT_NET_SCH="fq_codel"
#
# Classification
#
CONFIG_NET_CLS=y
# CONFIG_NET_CLS_BASIC is not set
# CONFIG_NET_CLS_TCINDEX is not set
# CONFIG_NET_CLS_ROUTE4 is not set
# CONFIG_NET_CLS_FW is not set
# CONFIG_NET_CLS_U32 is not set
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_FLOW is not set
CONFIG_NET_CLS_CGROUP=y
# CONFIG_NET_CLS_BPF is not set
# CONFIG_NET_CLS_FLOWER is not set
# CONFIG_NET_CLS_MATCHALL is not set
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
# CONFIG_NET_EMATCH_CMP is not set
# CONFIG_NET_EMATCH_NBYTE is not set
# CONFIG_NET_EMATCH_U32 is not set
# CONFIG_NET_EMATCH_META is not set
# CONFIG_NET_EMATCH_TEXT is not set
# CONFIG_NET_EMATCH_IPSET is not set
# CONFIG_NET_EMATCH_IPT is not set
CONFIG_NET_CLS_ACT=y
# CONFIG_NET_ACT_POLICE is not set
# CONFIG_NET_ACT_GACT is not set
# CONFIG_NET_ACT_MIRRED is not set
# CONFIG_NET_ACT_SAMPLE is not set
# CONFIG_NET_ACT_IPT is not set
# CONFIG_NET_ACT_NAT is not set
# CONFIG_NET_ACT_PEDIT is not set
# CONFIG_NET_ACT_SIMP is not set
# CONFIG_NET_ACT_SKBEDIT is not set
# CONFIG_NET_ACT_CSUM is not set
# CONFIG_NET_ACT_MPLS is not set
# CONFIG_NET_ACT_VLAN is not set
# CONFIG_NET_ACT_BPF is not set
# CONFIG_NET_ACT_CONNMARK is not set
# CONFIG_NET_ACT_CTINFO is not set
# CONFIG_NET_ACT_SKBMOD is not set
# CONFIG_NET_ACT_IFE is not set
# CONFIG_NET_ACT_TUNNEL_KEY is not set
# CONFIG_NET_ACT_GATE is not set
CONFIG_NET_TC_SKB_EXT=y
CONFIG_NET_SCH_FIFO=y
CONFIG_DCB=y
# CONFIG_DNS_RESOLVER is not set
# CONFIG_BATMAN_ADV is not set
# CONFIG_OPENVSWITCH is not set
# CONFIG_VSOCKETS is not set
# CONFIG_NETLINK_DIAG is not set
CONFIG_MPLS=y
CONFIG_NET_MPLS_GSO=y
# CONFIG_MPLS_ROUTING is not set
CONFIG_NET_NSH=y
# CONFIG_HSR is not set
CONFIG_NET_SWITCHDEV=y
CONFIG_NET_L3_MASTER_DEV=y
# CONFIG_QRTR is not set
# CONFIG_NET_NCSI is not set
CONFIG_PCPU_DEV_REFCNT=y
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_SOCK_RX_QUEUE_MAPPING=y
CONFIG_XPS=y
CONFIG_CGROUP_NET_PRIO=y
CONFIG_CGROUP_NET_CLASSID=y
CONFIG_NET_RX_BUSY_POLL=y
CONFIG_BQL=y
CONFIG_BPF_STREAM_PARSER=y
CONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NET_DROP_MONITOR=y
# end of Network testing
# end of Networking options
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not set
CONFIG_STREAM_PARSER=y
# CONFIG_MCTP is not set
CONFIG_FIB_RULES=y
# CONFIG_WIRELESS is not set
CONFIG_RFKILL=m
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_GPIO is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not set
# CONFIG_NFC is not set
# CONFIG_PSAMPLE is not set
# CONFIG_NET_IFE is not set
CONFIG_LWTUNNEL=y
CONFIG_LWTUNNEL_BPF=y
CONFIG_GRO_CELLS=y
CONFIG_NET_SELFTESTS=y
CONFIG_NET_SOCK_MSG=y
CONFIG_PAGE_POOL=y
# CONFIG_PAGE_POOL_STATS is not set
# CONFIG_FAILOVER is not set
CONFIG_ETHTOOL_NETLINK=y
#
# Device Drivers
#
CONFIG_HAVE_PCI=y
CONFIG_FORCE_PCI=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCI_SYSCALL=y
CONFIG_PCIEPORTBUS=y
# CONFIG_HOTPLUG_PCI_PCIE is not set
CONFIG_PCIEAER=y
# CONFIG_PCIEAER_INJECT is not set
CONFIG_PCIE_ECRC=y
CONFIG_PCIEASPM=y
CONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not set
CONFIG_PCIE_PME=y
CONFIG_PCIE_DPC=y
# CONFIG_PCIE_PTM is not set
CONFIG_PCI_MSI=y
CONFIG_PCI_MSI_IRQ_DOMAIN=y
CONFIG_PCI_MSI_ARCH_FALLBACKS=y
CONFIG_PCI_QUIRKS=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_REALLOC_ENABLE_AUTO is not set
CONFIG_PCI_STUB=y
# CONFIG_PCI_PF_STUB is not set
CONFIG_PCI_ATS=y
CONFIG_PCI_IOV=y
CONFIG_PCI_PRI=y
CONFIG_PCI_PASID=y
# CONFIG_PCI_P2PDMA is not set
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=64
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_CPCI is not set
CONFIG_HOTPLUG_PCI_SHPC=y
CONFIG_HOTPLUG_PCI_POWERNV=y
# CONFIG_HOTPLUG_PCI_RPA is not set
#
# PCI controller drivers
#
# CONFIG_PCI_FTPCI100 is not set
# CONFIG_PCI_HOST_GENERIC is not set
# CONFIG_PCIE_XILINX is not set
# CONFIG_PCIE_MICROCHIP_HOST is not set
#
# DesignWare PCI Core Support
#
# CONFIG_PCIE_DW_PLAT_HOST is not set
# CONFIG_PCI_MESON is not set
# end of DesignWare PCI Core Support
#
# Mobiveil PCIe Core Support
#
# end of Mobiveil PCIe Core Support
#
# Cadence PCIe controllers support
#
# CONFIG_PCIE_CADENCE_PLAT_HOST is not set
# CONFIG_PCI_J721E_HOST is not set
# end of Cadence PCIe controllers support
# end of PCI controller drivers
#
# PCI Endpoint
#
# CONFIG_PCI_ENDPOINT is not set
# end of PCI Endpoint
#
# PCI switch controller drivers
#
# CONFIG_PCI_SW_SWITCHTEC is not set
# end of PCI switch controller drivers
# CONFIG_CXL_BUS is not set
CONFIG_PCCARD=y
# CONFIG_PCMCIA is not set
CONFIG_CARDBUS=y
#
# PC-card bridges
#
# CONFIG_YENTA is not set
# CONFIG_RAPIDIO is not set
#
# Generic Driver Options
#
# CONFIG_UEVENT_HELPER is not set
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
# CONFIG_DEVTMPFS_SAFE is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#
CONFIG_FW_LOADER=y
CONFIG_FW_LOADER_PAGED_BUF=y
CONFIG_FW_LOADER_SYSFS=y
CONFIG_EXTRA_FIRMWARE=""
CONFIG_FW_LOADER_USER_HELPER=y
# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set
# CONFIG_FW_LOADER_COMPRESS is not set
CONFIG_FW_CACHE=y
# CONFIG_FW_UPLOAD is not set
# end of Firmware loader
CONFIG_ALLOW_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
# CONFIG_TEST_ASYNC_DRIVER_PROBE is not set
CONFIG_GENERIC_CPU_AUTOPROBE=y
CONFIG_GENERIC_CPU_VULNERABILITIES=y
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=y
CONFIG_DMA_SHARED_BUFFER=y
# CONFIG_DMA_FENCE_TRACE is not set
# end of Generic Driver Options
#
# Bus devices
#
# CONFIG_MHI_BUS is not set
# CONFIG_MHI_BUS_EP is not set
# end of Bus devices
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
#
# Firmware Drivers
#
#
# ARM System Control and Management Interface Protocol
#
# end of ARM System Control and Management Interface Protocol
# CONFIG_GOOGLE_FIRMWARE is not set
#
# Tegra firmware driver
#
# end of Tegra firmware driver
# end of Firmware Drivers
# CONFIG_GNSS is not set
# CONFIG_MTD is not set
CONFIG_DTC=y
CONFIG_OF=y
# CONFIG_OF_UNITTEST is not set
CONFIG_OF_FLATTREE=y
CONFIG_OF_EARLY_FLATTREE=y
CONFIG_OF_KOBJ=y
CONFIG_OF_DYNAMIC=y
CONFIG_OF_ADDRESS=y
CONFIG_OF_IRQ=y
CONFIG_OF_RESERVED_MEM=y
# CONFIG_OF_OVERLAY is not set
CONFIG_OF_DMA_DEFAULT_COHERENT=y
CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_NULL_BLK is not set
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
# CONFIG_ZRAM is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_VIRTIO_BLK is not set
# CONFIG_BLK_DEV_RBD is not set
#
# NVME Support
#
CONFIG_NVME_CORE=m
CONFIG_BLK_DEV_NVME=m
CONFIG_NVME_MULTIPATH=y
# CONFIG_NVME_VERBOSE_ERRORS is not set
# CONFIG_NVME_HWMON is not set
# CONFIG_NVME_FC is not set
# CONFIG_NVME_TCP is not set
# CONFIG_NVME_TARGET is not set
# end of NVME Support
#
# Misc devices
#
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_IBMVMC is not set
# CONFIG_PHANTOM is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not set
# CONFIG_APDS9802ALS is not set
# CONFIG_ISL29003 is not set
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1770 is not set
# CONFIG_SENSORS_APDS990X is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_SRAM is not set
# CONFIG_DW_XDATA_PCIE is not set
# CONFIG_PCI_ENDPOINT_TEST is not set
# CONFIG_XILINX_SDFEC is not set
# CONFIG_HISI_HIKEY_USB is not set
# CONFIG_OPEN_DICE is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_EEPROM_IDT_89HPESX is not set
# CONFIG_EEPROM_EE1004 is not set
# end of EEPROM support
# CONFIG_CB710_CORE is not set
#
# Texas Instruments shared transport line discipline
#
# CONFIG_TI_ST is not set
# end of Texas Instruments shared transport line discipline
# CONFIG_SENSORS_LIS3_I2C is not set
# CONFIG_ALTERA_STAPL is not set
# CONFIG_GENWQE is not set
# CONFIG_ECHO is not set
# CONFIG_CXL is not set
# CONFIG_OCXL is not set
# CONFIG_BCM_VK is not set
# CONFIG_MISC_ALCOR_PCI is not set
# CONFIG_MISC_RTSX_PCI is not set
# CONFIG_MISC_RTSX_USB is not set
# CONFIG_HABANA_AI is not set
# CONFIG_UACCE is not set
# CONFIG_PVPANIC is not set
# end of Misc devices
#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI_COMMON=y
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=m
CONFIG_BLK_DEV_BSG=y
# CONFIG_CHR_DEV_SCH is not set
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
CONFIG_SCSI_SRP_ATTRS=m
# end of SCSI Transports
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_CXGB4_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_MVUMI is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_MPT3SAS is not set
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_MPI3MR is not set
# CONFIG_SCSI_SMARTPQI is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_MYRB is not set
# CONFIG_SCSI_MYRS is not set
# CONFIG_SCSI_SNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_FDOMAIN_PCI is not set
# CONFIG_SCSI_IPS is not set
CONFIG_SCSI_IBMVSCSI=m
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_WD719X is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
# CONFIG_SCSI_VIRTIO is not set
CONFIG_SCSI_DH=y
CONFIG_SCSI_DH_RDAC=y
CONFIG_SCSI_DH_HP_SW=y
CONFIG_SCSI_DH_EMC=y
CONFIG_SCSI_DH_ALUA=y
# end of SCSI device support
# CONFIG_ATA is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
# CONFIG_BCACHE is not set
CONFIG_BLK_DEV_DM_BUILTIN=y
CONFIG_BLK_DEV_DM=m
CONFIG_DM_DEBUG=y
# CONFIG_DM_UNSTRIPED is not set
# CONFIG_DM_CRYPT is not set
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_THIN_PROVISIONING is not set
# CONFIG_DM_CACHE is not set
# CONFIG_DM_WRITECACHE is not set
# CONFIG_DM_EBS is not set
# CONFIG_DM_ERA is not set
# CONFIG_DM_CLONE is not set
CONFIG_DM_MIRROR=m
# CONFIG_DM_LOG_USERSPACE is not set
# CONFIG_DM_RAID is not set
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_DUST is not set
CONFIG_DM_UEVENT=y
# CONFIG_DM_FLAKEY is not set
# CONFIG_DM_VERITY is not set
# CONFIG_DM_SWITCH is not set
# CONFIG_DM_LOG_WRITES is not set
# CONFIG_DM_INTEGRITY is not set
CONFIG_DM_AUDIT=y
# CONFIG_TARGET_CORE is not set
CONFIG_FUSION=y
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_SAS is not set
CONFIG_FUSION_MAX_SGE=128
CONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_FIREWIRE_NOSY is not set
# end of IEEE 1394 (FireWire) support
CONFIG_MACINTOSH_DRIVERS=y
CONFIG_MAC_EMUMOUSEBTN=y
# CONFIG_WINDFARM is not set
CONFIG_NETDEVICES=y
CONFIG_NET_CORE=y
# CONFIG_BONDING is not set
# CONFIG_DUMMY is not set
# CONFIG_WIREGUARD is not set
# CONFIG_EQUALIZER is not set
CONFIG_NET_FC=y
# CONFIG_NET_TEAM is not set
# CONFIG_MACVLAN is not set
# CONFIG_IPVLAN is not set
# CONFIG_VXLAN is not set
# CONFIG_GENEVE is not set
# CONFIG_BAREUDP is not set
# CONFIG_GTP is not set
# CONFIG_AMT is not set
# CONFIG_MACSEC is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_TUN is not set
CONFIG_TUN_VNET_CROSS_LE=y
# CONFIG_VETH is not set
# CONFIG_VIRTIO_NET is not set
# CONFIG_NLMON is not set
# CONFIG_NET_VRF is not set
# CONFIG_ARCNET is not set
CONFIG_ETHERNET=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_ADAPTEC is not set
# CONFIG_NET_VENDOR_AGERE is not set
# CONFIG_NET_VENDOR_ALACRITECH is not set
# CONFIG_NET_VENDOR_ALTEON is not set
# CONFIG_ALTERA_TSE is not set
CONFIG_NET_VENDOR_AMAZON=y
# CONFIG_ENA_ETHERNET is not set
# CONFIG_NET_VENDOR_AMD is not set
CONFIG_NET_VENDOR_AQUANTIA=y
# CONFIG_AQTION is not set
# CONFIG_NET_VENDOR_ARC is not set
CONFIG_NET_VENDOR_ASIX=y
CONFIG_NET_VENDOR_ATHEROS=y
# CONFIG_ATL2 is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
# CONFIG_ALX is not set
CONFIG_NET_VENDOR_BROADCOM=y
# CONFIG_B44 is not set
# CONFIG_BCMGENET is not set
# CONFIG_BNX2 is not set
# CONFIG_CNIC is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2X is not set
# CONFIG_SYSTEMPORT is not set
# CONFIG_BNXT is not set
CONFIG_NET_VENDOR_CADENCE=y
CONFIG_NET_VENDOR_CAVIUM=y
# CONFIG_THUNDER_NIC_PF is not set
# CONFIG_THUNDER_NIC_VF is not set
# CONFIG_THUNDER_NIC_BGX is not set
# CONFIG_THUNDER_NIC_RGX is not set
CONFIG_CAVIUM_PTP=y
# CONFIG_LIQUIDIO is not set
# CONFIG_LIQUIDIO_VF is not set
CONFIG_NET_VENDOR_CHELSIO=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_CHELSIO_T4 is not set
# CONFIG_CHELSIO_T4VF is not set
CONFIG_NET_VENDOR_CISCO=y
# CONFIG_ENIC is not set
# CONFIG_NET_VENDOR_CORTINA is not set
CONFIG_NET_VENDOR_DAVICOM=y
# CONFIG_DNET is not set
CONFIG_NET_VENDOR_DEC=y
# CONFIG_NET_TULIP is not set
# CONFIG_NET_VENDOR_DLINK is not set
CONFIG_NET_VENDOR_EMULEX=y
# CONFIG_BE2NET is not set
CONFIG_NET_VENDOR_ENGLEDER=y
# CONFIG_TSNEP is not set
# CONFIG_NET_VENDOR_EZCHIP is not set
CONFIG_NET_VENDOR_FUNGIBLE=y
# CONFIG_FUN_ETH is not set
CONFIG_NET_VENDOR_GOOGLE=y
# CONFIG_GVE is not set
# CONFIG_NET_VENDOR_HUAWEI is not set
# CONFIG_NET_VENDOR_I825XX is not set
CONFIG_NET_VENDOR_IBM=y
CONFIG_IBMVETH=m
# CONFIG_IBMVNIC is not set
CONFIG_NET_VENDOR_INTEL=y
# CONFIG_E100 is not set
# CONFIG_E1000 is not set
# CONFIG_E1000E is not set
# CONFIG_IGB is not set
# CONFIG_IGBVF is not set
# CONFIG_IXGB is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGBEVF is not set
# CONFIG_I40E is not set
# CONFIG_I40EVF is not set
# CONFIG_ICE is not set
# CONFIG_FM10K is not set
# CONFIG_IGC is not set
# CONFIG_JME is not set
CONFIG_NET_VENDOR_LITEX=y
# CONFIG_LITEX_LITEETH is not set
# CONFIG_NET_VENDOR_MARVELL is not set
CONFIG_NET_VENDOR_MELLANOX=y
# CONFIG_MLX4_EN is not set
# CONFIG_MLX5_CORE is not set
# CONFIG_MLXSW_CORE is not set
# CONFIG_MLXFW is not set
# CONFIG_NET_VENDOR_MICREL is not set
CONFIG_NET_VENDOR_MICROCHIP=y
# CONFIG_LAN743X is not set
# CONFIG_LAN966X_SWITCH is not set
# CONFIG_NET_VENDOR_MICROSEMI is not set
CONFIG_NET_VENDOR_MICROSOFT=y
CONFIG_NET_VENDOR_MYRI=y
# CONFIG_MYRI10GE is not set
# CONFIG_FEALNX is not set
# CONFIG_NET_VENDOR_NI is not set
# CONFIG_NET_VENDOR_NATSEMI is not set
CONFIG_NET_VENDOR_NETERION=y
# CONFIG_S2IO is not set
# CONFIG_VXGE is not set
CONFIG_NET_VENDOR_NETRONOME=y
# CONFIG_NFP is not set
# CONFIG_NET_VENDOR_NVIDIA is not set
CONFIG_NET_VENDOR_OKI=y
# CONFIG_ETHOC is not set
CONFIG_NET_VENDOR_PACKET_ENGINES=y
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_NET_VENDOR_PENSANDO=y
# CONFIG_IONIC is not set
CONFIG_NET_VENDOR_QLOGIC=y
# CONFIG_QLA3XXX is not set
# CONFIG_QLCNIC is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_QED is not set
CONFIG_NET_VENDOR_BROCADE=y
# CONFIG_BNA is not set
# CONFIG_NET_VENDOR_QUALCOMM is not set
# CONFIG_NET_VENDOR_RDC is not set
CONFIG_NET_VENDOR_REALTEK=y
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_R8169 is not set
# CONFIG_NET_VENDOR_RENESAS is not set
CONFIG_NET_VENDOR_ROCKER=y
# CONFIG_NET_VENDOR_SAMSUNG is not set
# CONFIG_NET_VENDOR_SEEQ is not set
# CONFIG_NET_VENDOR_SILAN is not set
# CONFIG_NET_VENDOR_SIS is not set
CONFIG_NET_VENDOR_SOLARFLARE=y
# CONFIG_SFC is not set
# CONFIG_SFC_FALCON is not set
# CONFIG_SFC_SIENA is not set
# CONFIG_NET_VENDOR_SMSC is not set
# CONFIG_NET_VENDOR_SOCIONEXT is not set
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_NET_VENDOR_SUN is not set
# CONFIG_NET_VENDOR_SYNOPSYS is not set
# CONFIG_NET_VENDOR_TEHUTI is not set
# CONFIG_NET_VENDOR_TI is not set
CONFIG_NET_VENDOR_VERTEXCOM=y
# CONFIG_NET_VENDOR_VIA is not set
# CONFIG_NET_VENDOR_WIZNET is not set
# CONFIG_NET_VENDOR_XILINX is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PHYLIB=y
CONFIG_SWPHY=y
CONFIG_LED_TRIGGER_PHY=y
CONFIG_FIXED_PHY=y
#
# MII PHY device drivers
#
# CONFIG_AMD_PHY is not set
# CONFIG_ADIN_PHY is not set
# CONFIG_ADIN1100_PHY is not set
# CONFIG_AQUANTIA_PHY is not set
# CONFIG_AX88796B_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_BCM54140_PHY is not set
# CONFIG_BCM7XXX_PHY is not set
# CONFIG_BCM84881_PHY is not set
# CONFIG_BCM87XX_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_CORTINA_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_INTEL_XWAY_PHY is not set
# CONFIG_LSI_ET1011C_PHY is not set
# CONFIG_MARVELL_PHY is not set
# CONFIG_MARVELL_10G_PHY is not set
# CONFIG_MARVELL_88X2222_PHY is not set
# CONFIG_MAXLINEAR_GPHY is not set
# CONFIG_MEDIATEK_GE_PHY is not set
# CONFIG_MICREL_PHY is not set
# CONFIG_MICROCHIP_PHY is not set
# CONFIG_MICROCHIP_T1_PHY is not set
# CONFIG_MICROSEMI_PHY is not set
# CONFIG_MOTORCOMM_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_NXP_C45_TJA11XX_PHY is not set
# CONFIG_NXP_TJA11XX_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_REALTEK_PHY is not set
# CONFIG_RENESAS_PHY is not set
# CONFIG_ROCKCHIP_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_TERANETICS_PHY is not set
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
# CONFIG_DP83848_PHY is not set
# CONFIG_DP83867_PHY is not set
# CONFIG_DP83869_PHY is not set
# CONFIG_DP83TD510_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_XILINX_GMII2RGMII is not set
CONFIG_MDIO_DEVICE=y
CONFIG_MDIO_BUS=y
CONFIG_FWNODE_MDIO=y
CONFIG_OF_MDIO=y
CONFIG_MDIO_DEVRES=y
# CONFIG_MDIO_BITBANG is not set
# CONFIG_MDIO_BCM_UNIMAC is not set
# CONFIG_MDIO_HISI_FEMAC is not set
# CONFIG_MDIO_MVUSB is not set
# CONFIG_MDIO_OCTEON is not set
# CONFIG_MDIO_THUNDER is not set
#
# MDIO Multiplexers
#
# CONFIG_MDIO_BUS_MUX_GPIO is not set
# CONFIG_MDIO_BUS_MUX_MULTIPLEXER is not set
# CONFIG_MDIO_BUS_MUX_MMIOREG is not set
#
# PCS device drivers
#
# CONFIG_PCS_XPCS is not set
# end of PCS device drivers
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
CONFIG_USB_NET_DRIVERS=y
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_RTL8152 is not set
# CONFIG_USB_LAN78XX is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_HSO is not set
# CONFIG_USB_IPHETH is not set
# CONFIG_WLAN is not set
CONFIG_WAN=y
# CONFIG_HDLC is not set
#
# Wireless WAN
#
# CONFIG_WWAN is not set
# end of Wireless WAN
# CONFIG_USB4_NET is not set
# CONFIG_NETDEVSIM is not set
# CONFIG_NET_FAILOVER is not set
CONFIG_ISDN=y
# CONFIG_MISDN is not set
#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_LEDS=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_SPARSEKMAP is not set
# CONFIG_INPUT_MATRIXKMAP is not set
CONFIG_INPUT_VIVALDIFMAP=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1050 is not set
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_DLINK_DIR685 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_OMAP4 is not set
# CONFIG_KEYBOARD_TM2_TOUCHKEY is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_CAP11XX is not set
# CONFIG_KEYBOARD_CYPRESS_SF is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_BYD=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=y
CONFIG_MOUSE_PS2_CYPRESS=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_MOUSE_PS2_ELANTECH=y
CONFIG_MOUSE_PS2_ELANTECH_SMBUS=y
CONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_PS2_FOCALTECH=y
CONFIG_MOUSE_PS2_SMBUS=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_CYAPA is not set
# CONFIG_MOUSE_ELAN_I2C is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_MOUSE_SYNAPTICS_USB is not set
# CONFIG_INPUT_JOYSTICK is not set
CONFIG_INPUT_TABLET=y
# CONFIG_TABLET_USB_ACECAD is not set
# CONFIG_TABLET_USB_AIPTEK is not set
# CONFIG_TABLET_USB_HANWANG is not set
# CONFIG_TABLET_USB_KBTAB is not set
# CONFIG_TABLET_USB_PEGASUS is not set
# CONFIG_TABLET_SERIAL_WACOM4 is not set
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_AR1021_I2C is not set
# CONFIG_TOUCHSCREEN_ATMEL_MXT is not set
# CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_BU21029 is not set
# CONFIG_TOUCHSCREEN_CHIPONE_ICN8318 is not set
# CONFIG_TOUCHSCREEN_CY8CTMA140 is not set
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
# CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_EGALAX is not set
# CONFIG_TOUCHSCREEN_EGALAX_SERIAL is not set
# CONFIG_TOUCHSCREEN_EXC3000 is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GOODIX is not set
# CONFIG_TOUCHSCREEN_HIDEEP is not set
# CONFIG_TOUCHSCREEN_HYCON_HY46XX is not set
# CONFIG_TOUCHSCREEN_ILI210X is not set
# CONFIG_TOUCHSCREEN_ILITEK is not set
# CONFIG_TOUCHSCREEN_S6SY761 is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_EKTF2127 is not set
# CONFIG_TOUCHSCREEN_ELAN is not set
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_WACOM_I2C is not set
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
# CONFIG_TOUCHSCREEN_MMS114 is not set
# CONFIG_TOUCHSCREEN_MELFAS_MIP4 is not set
# CONFIG_TOUCHSCREEN_MSG2638 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_IMAGIS is not set
# CONFIG_TOUCHSCREEN_IMX6UL_TSC is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_PIXCIR is not set
# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC_SERIO is not set
# CONFIG_TOUCHSCREEN_TSC2004 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_RM_TS is not set
# CONFIG_TOUCHSCREEN_SILEAD is not set
# CONFIG_TOUCHSCREEN_SIS_I2C is not set
# CONFIG_TOUCHSCREEN_ST1232 is not set
# CONFIG_TOUCHSCREEN_STMFTS is not set
# CONFIG_TOUCHSCREEN_SX8654 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
# CONFIG_TOUCHSCREEN_ZET6223 is not set
# CONFIG_TOUCHSCREEN_ZFORCE is not set
# CONFIG_TOUCHSCREEN_ROHM_BU21023 is not set
# CONFIG_TOUCHSCREEN_IQS5XX is not set
# CONFIG_TOUCHSCREEN_ZINITIX is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_ATMEL_CAPTOUCH is not set
# CONFIG_INPUT_BMA150 is not set
# CONFIG_INPUT_E3X0_BUTTON is not set
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_MMA8450 is not set
# CONFIG_INPUT_GPIO_BEEPER is not set
# CONFIG_INPUT_GPIO_DECODER is not set
# CONFIG_INPUT_GPIO_VIBRA is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_KXTJ9 is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
# CONFIG_INPUT_UINPUT is not set
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_PWM_BEEPER is not set
# CONFIG_INPUT_PWM_VIBRA is not set
# CONFIG_INPUT_GPIO_ROTARY_ENCODER is not set
# CONFIG_INPUT_DA7280_HAPTICS is not set
# CONFIG_INPUT_ADXL34X is not set
# CONFIG_INPUT_IMS_PCU is not set
# CONFIG_INPUT_IQS269A is not set
# CONFIG_INPUT_IQS626A is not set
# CONFIG_INPUT_IQS7222 is not set
# CONFIG_INPUT_CMA3000 is not set
# CONFIG_INPUT_IDEAPAD_SLIDEBAR is not set
# CONFIG_INPUT_DRV260X_HAPTICS is not set
# CONFIG_INPUT_DRV2665_HAPTICS is not set
# CONFIG_INPUT_DRV2667_HAPTICS is not set
# CONFIG_RMI4_CORE is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_ARCH_MIGHT_HAVE_PC_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_XILINX_XPS_PS2 is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_SERIO_PS2MULT is not set
# CONFIG_SERIO_ARC_PS2 is not set
# CONFIG_SERIO_APBPS2 is not set
# CONFIG_SERIO_GPIO_PS2 is not set
# CONFIG_USERIO is not set
# CONFIG_GAMEPORT is not set
# end of Hardware I/O ports
# end of Input device support
#
# Character devices
#
CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_LDISC_AUTOLOAD=y
#
# Serial drivers
#
CONFIG_SERIAL_EARLYCON=y
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set
CONFIG_SERIAL_8250_16550A_VARIANTS=y
# CONFIG_SERIAL_8250_FINTEK is not set
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_DMA=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_EXAR=y
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y
CONFIG_SERIAL_8250_FSL=y
# CONFIG_SERIAL_8250_DW is not set
# CONFIG_SERIAL_8250_RT288X is not set
CONFIG_SERIAL_8250_PERICOM=y
# CONFIG_SERIAL_OF_PLATFORM is not set
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_KGDB_NMI is not set
# CONFIG_SERIAL_UARTLITE is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_CONSOLE_POLL=y
# CONFIG_SERIAL_ICOM is not set
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_SIFIVE is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_XILINX_PS_UART is not set
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_SERIAL_FSL_LINFLEXUART is not set
# CONFIG_SERIAL_CONEXANT_DIGICOLOR is not set
# end of Serial drivers
CONFIG_SERIAL_MCTRL_GPIO=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_SYNCLINK_GT is not set
# CONFIG_N_HDLC is not set
# CONFIG_PPC_EPAPR_HV_BYTECHAN is not set
# CONFIG_N_GSM is not set
# CONFIG_NOZOMI is not set
# CONFIG_NULL_TTY is not set
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_CONSOLE=y
# CONFIG_HVC_OLD_HVSI is not set
CONFIG_HVC_OPAL=y
CONFIG_HVC_RTAS=y
# CONFIG_HVC_UDBG is not set
# CONFIG_HVCS is not set
# CONFIG_SERIAL_DEV_BUS is not set
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_IBM_BSR is not set
# CONFIG_POWERNV_OP_PANEL is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_HW_RANDOM_BA431 is not set
CONFIG_HW_RANDOM_VIRTIO=y
CONFIG_HW_RANDOM_PSERIES=m
# CONFIG_HW_RANDOM_POWERNV is not set
# CONFIG_HW_RANDOM_CCTRNG is not set
# CONFIG_HW_RANDOM_XIPHERA is not set
# CONFIG_APPLICOM is not set
CONFIG_DEVMEM=y
CONFIG_NVRAM=y
# CONFIG_DEVPORT is not set
# CONFIG_HANGCHECK_TIMER is not set
CONFIG_TCG_TPM=y
CONFIG_HW_RANDOM_TPM=y
CONFIG_TCG_TIS_CORE=y
CONFIG_TCG_TIS=y
# CONFIG_TCG_TIS_I2C_CR50 is not set
CONFIG_TCG_TIS_I2C_ATMEL=y
CONFIG_TCG_TIS_I2C_INFINEON=y
CONFIG_TCG_TIS_I2C_NUVOTON=y
# CONFIG_TCG_ATMEL is not set
CONFIG_TCG_IBMVTPM=y
# CONFIG_TCG_VTPM_PROXY is not set
# CONFIG_TCG_TIS_ST33ZP24_I2C is not set
# CONFIG_XILLYBUS is not set
# CONFIG_XILLYUSB is not set
CONFIG_RANDOM_TRUST_CPU=y
CONFIG_RANDOM_TRUST_BOOTLOADER=y
# end of Character devices
#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
# CONFIG_I2C_CHARDEV is not set
# CONFIG_I2C_MUX is not set
CONFIG_I2C_HELPER_AUTO=y
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_NVIDIA_GPU is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_CBUS_GPIO is not set
# CONFIG_I2C_DESIGNWARE_PLATFORM is not set
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_MPC is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_CP2615 is not set
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#
CONFIG_I2C_OPAL=y
# CONFIG_I2C_VIRTIO is not set
# end of I2C Hardware Bus support
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_SLAVE is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# end of I2C support
# CONFIG_I3C is not set
# CONFIG_SPI is not set
# CONFIG_SPMI is not set
# CONFIG_HSI is not set
CONFIG_PPS=y
# CONFIG_PPS_DEBUG is not set
#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not set
# CONFIG_PPS_CLIENT_LDISC is not set
# CONFIG_PPS_CLIENT_GPIO is not set
#
# PPS generators support
#
#
# PTP clock support
#
CONFIG_PTP_1588_CLOCK=y
CONFIG_PTP_1588_CLOCK_OPTIONAL=y
# CONFIG_DP83640_PHY is not set
# CONFIG_PTP_1588_CLOCK_INES is not set
# CONFIG_PTP_1588_CLOCK_IDT82P33 is not set
# CONFIG_PTP_1588_CLOCK_IDTCM is not set
# end of PTP clock support
# CONFIG_PINCTRL is not set
CONFIG_GPIOLIB=y
CONFIG_GPIOLIB_FASTPATH_LIMIT=512
CONFIG_OF_GPIO=y
# CONFIG_DEBUG_GPIO is not set
CONFIG_GPIO_CDEV=y
CONFIG_GPIO_CDEV_V1=y
#
# Memory mapped GPIO drivers
#
# CONFIG_GPIO_74XX_MMIO is not set
# CONFIG_GPIO_ALTERA is not set
# CONFIG_GPIO_CADENCE is not set
# CONFIG_GPIO_DWAPB is not set
# CONFIG_GPIO_EXAR is not set
# CONFIG_GPIO_FTGPIO010 is not set
# CONFIG_GPIO_GENERIC_PLATFORM is not set
# CONFIG_GPIO_GRGPIO is not set
# CONFIG_GPIO_HLWD is not set
# CONFIG_GPIO_MB86S7X is not set
# CONFIG_GPIO_SIFIVE is not set
# CONFIG_GPIO_XILINX is not set
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers
#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_ADNP is not set
# CONFIG_GPIO_GW_PLD is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCA9570 is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_TPIC2810 is not set
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#
# end of MFD GPIO expanders
#
# PCI GPIO expanders
#
# CONFIG_GPIO_BT8XX is not set
# CONFIG_GPIO_PCI_IDIO_16 is not set
# CONFIG_GPIO_PCIE_IDIO_24 is not set
# CONFIG_GPIO_RDC321X is not set
# end of PCI GPIO expanders
#
# USB GPIO expanders
#
# end of USB GPIO expanders
#
# Virtual GPIO drivers
#
# CONFIG_GPIO_AGGREGATOR is not set
# CONFIG_GPIO_MOCKUP is not set
# CONFIG_GPIO_VIRTIO is not set
# CONFIG_GPIO_SIM is not set
# end of Virtual GPIO drivers
# CONFIG_W1 is not set
CONFIG_POWER_RESET=y
CONFIG_POWER_RESET_GPIO=y
# CONFIG_POWER_RESET_GPIO_RESTART is not set
# CONFIG_POWER_RESET_LTC2952 is not set
# CONFIG_POWER_RESET_RESTART is not set
# CONFIG_POWER_RESET_SYSCON is not set
# CONFIG_POWER_RESET_SYSCON_POWEROFF is not set
# CONFIG_NVMEM_REBOOT_MODE is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
CONFIG_POWER_SUPPLY_HWMON=y
# CONFIG_PDA_POWER is not set
# CONFIG_IP5XXX_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_CHARGER_ADP5061 is not set
# CONFIG_BATTERY_CW2015 is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SAMSUNG_SDI is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_CHARGER_SBS is not set
# CONFIG_BATTERY_BQ27XXX is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_LT3651 is not set
# CONFIG_CHARGER_LTC4162L is not set
# CONFIG_CHARGER_DETECTOR_MAX14656 is not set
# CONFIG_CHARGER_MAX77976 is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ2515X is not set
# CONFIG_CHARGER_BQ25890 is not set
# CONFIG_CHARGER_BQ25980 is not set
# CONFIG_CHARGER_BQ256XX is not set
# CONFIG_BATTERY_GAUGE_LTC2941 is not set
# CONFIG_BATTERY_GOLDFISH is not set
# CONFIG_BATTERY_RT5033 is not set
# CONFIG_CHARGER_RT9455 is not set
# CONFIG_CHARGER_BD99954 is not set
# CONFIG_BATTERY_UG3105 is not set
CONFIG_HWMON=y
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM1177 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7410 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_AHT10 is not set
# CONFIG_SENSORS_AQUACOMPUTER_D5NEXT is not set
# CONFIG_SENSORS_AS370 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_AXI_FAN_CONTROL is not set
# CONFIG_SENSORS_ASPEED is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_CORSAIR_CPRO is not set
# CONFIG_SENSORS_CORSAIR_PSU is not set
# CONFIG_SENSORS_DS620 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FTSTEUTATES is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set
# CONFIG_SENSORS_IBMPOWERNV is not set
# CONFIG_SENSORS_JC42 is not set
# CONFIG_SENSORS_POWR1220 is not set
# CONFIG_SENSORS_LINEAGE is not set
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2947_I2C is not set
# CONFIG_SENSORS_LTC2990 is not set
# CONFIG_SENSORS_LTC2992 is not set
# CONFIG_SENSORS_LTC4151 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4222 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LTC4260 is not set
# CONFIG_SENSORS_LTC4261 is not set
# CONFIG_SENSORS_MAX127 is not set
# CONFIG_SENSORS_MAX16065 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX1668 is not set
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX31730 is not set
# CONFIG_SENSORS_MAX6620 is not set
# CONFIG_SENSORS_MAX6621 is not set
# CONFIG_SENSORS_MAX6639 is not set
# CONFIG_SENSORS_MAX6642 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_MAX6697 is not set
# CONFIG_SENSORS_MAX31790 is not set
# CONFIG_SENSORS_MCP3021 is not set
# CONFIG_SENSORS_TC654 is not set
# CONFIG_SENSORS_TPS23861 is not set
# CONFIG_SENSORS_MR75203 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LM95234 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_LM95245 is not set
# CONFIG_SENSORS_NCT6775_I2C is not set
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_NPCM7XX is not set
# CONFIG_SENSORS_NZXT_KRAKEN2 is not set
# CONFIG_SENSORS_NZXT_SMART2 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_PWM_FAN is not set
# CONFIG_SENSORS_SBTSI is not set
# CONFIG_SENSORS_SBRMI is not set
# CONFIG_SENSORS_SHT15 is not set
# CONFIG_SENSORS_SHT21 is not set
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHT4x is not set
# CONFIG_SENSORS_SHTC1 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SY7636A is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_EMC2103 is not set
# CONFIG_SENSORS_EMC6W201 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_STTS751 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_ADC128D818 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_INA209 is not set
# CONFIG_SENSORS_INA2XX is not set
# CONFIG_SENSORS_INA238 is not set
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP103 is not set
# CONFIG_SENSORS_TMP108 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_TMP464 is not set
# CONFIG_SENSORS_TMP513 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83773G is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
CONFIG_THERMAL=y
# CONFIG_THERMAL_NETLINK is not set
# CONFIG_THERMAL_STATISTICS is not set
CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0
CONFIG_THERMAL_HWMON=y
CONFIG_THERMAL_OF=y
# CONFIG_THERMAL_WRITABLE_TRIPS is not set
CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set
# CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set
CONFIG_THERMAL_GOV_FAIR_SHARE=y
CONFIG_THERMAL_GOV_STEP_WISE=y
# CONFIG_THERMAL_GOV_BANG_BANG is not set
# CONFIG_THERMAL_GOV_USER_SPACE is not set
# CONFIG_THERMAL_GOV_POWER_ALLOCATOR is not set
# CONFIG_CPU_THERMAL is not set
# CONFIG_THERMAL_EMULATION is not set
# CONFIG_THERMAL_MMIO is not set
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=y
CONFIG_WATCHDOG_OPEN_TIMEOUT=0
CONFIG_WATCHDOG_SYSFS=y
# CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT is not set
#
# Watchdog Pretimeout Governors
#
# CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_GPIO_WATCHDOG is not set
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_CADENCE_WATCHDOG is not set
# CONFIG_DW_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_MEN_A21_WDT is not set
# CONFIG_WATCHDOG_RTAS is not set
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set
CONFIG_BCMA_POSSIBLE=y
# CONFIG_BCMA is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_ACT8945A is not set
# CONFIG_MFD_AS3711 is not set
# CONFIG_MFD_AS3722 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_ATMEL_FLEXCOM is not set
# CONFIG_MFD_ATMEL_HLCDC is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_BD9571MWV is not set
# CONFIG_MFD_AXP20X_I2C is not set
# CONFIG_MFD_MADERA is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_DLN2 is not set
# CONFIG_MFD_GATEWORKS_GSC is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_MFD_MP2629 is not set
# CONFIG_MFD_HI6421_PMIC is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_LPC_ICH is not set
# CONFIG_LPC_SCH is not set
# CONFIG_MFD_IQS62X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_MAX14577 is not set
# CONFIG_MFD_MAX77620 is not set
# CONFIG_MFD_MAX77650 is not set
# CONFIG_MFD_MAX77686 is not set
# CONFIG_MFD_MAX77693 is not set
# CONFIG_MFD_MAX77714 is not set
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MT6360 is not set
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_MFD_VIPERBOARD is not set
# CONFIG_MFD_NTXEC is not set
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RT4831 is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_RK808 is not set
# CONFIG_MFD_RN5T618 is not set
# CONFIG_MFD_SEC_CORE is not set
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SIMPLE_MFD_I2C is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_SKY81452 is not set
# CONFIG_MFD_STMPE is not set
# CONFIG_MFD_SYSCON is not set
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_TI_LMU is not set
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TPS65217 is not set
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TI_LP87565 is not set
# CONFIG_MFD_TPS65218 is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_TQMX86 is not set
# CONFIG_MFD_VX855 is not set
# CONFIG_MFD_LOCHNAGAR is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_ROHM_BD718XX is not set
# CONFIG_MFD_ROHM_BD71828 is not set
# CONFIG_MFD_ROHM_BD957XMUF is not set
# CONFIG_MFD_STPMIC1 is not set
# CONFIG_MFD_STMFX is not set
# CONFIG_MFD_ATC260X_I2C is not set
# CONFIG_MFD_QCOM_PM8008 is not set
# CONFIG_MFD_RSMU_I2C is not set
# end of Multifunction device drivers
# CONFIG_REGULATOR is not set
# CONFIG_RC_CORE is not set
#
# CEC support
#
CONFIG_MEDIA_CEC_SUPPORT=y
# CONFIG_CEC_CH7322 is not set
# CONFIG_USB_PULSE8_CEC is not set
# CONFIG_USB_RAINSHADOW_CEC is not set
# end of CEC support
# CONFIG_MEDIA_SUPPORT is not set
#
# Graphics support
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
#
# ARM devices
#
# end of ARM devices
#
# Frame buffer Devices
#
CONFIG_FB_CMDLINE=y
CONFIG_FB_NOTIFY=y
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_MACMODES=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
CONFIG_FB_OF=y
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
CONFIG_FB_MATROX=y
# CONFIG_FB_MATROX_MILLENIUM is not set
# CONFIG_FB_MATROX_MYSTIQUE is not set
CONFIG_FB_MATROX_G=y
# CONFIG_FB_MATROX_I2C is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
CONFIG_FB_IBM_GXT4500=y
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_SIMPLE is not set
# CONFIG_FB_SSD1307 is not set
# CONFIG_FB_SM712 is not set
# end of Frame buffer Devices
#
# Backlight & LCD device support
#
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_KTD253 is not set
# CONFIG_BACKLIGHT_PWM is not set
# CONFIG_BACKLIGHT_QCOM_WLED is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_LP855X is not set
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_BACKLIGHT_ARCXCNN is not set
# CONFIG_BACKLIGHT_LED is not set
# end of Backlight & LCD device support
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_DUMMY_CONSOLE_COLUMNS=80
CONFIG_DUMMY_CONSOLE_ROWS=25
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION is not set
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y
# end of Console display driver support
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
# end of Graphics support
# CONFIG_SOUND is not set
#
# HID support
#
CONFIG_HID=y
CONFIG_HID_BATTERY_STRENGTH=y
CONFIG_HIDRAW=y
# CONFIG_UHID is not set
CONFIG_HID_GENERIC=y
#
# Special HID drivers
#
# CONFIG_HID_A4TECH is not set
# CONFIG_HID_ACCUTOUCH is not set
# CONFIG_HID_ACRUX is not set
# CONFIG_HID_APPLE is not set
# CONFIG_HID_APPLEIR is not set
# CONFIG_HID_ASUS is not set
# CONFIG_HID_AUREAL is not set
# CONFIG_HID_BELKIN is not set
# CONFIG_HID_BETOP_FF is not set
# CONFIG_HID_BIGBEN_FF is not set
# CONFIG_HID_CHERRY is not set
# CONFIG_HID_CHICONY is not set
# CONFIG_HID_CORSAIR is not set
# CONFIG_HID_COUGAR is not set
# CONFIG_HID_MACALLY is not set
# CONFIG_HID_CMEDIA is not set
# CONFIG_HID_CP2112 is not set
# CONFIG_HID_CREATIVE_SB0540 is not set
# CONFIG_HID_CYPRESS is not set
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELAN is not set
# CONFIG_HID_ELECOM is not set
# CONFIG_HID_ELO is not set
# CONFIG_HID_EZKEY is not set
# CONFIG_HID_FT260 is not set
# CONFIG_HID_GEMBIRD is not set
# CONFIG_HID_GFRM is not set
# CONFIG_HID_GLORIOUS is not set
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_VIVALDI is not set
# CONFIG_HID_GT683R is not set
# CONFIG_HID_KEYTOUCH is not set
# CONFIG_HID_KYE is not set
# CONFIG_HID_UCLOGIC is not set
# CONFIG_HID_WALTOP is not set
# CONFIG_HID_VIEWSONIC is not set
# CONFIG_HID_XIAOMI is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_ICADE is not set
# CONFIG_HID_ITE is not set
# CONFIG_HID_JABRA is not set
# CONFIG_HID_TWINHAN is not set
# CONFIG_HID_KENSINGTON is not set
# CONFIG_HID_LCPOWER is not set
# CONFIG_HID_LED is not set
# CONFIG_HID_LENOVO is not set
# CONFIG_HID_LETSKETCH is not set
# CONFIG_HID_LOGITECH is not set
CONFIG_HID_MAGICMOUSE=y
# CONFIG_HID_MALTRON is not set
# CONFIG_HID_MAYFLASH is not set
# CONFIG_HID_MEGAWORLD_FF is not set
# CONFIG_HID_REDRAGON is not set
# CONFIG_HID_MICROSOFT is not set
# CONFIG_HID_MONTEREY is not set
# CONFIG_HID_MULTITOUCH is not set
# CONFIG_HID_NINTENDO is not set
# CONFIG_HID_NTI is not set
CONFIG_HID_NTRIG=y
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PENMOUNT is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PLANTRONICS is not set
# CONFIG_HID_RAZER is not set
# CONFIG_HID_PRIMAX is not set
# CONFIG_HID_RETRODE is not set
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_SAITEK is not set
# CONFIG_HID_SAMSUNG is not set
# CONFIG_HID_SEMITEK is not set
# CONFIG_HID_SIGMAMICRO is not set
# CONFIG_HID_SONY is not set
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_STEAM is not set
# CONFIG_HID_STEELSERIES is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_RMI is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TIVO is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_THINGM is not set
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_U2FZERO is not set
# CONFIG_HID_WACOM is not set
# CONFIG_HID_WIIMOTE is not set
# CONFIG_HID_XINMO is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
# CONFIG_HID_SENSOR_HUB is not set
# CONFIG_HID_ALPS is not set
# CONFIG_HID_MCP2221 is not set
# end of Special HID drivers
#
# USB HID support
#
CONFIG_USB_HID=y
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
# end of USB HID support
#
# I2C HID support
#
# CONFIG_I2C_HID_OF is not set
# CONFIG_I2C_HID_OF_GOODIX is not set
# end of I2C HID support
# end of HID support
CONFIG_USB_OHCI_BIG_ENDIAN_DESC=y
CONFIG_USB_OHCI_BIG_ENDIAN_MMIO=y
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
# CONFIG_USB_LED_TRIG is not set
# CONFIG_USB_ULPI_BUS is not set
# CONFIG_USB_CONN_GPIO is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=y
CONFIG_USB_PCI=y
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#
CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_FEW_INIT_RETRIES is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_PRODUCTLIST is not set
# CONFIG_USB_LEDS_TRIGGER_USBPORT is not set
CONFIG_USB_AUTOSUSPEND_DELAY=2
CONFIG_USB_MON=y
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_XHCI_HCD=y
# CONFIG_USB_XHCI_DBGCAP is not set
CONFIG_USB_XHCI_PCI=y
# CONFIG_USB_XHCI_PCI_RENESAS is not set
# CONFIG_USB_XHCI_PLATFORM is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_PCI=y
# CONFIG_USB_EHCI_FSL is not set
CONFIG_USB_EHCI_HCD_PPC_OF=y
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_PPC_OF_BE=y
CONFIG_USB_OHCI_HCD_PPC_OF_LE=y
CONFIG_USB_OHCI_HCD_PPC_OF=y
CONFIG_USB_OHCI_HCD_PCI=y
# CONFIG_USB_OHCI_HCD_PLATFORM is not set
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HCD_TEST_MODE is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
# CONFIG_USB_STORAGE is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USBIP_CORE is not set
# CONFIG_USB_CDNS_SUPPORT is not set
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_DWC3 is not set
# CONFIG_USB_DWC2 is not set
# CONFIG_USB_CHIPIDEA is not set
# CONFIG_USB_ISP1760 is not set
#
# USB port drivers
#
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CONSOLE=y
CONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_SIMPLE is not set
# CONFIG_USB_SERIAL_AIRCABLE is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_CH341 is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP210X is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_F81232 is not set
# CONFIG_USB_SERIAL_F8153X is not set
# CONFIG_USB_SERIAL_GARMIN is not set
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_IUU is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_METRO is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_MXUPORT is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_OTI6858 is not set
# CONFIG_USB_SERIAL_QCAUX is not set
# CONFIG_USB_SERIAL_QUALCOMM is not set
# CONFIG_USB_SERIAL_SPCP8X5 is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
# CONFIG_USB_SERIAL_SYMBOL is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_SERIAL_OPTICON is not set
# CONFIG_USB_SERIAL_XSENS_MT is not set
# CONFIG_USB_SERIAL_WISHBONE is not set
# CONFIG_USB_SERIAL_SSU100 is not set
# CONFIG_USB_SERIAL_QT2 is not set
# CONFIG_USB_SERIAL_UPD78F0730 is not set
# CONFIG_USB_SERIAL_XR is not set
# CONFIG_USB_SERIAL_DEBUG is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_APPLE_MFI_FASTCHARGE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
# CONFIG_USB_EZUSB_FX2 is not set
# CONFIG_USB_HUB_USB251XB is not set
# CONFIG_USB_HSIC_USB3503 is not set
# CONFIG_USB_HSIC_USB4604 is not set
# CONFIG_USB_LINK_LAYER_TEST is not set
# CONFIG_USB_CHAOSKEY is not set
#
# USB Physical Layer drivers
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ISP1301 is not set
# end of USB Physical Layer drivers
# CONFIG_USB_GADGET is not set
CONFIG_TYPEC=y
CONFIG_TYPEC_TCPM=y
CONFIG_TYPEC_TCPCI=y
CONFIG_TYPEC_RT1711H=y
# CONFIG_TYPEC_TCPCI_MAXIM is not set
# CONFIG_TYPEC_FUSB302 is not set
CONFIG_TYPEC_UCSI=y
# CONFIG_UCSI_CCG is not set
# CONFIG_TYPEC_TPS6598X is not set
# CONFIG_TYPEC_RT1719 is not set
# CONFIG_TYPEC_HD3SS3220 is not set
# CONFIG_TYPEC_STUSB160X is not set
# CONFIG_TYPEC_WUSB3801 is not set
#
# USB Type-C Multiplexer/DeMultiplexer Switch support
#
# CONFIG_TYPEC_MUX_FSA4480 is not set
# CONFIG_TYPEC_MUX_PI3USB30532 is not set
# end of USB Type-C Multiplexer/DeMultiplexer Switch support
#
# USB Type-C Alternate Mode drivers
#
# end of USB Type-C Alternate Mode drivers
CONFIG_USB_ROLE_SWITCH=y
# CONFIG_MMC is not set
# CONFIG_SCSI_UFSHCD is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
# CONFIG_LEDS_CLASS_FLASH is not set
# CONFIG_LEDS_CLASS_MULTICOLOR is not set
CONFIG_LEDS_BRIGHTNESS_HW_CHANGED=y
#
# LED drivers
#
# CONFIG_LEDS_AN30259A is not set
# CONFIG_LEDS_AW2013 is not set
# CONFIG_LEDS_BCM6328 is not set
# CONFIG_LEDS_BCM6358 is not set
# CONFIG_LEDS_LM3530 is not set
# CONFIG_LEDS_LM3532 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_LM3692X is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_GPIO is not set
# CONFIG_LEDS_LP3944 is not set
# CONFIG_LEDS_LP3952 is not set
# CONFIG_LEDS_LP50XX is not set
# CONFIG_LEDS_LP55XX_COMMON is not set
# CONFIG_LEDS_LP8860 is not set
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_PWM is not set
# CONFIG_LEDS_BD2802 is not set
# CONFIG_LEDS_LT3593 is not set
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
# CONFIG_LEDS_LM355x is not set
# CONFIG_LEDS_IS31FL319X is not set
# CONFIG_LEDS_IS31FL32XX is not set
#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)
#
# CONFIG_LEDS_BLINKM is not set
# CONFIG_LEDS_POWERNV is not set
# CONFIG_LEDS_MLXREG is not set
# CONFIG_LEDS_USER is not set
# CONFIG_LEDS_TI_LMU_COMMON is not set
#
# Flash and Torch LED drivers
#
#
# RGB LED drivers
#
#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
# CONFIG_LEDS_TRIGGER_TIMER is not set
# CONFIG_LEDS_TRIGGER_ONESHOT is not set
# CONFIG_LEDS_TRIGGER_HEARTBEAT is not set
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
# CONFIG_LEDS_TRIGGER_CPU is not set
# CONFIG_LEDS_TRIGGER_ACTIVITY is not set
# CONFIG_LEDS_TRIGGER_GPIO is not set
# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set
#
# iptables trigger is under Netfilter config (LED target)
#
# CONFIG_LEDS_TRIGGER_TRANSIENT is not set
# CONFIG_LEDS_TRIGGER_CAMERA is not set
# CONFIG_LEDS_TRIGGER_PANIC is not set
# CONFIG_LEDS_TRIGGER_NETDEV is not set
# CONFIG_LEDS_TRIGGER_PATTERN is not set
# CONFIG_LEDS_TRIGGER_AUDIO is not set
# CONFIG_LEDS_TRIGGER_TTY is not set
#
# Simple LED drivers
#
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC_ATOMIC_SCRUB=y
CONFIG_EDAC_SUPPORT=y
CONFIG_EDAC=y
CONFIG_EDAC_LEGACY_SYSFS=y
# CONFIG_EDAC_DEBUG is not set
# CONFIG_EDAC_CPC925 is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_MC146818_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_SYSTOHC is not set
# CONFIG_RTC_DEBUG is not set
CONFIG_RTC_NVMEM=y
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_ABB5ZES3 is not set
# CONFIG_RTC_DRV_ABEOZ9 is not set
# CONFIG_RTC_DRV_ABX80X is not set
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_HYM8563 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_ISL12026 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8523 is not set
# CONFIG_RTC_DRV_PCF85063 is not set
# CONFIG_RTC_DRV_PCF85363 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8010 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
# CONFIG_RTC_DRV_RV3028 is not set
# CONFIG_RTC_DRV_RV3032 is not set
# CONFIG_RTC_DRV_RV8803 is not set
# CONFIG_RTC_DRV_SD3078 is not set
#
# SPI RTC drivers
#
CONFIG_RTC_I2C_AND_SPI=y
#
# SPI and I2C RTC drivers
#
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_PCF2127 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set
# CONFIG_RTC_DRV_RX6110 is not set
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1685_FAMILY is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_DS2404 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
CONFIG_RTC_DRV_OPAL=y
# CONFIG_RTC_DRV_ZYNQMP is not set
#
# on-CPU RTC drivers
#
CONFIG_RTC_DRV_GENERIC=y
# CONFIG_RTC_DRV_CADENCE is not set
# CONFIG_RTC_DRV_FTRTC010 is not set
# CONFIG_RTC_DRV_R7301 is not set
#
# HID Sensor RTC drivers
#
# CONFIG_RTC_DRV_GOLDFISH is not set
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#
CONFIG_DMA_ENGINE=y
CONFIG_DMA_OF=y
# CONFIG_ALTERA_MSGDMA is not set
# CONFIG_DW_AXI_DMAC is not set
# CONFIG_FSL_EDMA is not set
# CONFIG_INTEL_IDMA64 is not set
# CONFIG_PLX_DMA is not set
# CONFIG_XILINX_ZYNQMP_DPDMA is not set
# CONFIG_QCOM_HIDMA_MGMT is not set
# CONFIG_QCOM_HIDMA is not set
# CONFIG_DW_DMAC is not set
# CONFIG_DW_DMAC_PCI is not set
# CONFIG_DW_EDMA is not set
# CONFIG_DW_EDMA_PCIE is not set
# CONFIG_SF_PDMA is not set
#
# DMA Clients
#
CONFIG_ASYNC_TX_DMA=y
# CONFIG_DMATEST is not set
#
# DMABUF options
#
CONFIG_SYNC_FILE=y
# CONFIG_SW_SYNC is not set
# CONFIG_UDMABUF is not set
# CONFIG_DMABUF_MOVE_NOTIFY is not set
# CONFIG_DMABUF_DEBUG is not set
# CONFIG_DMABUF_SELFTESTS is not set
# CONFIG_DMABUF_HEAPS is not set
# CONFIG_DMABUF_SYSFS_STATS is not set
# end of DMABUF options
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
# CONFIG_VFIO is not set
CONFIG_VIRT_DRIVERS=y
CONFIG_VIRTIO=y
CONFIG_VIRTIO_PCI_LIB=y
CONFIG_VIRTIO_PCI_LIB_LEGACY=y
CONFIG_VIRTIO_MENU=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_PCI_LEGACY=y
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_VIRTIO_INPUT is not set
# CONFIG_VIRTIO_MMIO is not set
# CONFIG_VDPA is not set
CONFIG_VHOST_MENU=y
# CONFIG_VHOST_NET is not set
CONFIG_VHOST_CROSS_ENDIAN_LEGACY=y
#
# Microsoft Hyper-V guest support
#
# end of Microsoft Hyper-V guest support
# CONFIG_GREYBUS is not set
# CONFIG_COMEDI is not set
# CONFIG_STAGING is not set
# CONFIG_GOLDFISH is not set
# CONFIG_COMMON_CLK is not set
CONFIG_HWSPINLOCK=y
#
# Clock Source drivers
#
CONFIG_I8253_LOCK=y
CONFIG_CLKBLD_I8253=y
# CONFIG_MICROCHIP_PIT64B is not set
# end of Clock Source drivers
# CONFIG_MAILBOX is not set
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
#
# Generic IOMMU Pagetable Support
#
# end of Generic IOMMU Pagetable Support
# CONFIG_IOMMU_DEBUGFS is not set
CONFIG_IOMMU_DEFAULT_DMA_STRICT=y
# CONFIG_IOMMU_DEFAULT_DMA_LAZY is not set
# CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not set
CONFIG_OF_IOMMU=y
CONFIG_SPAPR_TCE_IOMMU=y
#
# Remoteproc drivers
#
# CONFIG_REMOTEPROC is not set
# end of Remoteproc drivers
#
# Rpmsg drivers
#
# CONFIG_RPMSG_VIRTIO is not set
# end of Rpmsg drivers
# CONFIG_SOUNDWIRE is not set
#
# SOC (System On Chip) specific Drivers
#
#
# Amlogic SoC drivers
#
# end of Amlogic SoC drivers
#
# Broadcom SoC drivers
#
# end of Broadcom SoC drivers
#
# NXP/Freescale QorIQ SoC drivers
#
# CONFIG_QUICC_ENGINE is not set
# end of NXP/Freescale QorIQ SoC drivers
#
# i.MX SoC drivers
#
# end of i.MX SoC drivers
#
# Enable LiteX SoC Builder specific drivers
#
# CONFIG_LITEX_SOC_CONTROLLER is not set
# end of Enable LiteX SoC Builder specific drivers
#
# Qualcomm SoC drivers
#
# end of Qualcomm SoC drivers
# CONFIG_SOC_TI is not set
#
# Xilinx SoC drivers
#
# end of Xilinx SoC drivers
# end of SOC (System On Chip) specific Drivers
# CONFIG_PM_DEVFREQ is not set
# CONFIG_EXTCON is not set
# CONFIG_MEMORY is not set
# CONFIG_IIO is not set
# CONFIG_NTB is not set
# CONFIG_VME_BUS is not set
CONFIG_PWM=y
CONFIG_PWM_SYSFS=y
# CONFIG_PWM_DEBUG is not set
# CONFIG_PWM_ATMEL_TCB is not set
# CONFIG_PWM_DWC is not set
# CONFIG_PWM_FSL_FTM is not set
# CONFIG_PWM_PCA9685 is not set
#
# IRQ chip support
#
CONFIG_IRQCHIP=y
# CONFIG_AL_FIC is not set
# end of IRQ chip support
# CONFIG_IPACK_BUS is not set
# CONFIG_RESET_CONTROLLER is not set
#
# PHY Subsystem
#
# CONFIG_GENERIC_PHY is not set
# CONFIG_PHY_CAN_TRANSCEIVER is not set
#
# PHY drivers for Broadcom platforms
#
# CONFIG_BCM_KONA_USB2_PHY is not set
# end of PHY drivers for Broadcom platforms
# CONFIG_PHY_CADENCE_DPHY is not set
# CONFIG_PHY_CADENCE_DPHY_RX is not set
# CONFIG_PHY_CADENCE_SALVO is not set
# CONFIG_PHY_PXA_28NM_HSIC is not set
# CONFIG_PHY_PXA_28NM_USB2 is not set
# CONFIG_PHY_MAPPHONE_MDM6600 is not set
# end of PHY Subsystem
# CONFIG_POWERCAP is not set
# CONFIG_MCB is not set
#
# Performance monitor support
#
# end of Performance monitor support
CONFIG_RAS=y
CONFIG_USB4=y
# CONFIG_USB4_DEBUGFS_WRITE is not set
# CONFIG_USB4_DMA_TEST is not set
#
# Android
#
# CONFIG_ANDROID is not set
# end of Android
# CONFIG_LIBNVDIMM is not set
CONFIG_DAX=y
# CONFIG_DEV_DAX is not set
CONFIG_NVMEM=y
CONFIG_NVMEM_SYSFS=y
# CONFIG_NVMEM_RMEM is not set
#
# HW tracing support
#
# CONFIG_STM is not set
# CONFIG_INTEL_TH is not set
# end of HW tracing support
# CONFIG_FPGA is not set
# CONFIG_FSI is not set
# CONFIG_SIOX is not set
# CONFIG_SLIMBUS is not set
# CONFIG_INTERCONNECT is not set
# CONFIG_COUNTER is not set
# CONFIG_MOST is not set
# CONFIG_PECI is not set
# CONFIG_HTE is not set
# end of Device Drivers
#
# File systems
#
CONFIG_DCACHE_WORD_ACCESS=y
# CONFIG_VALIDATE_FS_PARSER is not set
CONFIG_FS_IOMAP=y
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_EXT4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_XFS_FS=m
CONFIG_XFS_SUPPORT_V4=y
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_XFS_RT is not set
# CONFIG_XFS_ONLINE_SCRUB is not set
# CONFIG_XFS_WARN is not set
# CONFIG_XFS_DEBUG is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
# CONFIG_F2FS_FS is not set
CONFIG_FS_DAX=y
CONFIG_FS_DAX_PMD=y
CONFIG_FS_POSIX_ACL=y
CONFIG_EXPORTFS=y
CONFIG_EXPORTFS_BLOCK_OPS=y
CONFIG_FILE_LOCKING=y
# CONFIG_FS_ENCRYPTION is not set
# CONFIG_FS_VERITY is not set
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
CONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QUOTA_DEBUG is not set
CONFIG_QUOTA_TREE=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_AUTOFS4_FS=y
CONFIG_AUTOFS_FS=y
# CONFIG_FUSE_FS is not set
# CONFIG_OVERLAY_FS is not set
#
# Caches
#
# CONFIG_FSCACHE is not set
# end of Caches
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
# end of CD-ROM/DVD Filesystems
#
# DOS/FAT/EXFAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_EXFAT_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS3_FS is not set
# end of DOS/FAT/EXFAT/NT Filesystems
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_VMCORE_DEVICE_DUMP=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_PROC_CHILDREN=y
CONFIG_KERNFS=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
# CONFIG_TMPFS_INODE64 is not set
CONFIG_ARCH_SUPPORTS_HUGETLBFS=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_MEMFD_CREATE=y
CONFIG_ARCH_HAS_GIGANTIC_PAGE=y
CONFIG_CONFIGFS_FS=y
# end of Pseudo filesystems
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ORANGEFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX6FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_PSTORE=y
CONFIG_PSTORE_DEFAULT_KMSG_BYTES=10240
CONFIG_PSTORE_DEFLATE_COMPRESS=y
# CONFIG_PSTORE_LZO_COMPRESS is not set
# CONFIG_PSTORE_LZ4_COMPRESS is not set
# CONFIG_PSTORE_LZ4HC_COMPRESS is not set
# CONFIG_PSTORE_842_COMPRESS is not set
# CONFIG_PSTORE_ZSTD_COMPRESS is not set
CONFIG_PSTORE_COMPRESS=y
CONFIG_PSTORE_DEFLATE_COMPRESS_DEFAULT=y
CONFIG_PSTORE_COMPRESS_DEFAULT="deflate"
# CONFIG_PSTORE_CONSOLE is not set
# CONFIG_PSTORE_PMSG is not set
# CONFIG_PSTORE_FTRACE is not set
# CONFIG_PSTORE_RAM is not set
# CONFIG_PSTORE_BLK is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_EROFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
# CONFIG_NFS_V2 is not set
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_SWAP is not set
CONFIG_NFS_DEBUG=y
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
# CONFIG_NFSD is not set
CONFIG_GRACE_PERIOD=m
CONFIG_LOCKD=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_DEBUG=y
# CONFIG_CEPH_FS is not set
# CONFIG_CIFS is not set
# CONFIG_SMB_SERVER is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_MAC_ROMAN is not set
# CONFIG_NLS_MAC_CELTIC is not set
# CONFIG_NLS_MAC_CENTEURO is not set
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set
# CONFIG_NLS_MAC_GAELIC is not set
# CONFIG_NLS_MAC_GREEK is not set
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not set
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set
# CONFIG_NLS_UTF8 is not set
# CONFIG_DLM is not set
# CONFIG_UNICODE is not set
CONFIG_IO_WQ=y
# end of File systems
#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_REQUEST_CACHE is not set
CONFIG_PERSISTENT_KEYRINGS=y
CONFIG_TRUSTED_KEYS=y
CONFIG_TRUSTED_KEYS_TPM=y
CONFIG_ENCRYPTED_KEYS=y
# CONFIG_USER_DECRYPTED_DATA is not set
# CONFIG_KEY_DH_OPERATIONS is not set
# CONFIG_SECURITY_DMESG_RESTRICT is not set
CONFIG_SECURITY=y
CONFIG_SECURITY_WRITABLE_HOOKS=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
# CONFIG_SECURITY_PATH is not set
CONFIG_LSM_MMAP_MIN_ADDR=65535
CONFIG_HAVE_HARDENED_USERCOPY_ALLOCATOR=y
CONFIG_HARDENED_USERCOPY=y
CONFIG_FORTIFY_SOURCE=y
# CONFIG_STATIC_USERMODEHELPER is not set
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
CONFIG_SECURITY_SELINUX_SIDTAB_HASH_BITS=9
CONFIG_SECURITY_SELINUX_SID2STR_CACHE_SIZE=256
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_SECURITY_LOADPIN is not set
CONFIG_SECURITY_YAMA=y
# CONFIG_SECURITY_SAFESETID is not set
# CONFIG_SECURITY_LOCKDOWN_LSM is not set
# CONFIG_SECURITY_LANDLOCK is not set
CONFIG_INTEGRITY=y
CONFIG_INTEGRITY_SIGNATURE=y
CONFIG_INTEGRITY_ASYMMETRIC_KEYS=y
CONFIG_INTEGRITY_TRUSTED_KEYRING=y
CONFIG_INTEGRITY_PLATFORM_KEYRING=y
CONFIG_LOAD_PPC_KEYS=y
CONFIG_INTEGRITY_AUDIT=y
CONFIG_IMA=y
CONFIG_IMA_KEXEC=y
CONFIG_IMA_MEASURE_PCR_IDX=10
CONFIG_IMA_LSM_RULES=y
# CONFIG_IMA_NG_TEMPLATE is not set
CONFIG_IMA_SIG_TEMPLATE=y
CONFIG_IMA_DEFAULT_TEMPLATE="ima-sig"
# CONFIG_IMA_DEFAULT_HASH_SHA1 is not set
CONFIG_IMA_DEFAULT_HASH_SHA256=y
# CONFIG_IMA_DEFAULT_HASH_SHA512 is not set
CONFIG_IMA_DEFAULT_HASH="sha256"
CONFIG_IMA_WRITE_POLICY=y
CONFIG_IMA_READ_POLICY=y
CONFIG_IMA_APPRAISE=y
CONFIG_IMA_ARCH_POLICY=y
# CONFIG_IMA_APPRAISE_BUILD_POLICY is not set
CONFIG_IMA_APPRAISE_BOOTPARAM=y
CONFIG_IMA_APPRAISE_MODSIG=y
CONFIG_IMA_TRUSTED_KEYRING=y
# CONFIG_IMA_BLACKLIST_KEYRING is not set
# CONFIG_IMA_LOAD_X509 is not set
CONFIG_IMA_MEASURE_ASYMMETRIC_KEYS=y
CONFIG_IMA_QUEUE_EARLY_BOOT_KEYS=y
CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT=y
# CONFIG_IMA_DISABLE_HTABLE is not set
CONFIG_EVM=y
CONFIG_EVM_ATTR_FSUUID=y
# CONFIG_EVM_ADD_XATTRS is not set
# CONFIG_EVM_LOAD_X509 is not set
CONFIG_DEFAULT_SECURITY_SELINUX=y
# CONFIG_DEFAULT_SECURITY_DAC is not set
CONFIG_LSM="yama,integrity,selinux,bpf"
#
# Kernel hardening options
#
#
# Memory initialization
#
CONFIG_INIT_STACK_NONE=y
# CONFIG_INIT_ON_ALLOC_DEFAULT_ON is not set
# CONFIG_INIT_ON_FREE_DEFAULT_ON is not set
# end of Memory initialization
CONFIG_RANDSTRUCT_NONE=y
# end of Kernel hardening options
# end of Security options
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_FIPS=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_SKCIPHER=y
CONFIG_CRYPTO_SKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_AKCIPHER2=y
CONFIG_CRYPTO_AKCIPHER=y
CONFIG_CRYPTO_KPP2=y
CONFIG_CRYPTO_ACOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_USER is not set
# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
# CONFIG_CRYPTO_MANAGER_EXTRA_TESTS is not set
CONFIG_CRYPTO_GF128MUL=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_NULL2=y
# CONFIG_CRYPTO_PCRYPT is not set
CONFIG_CRYPTO_CRYPTD=y
CONFIG_CRYPTO_AUTHENC=y
# CONFIG_CRYPTO_TEST is not set
#
# Public-key cryptography
#
CONFIG_CRYPTO_RSA=y
# CONFIG_CRYPTO_DH is not set
# CONFIG_CRYPTO_ECDH is not set
# CONFIG_CRYPTO_ECDSA is not set
# CONFIG_CRYPTO_ECRDSA is not set
# CONFIG_CRYPTO_SM2 is not set
# CONFIG_CRYPTO_CURVE25519 is not set
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
CONFIG_CRYPTO_GCM=y
# CONFIG_CRYPTO_CHACHA20POLY1305 is not set
# CONFIG_CRYPTO_AEGIS128 is not set
# CONFIG_CRYPTO_SEQIV is not set
# CONFIG_CRYPTO_ECHAINIV is not set
#
# Block modes
#
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_CFB=y
CONFIG_CRYPTO_CTR=y
CONFIG_CRYPTO_CTS=y
CONFIG_CRYPTO_ECB=y
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_OFB is not set
# CONFIG_CRYPTO_PCBC is not set
CONFIG_CRYPTO_XTS=m
# CONFIG_CRYPTO_KEYWRAP is not set
# CONFIG_CRYPTO_ADIANTUM is not set
CONFIG_CRYPTO_ESSIV=y
#
# Hash modes
#
# CONFIG_CRYPTO_CMAC is not set
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set
#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
# CONFIG_CRYPTO_CRC32C_VPMSUM is not set
# CONFIG_CRYPTO_CRC32 is not set
# CONFIG_CRYPTO_XXHASH is not set
# CONFIG_CRYPTO_BLAKE2B is not set
# CONFIG_CRYPTO_BLAKE2S is not set
CONFIG_CRYPTO_CRCT10DIF=y
# CONFIG_CRYPTO_CRCT10DIF_VPMSUM is not set
CONFIG_CRYPTO_CRC64_ROCKSOFT=m
CONFIG_CRYPTO_GHASH=y
# CONFIG_CRYPTO_POLY1305 is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MD5_PPC is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD160 is not set
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA1_PPC is not set
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
# CONFIG_CRYPTO_SHA3 is not set
# CONFIG_CRYPTO_SM3_GENERIC is not set
# CONFIG_CRYPTO_STREEBOG is not set
# CONFIG_CRYPTO_WP512 is not set
#
# Ciphers
#
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_TI is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_CHACHA20 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_SM4_GENERIC is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_LZO=y
# CONFIG_CRYPTO_842 is not set
# CONFIG_CRYPTO_LZ4 is not set
# CONFIG_CRYPTO_LZ4HC is not set
# CONFIG_CRYPTO_ZSTD is not set
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_DRBG_MENU=y
CONFIG_CRYPTO_DRBG_HMAC=y
CONFIG_CRYPTO_DRBG_HASH=y
CONFIG_CRYPTO_DRBG_CTR=y
CONFIG_CRYPTO_DRBG=y
CONFIG_CRYPTO_JITTERENTROPY=y
CONFIG_CRYPTO_USER_API=y
CONFIG_CRYPTO_USER_API_HASH=y
CONFIG_CRYPTO_USER_API_SKCIPHER=y
CONFIG_CRYPTO_USER_API_RNG=y
# CONFIG_CRYPTO_USER_API_RNG_CAVP is not set
CONFIG_CRYPTO_USER_API_AEAD=y
CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE=y
CONFIG_CRYPTO_HASH_INFO=y
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_NX=y
CONFIG_CRYPTO_DEV_NX_COMPRESS=y
CONFIG_CRYPTO_DEV_NX_COMPRESS_PSERIES=y
CONFIG_CRYPTO_DEV_NX_COMPRESS_POWERNV=y
# CONFIG_CRYPTO_DEV_ATMEL_ECC is not set
# CONFIG_CRYPTO_DEV_ATMEL_SHA204A is not set
# CONFIG_CRYPTO_DEV_NITROX_CNN55XX is not set
CONFIG_CRYPTO_DEV_VMX=y
CONFIG_CRYPTO_DEV_VMX_ENCRYPT=m
# CONFIG_CRYPTO_DEV_VIRTIO is not set
# CONFIG_CRYPTO_DEV_SAFEXCEL is not set
# CONFIG_CRYPTO_DEV_CCREE is not set
# CONFIG_CRYPTO_DEV_AMLOGIC_GXL is not set
CONFIG_ASYMMETRIC_KEY_TYPE=y
CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y
CONFIG_X509_CERTIFICATE_PARSER=y
# CONFIG_PKCS8_PRIVATE_KEY_PARSER is not set
CONFIG_PKCS7_MESSAGE_PARSER=y
# CONFIG_PKCS7_TEST_KEY is not set
# CONFIG_SIGNED_PE_FILE_VERIFICATION is not set
#
# Certificates for signature checking
#
CONFIG_MODULE_SIG_KEY="certs/signing_key.pem"
CONFIG_MODULE_SIG_KEY_TYPE_RSA=y
# CONFIG_MODULE_SIG_KEY_TYPE_ECDSA is not set
CONFIG_SYSTEM_TRUSTED_KEYRING=y
CONFIG_SYSTEM_TRUSTED_KEYS=""
CONFIG_SYSTEM_EXTRA_CERTIFICATE=y
CONFIG_SYSTEM_EXTRA_CERTIFICATE_SIZE=4096
# CONFIG_SECONDARY_TRUSTED_KEYRING is not set
CONFIG_SYSTEM_BLACKLIST_KEYRING=y
CONFIG_SYSTEM_BLACKLIST_HASH_LIST=""
# CONFIG_SYSTEM_REVOCATION_LIST is not set
# CONFIG_SYSTEM_BLACKLIST_AUTH_UPDATE is not set
# end of Certificates for signature checking
CONFIG_BINARY_PRINTF=y
#
# Library routines
#
# CONFIG_PACKING is not set
CONFIG_BITREVERSE=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_NET_UTILS=y
# CONFIG_CORDIC is not set
# CONFIG_PRIME_NUMBERS is not set
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
CONFIG_ARCH_HAS_FAST_MULTIPLIER=y
#
# Crypto library routines
#
CONFIG_CRYPTO_LIB_AES=y
CONFIG_CRYPTO_LIB_BLAKE2S_GENERIC=y
# CONFIG_CRYPTO_LIB_CHACHA is not set
# CONFIG_CRYPTO_LIB_CURVE25519 is not set
CONFIG_CRYPTO_LIB_POLY1305_RSIZE=1
# CONFIG_CRYPTO_LIB_POLY1305 is not set
# CONFIG_CRYPTO_LIB_CHACHA20POLY1305 is not set
CONFIG_CRYPTO_LIB_SHA256=y
# end of Crypto library routines
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC64_ROCKSOFT=m
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
CONFIG_CRC32_SLICEBY8=y
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
CONFIG_CRC64=m
# CONFIG_CRC4 is not set
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=m
# CONFIG_CRC8 is not set
CONFIG_XXHASH=y
# CONFIG_RANDOM32_SELFTEST is not set
CONFIG_842_DECOMPRESS=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_LZ4_DECOMPRESS=y
CONFIG_ZSTD_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
# CONFIG_XZ_DEC_MICROLZMA is not set
CONFIG_XZ_DEC_BCJ=y
# CONFIG_XZ_DEC_TEST is not set
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_DECOMPRESS_LZ4=y
CONFIG_DECOMPRESS_ZSTD=y
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_INTERVAL_TREE=y
CONFIG_XARRAY_MULTI=y
CONFIG_ASSOCIATIVE_ARRAY=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT_MAP=y
CONFIG_HAS_DMA=y
CONFIG_DMA_OPS=y
CONFIG_DMA_OPS_BYPASS=y
CONFIG_ARCH_HAS_DMA_MAP_DIRECT=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_DMA_DECLARE_COHERENT=y
CONFIG_ARCH_HAS_FORCE_DMA_UNENCRYPTED=y
CONFIG_SWIOTLB=y
# CONFIG_DMA_RESTRICTED_POOL is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_DMA_MAP_BENCHMARK is not set
CONFIG_SGL_ALLOC=y
CONFIG_IOMMU_HELPER=y
CONFIG_CPU_RMAP=y
CONFIG_DQL=y
CONFIG_GLOB=y
# CONFIG_GLOB_SELFTEST is not set
CONFIG_NLATTR=y
CONFIG_CLZ_TAB=y
CONFIG_IRQ_POLL=y
CONFIG_MPILIB=y
CONFIG_SIGNATURE=y
CONFIG_LIBFDT=y
CONFIG_OID_REGISTRY=y
CONFIG_HAVE_GENERIC_VDSO=y
CONFIG_GENERIC_GETTIMEOFDAY=y
CONFIG_GENERIC_VDSO_TIME_NS=y
CONFIG_FONT_SUPPORT=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_SG_POOL=y
CONFIG_ARCH_HAS_PMEM_API=y
CONFIG_ARCH_HAS_MEMREMAP_COMPAT_ALIGN=y
CONFIG_ARCH_HAS_UACCESS_FLUSHCACHE=y
CONFIG_ARCH_HAS_COPY_MC=y
CONFIG_ARCH_STACKWALK=y
CONFIG_STACKDEPOT=y
CONFIG_STACK_HASH_ORDER=20
CONFIG_SBITMAP=y
# end of Library routines
CONFIG_ASN1_ENCODER=y
#
# Kernel hacking
#
#
# printk and dmesg options
#
CONFIG_PRINTK_TIME=y
# CONFIG_PRINTK_CALLER is not set
# CONFIG_STACKTRACE_BUILD_ID is not set
CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7
CONFIG_CONSOLE_LOGLEVEL_QUIET=4
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4
CONFIG_DYNAMIC_DEBUG=y
CONFIG_DYNAMIC_DEBUG_CORE=y
CONFIG_SYMBOLIC_ERRNAME=y
CONFIG_DEBUG_BUGVERBOSE=y
# end of printk and dmesg options
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_MISC=y
#
# Compile-time checks and compiler options
#
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_INFO_NONE is not set
# CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT is not set
CONFIG_DEBUG_INFO_DWARF4=y
# CONFIG_DEBUG_INFO_DWARF5 is not set
# CONFIG_DEBUG_INFO_REDUCED is not set
# CONFIG_DEBUG_INFO_COMPRESSED is not set
# CONFIG_DEBUG_INFO_SPLIT is not set
CONFIG_DEBUG_INFO_BTF=y
CONFIG_PAHOLE_HAS_SPLIT_BTF=y
CONFIG_DEBUG_INFO_BTF_MODULES=y
# CONFIG_MODULE_ALLOW_BTF_MISMATCH is not set
# CONFIG_GDB_SCRIPTS is not set
CONFIG_FRAME_WARN=2048
CONFIG_STRIP_ASM_SYMS=y
# CONFIG_READABLE_ASM is not set
# CONFIG_HEADERS_INSTALL is not set
CONFIG_DEBUG_SECTION_MISMATCH=y
CONFIG_SECTION_MISMATCH_WARN_ONLY=y
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# end of Compile-time checks and compiler options
#
# Generic Kernel Debugging Instruments
#
CONFIG_MAGIC_SYSRQ=y
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1
CONFIG_MAGIC_SYSRQ_SERIAL=y
CONFIG_MAGIC_SYSRQ_SERIAL_SEQUENCE=""
CONFIG_DEBUG_FS=y
CONFIG_DEBUG_FS_ALLOW_ALL=y
# CONFIG_DEBUG_FS_DISALLOW_MOUNT is not set
# CONFIG_DEBUG_FS_ALLOW_NONE is not set
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_KGDB=y
CONFIG_KGDB_HONOUR_BLOCKLIST=y
CONFIG_KGDB_SERIAL_CONSOLE=y
CONFIG_KGDB_TESTS=y
# CONFIG_KGDB_TESTS_ON_BOOT is not set
CONFIG_KGDB_KDB=y
CONFIG_KDB_DEFAULT_ENABLE=0x0
CONFIG_KDB_KEYBOARD=y
CONFIG_KDB_CONTINUE_CATASTROPHIC=0
CONFIG_ARCH_HAS_UBSAN_SANITIZE_ALL=y
# CONFIG_UBSAN is not set
# end of Generic Kernel Debugging Instruments
#
# Networking Debugging
#
# CONFIG_NET_DEV_REFCNT_TRACKER is not set
# CONFIG_NET_NS_REFCNT_TRACKER is not set
# CONFIG_DEBUG_NET is not set
# end of Networking Debugging
#
# Memory Debugging
#
CONFIG_PAGE_EXTENSION=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_SLUB_DEBUG=y
# CONFIG_SLUB_DEBUG_ON is not set
CONFIG_PAGE_OWNER=y
CONFIG_PAGE_POISONING=y
# CONFIG_DEBUG_PAGE_REF is not set
# CONFIG_DEBUG_RODATA_TEST is not set
CONFIG_ARCH_HAS_DEBUG_WX=y
# CONFIG_DEBUG_WX is not set
CONFIG_GENERIC_PTDUMP=y
# CONFIG_PTDUMP_DEBUGFS is not set
# CONFIG_DEBUG_OBJECTS is not set
CONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_SCHED_STACK_END_CHECK is not set
CONFIG_ARCH_HAS_DEBUG_VM_PGTABLE=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VM_PGTABLE is not set
CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
# CONFIG_DEBUG_VIRTUAL is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_PER_CPU_MAPS is not set
CONFIG_HAVE_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_HAVE_ARCH_KASAN=y
CONFIG_HAVE_ARCH_KASAN_VMALLOC=y
CONFIG_ARCH_DISABLE_KASAN_INLINE=y
CONFIG_CC_HAS_KASAN_GENERIC=y
CONFIG_CC_HAS_WORKING_NOSANITIZE_ADDRESS=y
# CONFIG_KASAN is not set
# end of Memory Debugging
CONFIG_DEBUG_SHIRQ=y
#
# Debug Oops, Lockups and Hangs
#
CONFIG_PANIC_ON_OOPS=y
CONFIG_PANIC_ON_OOPS_VALUE=1
CONFIG_LOCKUP_DETECTOR=y
CONFIG_SOFTLOCKUP_DETECTOR=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_HARDLOCKUP_DETECTOR=y
# CONFIG_BOOTPARAM_HARDLOCKUP_PANIC is not set
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
# CONFIG_WQ_WATCHDOG is not set
# CONFIG_TEST_LOCKUP is not set
# end of Debug Oops, Lockups and Hangs
#
# Scheduler Debugging
#
CONFIG_SCHED_DEBUG=y
CONFIG_SCHED_INFO=y
CONFIG_SCHEDSTATS=y
# end of Scheduler Debugging
# CONFIG_DEBUG_TIMEKEEPING is not set
#
# Lock Debugging (spinlocks, mutexes, etc...)
#
CONFIG_LOCK_DEBUGGING_SUPPORT=y
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_DEBUG_RWSEMS is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_LOCK_TORTURE_TEST is not set
# CONFIG_WW_MUTEX_SELFTEST is not set
# CONFIG_SCF_TORTURE_TEST is not set
# CONFIG_CSD_LOCK_WAIT_DEBUG is not set
# end of Lock Debugging (spinlocks, mutexes, etc...)
# CONFIG_DEBUG_IRQFLAGS is not set
CONFIG_STACKTRACE=y
# CONFIG_WARN_ALL_UNSEEDED_RANDOM is not set
# CONFIG_DEBUG_KOBJECT is not set
#
# Debug kernel data structures
#
CONFIG_DEBUG_LIST=y
# CONFIG_DEBUG_PLIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
CONFIG_BUG_ON_DATA_CORRUPTION=y
# end of Debug kernel data structures
# CONFIG_DEBUG_CREDENTIALS is not set
#
# RCU Debugging
#
# CONFIG_RCU_SCALE_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_REF_SCALE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=60
CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=0
# CONFIG_RCU_TRACE is not set
# CONFIG_RCU_EQS_DEBUG is not set
# end of RCU Debugging
# CONFIG_DEBUG_WQ_FORCE_RR_CPU is not set
# CONFIG_CPU_HOTPLUG_STATE_CONTROL is not set
# CONFIG_LATENCYTOP is not set
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_ARGS=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACER_MAX_TRACE=y
CONFIG_TRACE_CLOCK=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_TRACING=y
CONFIG_GENERIC_TRACER=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
# CONFIG_BOOTTIME_TRACING is not set
CONFIG_FUNCTION_TRACER=y
CONFIG_FUNCTION_GRAPH_TRACER=y
CONFIG_DYNAMIC_FTRACE=y
CONFIG_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_DYNAMIC_FTRACE_WITH_ARGS=y
# CONFIG_FUNCTION_PROFILER is not set
CONFIG_STACK_TRACER=y
# CONFIG_IRQSOFF_TRACER is not set
CONFIG_SCHED_TRACER=y
CONFIG_HWLAT_TRACER=y
CONFIG_OSNOISE_TRACER=y
CONFIG_TIMERLAT_TRACER=y
CONFIG_FTRACE_SYSCALLS=y
CONFIG_TRACER_SNAPSHOT=y
# CONFIG_TRACER_SNAPSHOT_PER_CPU_SWAP is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
CONFIG_BLK_DEV_IO_TRACE=y
CONFIG_KPROBE_EVENTS=y
# CONFIG_KPROBE_EVENTS_ON_NOTRACE is not set
CONFIG_UPROBE_EVENTS=y
CONFIG_BPF_EVENTS=y
CONFIG_DYNAMIC_EVENTS=y
CONFIG_PROBE_EVENTS=y
# CONFIG_BPF_KPROBE_OVERRIDE is not set
CONFIG_FTRACE_MCOUNT_RECORD=y
CONFIG_FTRACE_MCOUNT_USE_RECORDMCOUNT=y
CONFIG_TRACING_MAP=y
CONFIG_SYNTH_EVENTS=y
CONFIG_HIST_TRIGGERS=y
# CONFIG_TRACE_EVENT_INJECT is not set
# CONFIG_TRACEPOINT_BENCHMARK is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
# CONFIG_TRACE_EVAL_MAP_FILE is not set
# CONFIG_FTRACE_RECORD_RECURSION is not set
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_RING_BUFFER_STARTUP_TEST is not set
# CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS is not set
# CONFIG_PREEMPTIRQ_DELAY_TEST is not set
# CONFIG_SYNTH_EVENT_GEN_TEST is not set
# CONFIG_KPROBE_EVENT_GEN_TEST is not set
# CONFIG_HIST_TRIGGERS_DEBUG is not set
CONFIG_SAMPLES=y
# CONFIG_SAMPLE_AUXDISPLAY is not set
# CONFIG_SAMPLE_TRACE_EVENTS is not set
# CONFIG_SAMPLE_TRACE_CUSTOM_EVENTS is not set
# CONFIG_SAMPLE_TRACE_PRINTK is not set
# CONFIG_SAMPLE_TRACE_ARRAY is not set
# CONFIG_SAMPLE_KOBJECT is not set
# CONFIG_SAMPLE_KPROBES is not set
# CONFIG_SAMPLE_HW_BREAKPOINT is not set
# CONFIG_SAMPLE_KFIFO is not set
# CONFIG_SAMPLE_KDB is not set
# CONFIG_SAMPLE_LIVEPATCH is not set
# CONFIG_SAMPLE_CONFIGFS is not set
# CONFIG_SAMPLE_VFIO_MDEV_MDPY_FB is not set
# CONFIG_SAMPLE_WATCHDOG is not set
CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y
CONFIG_STRICT_DEVMEM=y
# CONFIG_IO_STRICT_DEVMEM is not set
#
# powerpc Debugging
#
CONFIG_PPC_DISABLE_WERROR=y
CONFIG_PRINT_STACK_DEPTH=64
# CONFIG_HCALL_STATS is not set
CONFIG_PPC_EMULATED_STATS=y
# CONFIG_CODE_PATCHING_SELFTEST is not set
CONFIG_JUMP_LABEL_FEATURE_CHECKS=y
# CONFIG_JUMP_LABEL_FEATURE_CHECK_DEBUG is not set
# CONFIG_FTR_FIXUP_SELFTEST is not set
CONFIG_MSI_BITMAP_SELFTEST=y
# CONFIG_PPC_IRQ_SOFT_MASK_DEBUG is not set
# CONFIG_PPC_RFI_SRR_DEBUG is not set
CONFIG_XMON=y
# CONFIG_XMON_DEFAULT is not set
CONFIG_XMON_DISASSEMBLY=y
CONFIG_XMON_DEFAULT_RO_MODE=y
CONFIG_DEBUGGER=y
CONFIG_BOOTX_TEXT=y
# CONFIG_PPC_EARLY_DEBUG is not set
# CONFIG_PPC_FAST_ENDIAN_SWITCH is not set
# end of powerpc Debugging
#
# Kernel Testing and Coverage
#
# CONFIG_KUNIT is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
CONFIG_FUNCTION_ERROR_INJECTION=y
# CONFIG_FAULT_INJECTION is not set
CONFIG_ARCH_HAS_KCOV=y
CONFIG_CC_HAS_SANCOV_TRACE_PC=y
CONFIG_RUNTIME_TESTING_MENU=y
# CONFIG_LKDTM is not set
# CONFIG_TEST_MIN_HEAP is not set
# CONFIG_TEST_DIV64 is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_TEST_REF_TRACKER is not set
# CONFIG_RBTREE_TEST is not set
# CONFIG_REED_SOLOMON_TEST is not set
# CONFIG_INTERVAL_TREE_TEST is not set
# CONFIG_PERCPU_TEST is not set
CONFIG_ATOMIC64_SELFTEST=y
# CONFIG_TEST_HEXDUMP is not set
# CONFIG_STRING_SELFTEST is not set
# CONFIG_TEST_STRING_HELPERS is not set
# CONFIG_TEST_STRSCPY is not set
CONFIG_TEST_KSTRTOX=y
# CONFIG_TEST_PRINTF is not set
# CONFIG_TEST_SCANF is not set
# CONFIG_TEST_BITMAP is not set
# CONFIG_TEST_UUID is not set
# CONFIG_TEST_XARRAY is not set
# CONFIG_TEST_RHASHTABLE is not set
# CONFIG_TEST_SIPHASH is not set
# CONFIG_TEST_IDA is not set
# CONFIG_TEST_LKM is not set
# CONFIG_TEST_BITOPS is not set
# CONFIG_TEST_VMALLOC is not set
# CONFIG_TEST_USER_COPY is not set
# CONFIG_TEST_BPF is not set
# CONFIG_TEST_BLACKHOLE_DEV is not set
# CONFIG_FIND_BIT_BENCHMARK is not set
# CONFIG_TEST_FIRMWARE is not set
# CONFIG_TEST_SYSCTL is not set
# CONFIG_TEST_UDELAY is not set
# CONFIG_TEST_STATIC_KEYS is not set
# CONFIG_TEST_KMOD is not set
# CONFIG_TEST_MEMCAT_P is not set
# CONFIG_TEST_LIVEPATCH is not set
# CONFIG_TEST_MEMINIT is not set
# CONFIG_TEST_HMM is not set
# CONFIG_TEST_FREE_PAGES is not set
CONFIG_ARCH_USE_MEMTEST=y
# CONFIG_MEMTEST is not set
# end of Kernel Testing and Coverage
# end of Kernel hacking
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-02-17 11:15 xfs: system fails to boot up due to Internal error xfs_trans_cancel shrikanth hegde
2023-02-17 11:25 ` shrikanth hegde
@ 2023-02-17 11:30 ` shrikanth hegde
2023-02-17 15:03 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-02-17 16:53 ` Darrick J. Wong
3 siblings, 0 replies; 28+ messages in thread
From: shrikanth hegde @ 2023-02-17 11:30 UTC (permalink / raw)
To: djwong, dchinner; +Cc: linux-xfs, Srikar Dronamraju, ojaswin
On 2/17/23 4:45 PM, shrikanth hegde wrote:
> We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in
> one of our systems. System fails to come up. System was booting well
> with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel.
>
> Panic Log is below.
> [ 333.390539] ------------[ cut here ]------------
> [ 333.390552] WARNING: CPU: 56 PID: 12450 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
>
> we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
> as the bad commit.
> Short description of commit:
> commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad)
> Author: Dave Chinner <dchinner@redhat.com>
> Date: Thu Jul 14 11:42:39 2022 +1000
>
> xfs: refactor xlog_recover_process_iunlinks()
>
>
Tried one of the recent patch sent by Dave.
https://lore.kernel.org/all/20230118224505.1964941-1-david@fromorbit.com/
If the full series is applied, it panics upon booting. i.e same problem persists.
If only "[6/42] xfs: don't assert fail on transaction cancel with deferred ops"
is applied, then it doesnt panic at boot. It panics later, when doing a make.
A bit better than not booting. But still panics later.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-02-17 11:15 xfs: system fails to boot up due to Internal error xfs_trans_cancel shrikanth hegde
2023-02-17 11:25 ` shrikanth hegde
2023-02-17 11:30 ` shrikanth hegde
@ 2023-02-17 15:03 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-02-17 16:53 ` Darrick J. Wong
3 siblings, 0 replies; 28+ messages in thread
From: Linux regression tracking #adding (Thorsten Leemhuis) @ 2023-02-17 15:03 UTC (permalink / raw)
To: shrikanth hegde, djwong, dchinner
Cc: linux-xfs, Srikar Dronamraju, ojaswin, Linux kernel regressions list
[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]
[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]
On 17.02.23 12:15, shrikanth hegde wrote:
> We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in
> one of our systems. System fails to come up. System was booting well
> with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel.
>
> [...]
>
> we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
> as the bad commit.
Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:
#regzbot ^introduced 04755d2e5821
#regzbot title xfs: system fails to boot up due to Internal error
xfs_trans_cancel
#regzbot ignore-activity
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.
Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-02-17 11:15 xfs: system fails to boot up due to Internal error xfs_trans_cancel shrikanth hegde
` (2 preceding siblings ...)
2023-02-17 15:03 ` Linux regression tracking #adding (Thorsten Leemhuis)
@ 2023-02-17 16:53 ` Darrick J. Wong
2023-02-17 20:25 ` Dave Chinner
2023-02-18 7:17 ` shrikanth hegde
3 siblings, 2 replies; 28+ messages in thread
From: Darrick J. Wong @ 2023-02-17 16:53 UTC (permalink / raw)
To: shrikanth hegde; +Cc: dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On Fri, Feb 17, 2023 at 04:45:12PM +0530, shrikanth hegde wrote:
> We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in
> one of our systems. System fails to come up. System was booting well
> with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel.
>
> Panic Log is below.
> [ 333.390539] ------------[ cut here ]------------
> [ 333.390552] WARNING: CPU: 56 PID: 12450 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
Hmm, ok, so this is the same if (WARN_ON_ONCE(!ip || !ip->i_ino)) line
in xfs_iunlink_lookup that I've been bonking my head on the past
several days. 333 seconds uptime, so I guess this is a pretty recent
mount. You didn't post a full dmesg, so I can only assume there weren't
any *other* obvious complaints from XFS when the fs was mounted...
> [ 333.390615] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
> [ 333.390645] CPU: 56 PID: 12450 Comm: rm Not tainted 6.2.0-rc4ssh+ #4
> [ 333.390649] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> [ 333.390652] NIP: c0080000004bfa80 LR: c0080000004bfa4c CTR: c000000000ea28d0
> [ 333.390655] REGS: c0000000442bb8c0 TRAP: 0700 Not tainted (6.2.0-rc4ssh+)
> [ 333.390658] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24002842 XER: 00000000
> [ 333.390666] CFAR: c0080000004bfa54 IRQMASK: 0
> [ 333.390666] GPR00: c00000003b69c0c8 c0000000442bbb60 c008000000568300 0000000000000000
> [ 333.390666] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000004b27d78
> [ 333.390666] GPR08: 0000000000000000 c000000004b27e28 0000000000000000 fffffffffffffffd
> [ 333.390666] GPR12: 0000000000000040 c000004afecc5880 0000000106620918 0000000000000001
> [ 333.390666] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
> [ 333.390666] GPR20: 0000000106620e30 c0000000880ba938 0000000000200000 00000000002ec44d
> [ 333.390666] GPR24: 000000000008170d 000000000000000d c0000000519f4800 00000000002ec44d
> [ 333.390666] GPR28: c0000000880ba800 c00000003b69c000 c0000000833edd20 000000000008170d
> [ 333.390702] NIP [c0080000004bfa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
> [ 333.390756] LR [c0080000004bfa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
> [ 333.390810] Call Trace:
> [ 333.390811] [c0000000442bbb60] [c0000000833edd20] 0xc0000000833edd20 (unreliable)
> [ 333.390816] [c0000000442bbb80] [c0080000004c0094] xfs_iunlink+0x1bc/0x280 [xfs]
> [ 333.390869] [c0000000442bbc00] [c0080000004c3f84] xfs_remove+0x1dc/0x310 [xfs]
> [ 333.390922] [c0000000442bbc70] [c0080000004be180] xfs_vn_unlink+0x68/0xf0 [xfs]
> [ 333.390975] [c0000000442bbcd0] [c000000000576b24] vfs_unlink+0x1b4/0x3d0
...that trips when rm tries to remove a file, which means that the call
stack is
xfs_remove -> xfs_iunlink -> xfs_iunlink_insert_inode ->
xfs_iunlink_update_backref -> xfs_iunlink_lookup <kaboom>
It looks as though "rm foo" unlinked foo from the directory and was
trying to insert it at the head of one of the unlinked lists in the AGI
buffer. The AGI claims that the list points to an ondisk inode, so the
iunlink code tries to find the incore inode to update the incore list,
fails to find an incore inode, and this is the result...
> [ 333.390981] [c0000000442bbd20] [c00000000057e5d8] do_unlinkat+0x2b8/0x390
> [ 333.390985] [c0000000442bbde0] [c00000000057e708] sys_unlinkat+0x58/0xb0
> [ 333.390989] [c0000000442bbe10] [c0000000000335d0] system_call_exception+0x150/0x3b0
> [ 333.390994] [c0000000442bbe50] [c00000000000c554] system_call_common+0xf4/0x258
> [ 333.390999] --- interrupt: c00 at 0x7fffa47230a0
> [ 333.391001] NIP: 00007fffa47230a0 LR: 00000001066138ac CTR: 0000000000000000
> [ 333.391004] REGS: c0000000442bbe80 TRAP: 0c00 Not tainted (6.2.0-rc4ssh+)
> [ 333.391007] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 22002202 XER: 00000000
> [ 333.391016] IRQMASK: 0
> [ 333.391016] GPR00: 0000000000000124 00007fffdb9330b0 00007fffa4807300 0000000000000008
> [ 333.391016] GPR04: 000000010bd36f18 0000000000000000 0000000000000000 0000000000000003
> [ 333.391016] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> [ 333.391016] GPR12: 0000000000000000 00007fffa48ba340 0000000106620918 0000000000000001
> [ 333.391016] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
> [ 333.391016] GPR20: 0000000106620e30 0000000106620e00 0000000106620c40 0000000000000002
> [ 333.391016] GPR24: 0000000106620c38 00000001066208d8 0000000000000000 0000000106620d20
> [ 333.391016] GPR28: 00007fffdb933408 000000010bd24cec 00007fffdb933408 000000010bd36e10
> [ 333.391050] NIP [00007fffa47230a0] 0x7fffa47230a0
> [ 333.391052] LR [00000001066138ac] 0x1066138ac
> [ 333.391054] --- interrupt: c00
> [ 333.391056] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
> [ 333.391069] ---[ end trace 0000000000000000 ]---
> [ 333.391072] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_remove+0x1a0/0x310 [xfs]
> [ 333.391128] CPU: 56 PID: 12450 Comm: rm Tainted: G W 6.2.0-rc4ssh+ #4
> [ 333.391131] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> [ 333.391135] Call Trace:
> [ 333.391136] [c0000000442bbb10] [c000000000e84f4c] dump_stack_lvl+0x70/0xa4 (unreliable)
> [ 333.391142] [c0000000442bbb50] [c0080000004a6a84] xfs_error_report+0x5c/0x80 [xfs]
> [ 333.391194] [c0000000442bbbb0] [c0080000004d67b0] xfs_trans_cancel+0x178/0x1b0 [xfs]
> [ 333.391249] [c0000000442bbc00] [c0080000004c3f48] xfs_remove+0x1a0/0x310 [xfs]
> [ 333.391302] [c0000000442bbc70] [c0080000004be180] xfs_vn_unlink+0x68/0xf0 [xfs]
> [ 333.391355] [c0000000442bbcd0] [c000000000576b24] vfs_unlink+0x1b4/0x3d0
> [ 333.391359] [c0000000442bbd20] [c00000000057e5d8] do_unlinkat+0x2b8/0x390
> [ 333.391363] [c0000000442bbde0] [c00000000057e708] sys_unlinkat+0x58/0xb0
> [ 333.391367] [c0000000442bbe10] [c0000000000335d0] system_call_exception+0x150/0x3b0
> [ 333.391371] [c0000000442bbe50] [c00000000000c554] system_call_common+0xf4/0x258
> [ 333.391376] --- interrupt: c00 at 0x7fffa47230a0
> [ 333.391378] NIP: 00007fffa47230a0 LR: 00000001066138ac CTR: 0000000000000000
> [ 333.391381] REGS: c0000000442bbe80 TRAP: 0c00 Tainted: G W (6.2.0-rc4ssh+)
> [ 333.391385] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 22002202 XER: 00000000
> [ 333.391393] IRQMASK: 0
> [ 333.391393] GPR00: 0000000000000124 00007fffdb9330b0 00007fffa4807300 0000000000000008
> [ 333.391393] GPR04: 000000010bd36f18 0000000000000000 0000000000000000 0000000000000003
> [ 333.391393] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> [ 333.391393] GPR12: 0000000000000000 00007fffa48ba340 0000000106620918 0000000000000001
> [ 333.391393] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
> [ 333.391393] GPR20: 0000000106620e30 0000000106620e00 0000000106620c40 0000000000000002
> [ 333.391393] GPR24: 0000000106620c38 00000001066208d8 0000000000000000 0000000106620d20
> [ 333.391393] GPR28: 00007fffdb933408 000000010bd24cec 00007fffdb933408 000000010bd36e10
> [ 333.391427] NIP [00007fffa47230a0] 0x7fffa47230a0
> [ 333.391429] LR [00000001066138ac] 0x1066138ac
> [ 333.391431] --- interrupt: c00
> [ 333.394067] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
> [ 333.394125] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
>
>
>
> we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
> as the bad commit.
> Short description of commit:
> commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad)
> Author: Dave Chinner <dchinner@redhat.com>
> Date: Thu Jul 14 11:42:39 2022 +1000
>
> xfs: refactor xlog_recover_process_iunlinks()
...which was in the middle of the series that reworked thev mount time
iunlink clearing. Oddly, I don't spot any obvious errors in /that/
patch that didn't already exist. But this does make me wonder, does
xfs_repair -n have anything to say about unlinked or orphaned inodes?
The runtime code expects that every ondisk inode in an iunlink chain has
an incore inode that is linked (via i_{next,prev}_unlinked) to the other
incore inodes in that same chain. If this requirement is not met, then
the WARNings you see will trip, and the fs shuts down.
My hypothesis here is that one of the AGs has an unprocessed unlinked
list. At mount time, the ondisk log was clean, so mount time log
recovery didn't invoke xlog_recover_process_iunlinks, and the list was
not cleared. The mount code does not construct the incore unlinked list
from an existing ondisk iunlink list, hence the WARNing. Prior to 5.17,
we only manipulated the ondisk unlink list, and the code never noticed
or cared if there were mystery inodes in the list that never went away.
(Obviously, if something blew up earlier in dmesg, that would be
relevant here.)
It's possible that we could end up in this situation (clean log,
unlinked inodes) if a previous log recovery was only partially
successful at clearing the unlinked list, since all that code ignores
errors. If that happens, we ... succeed at mounting and clean the log.
If you're willing to patch your kernels, it would be interesting
to printk if the xfs_read_agi or the xlog_recover_iunlink_bucket calls
in xlog_recover_iunlink_ag returns an error code. It might be too late
to capture that, hence my suggestion of seeing if xfs_repair -n will
tell us anything else.
I've long thought that the iunlink recovery ought to complain loudly and
fail the mount if it can't clear all the unlinked files. Given the new
iunlink design, I think it's pretty much required now. The uglier piece
is that now we either (a) have to clear iunlinks at mount time
unconditionally as Eric has been saying for years; or (b) construct the
incore list at a convenient time so that the incore list always exists.
Thanks for the detailed report!
--D
>
> Git bisect log:
> git bisect start
> # good: [26291c54e111ff6ba87a164d85d4a4e134b7315c] Linux 5.17-rc2
> git bisect good 26291c54e111ff6ba87a164d85d4a4e134b7315c
> # bad: [4fe89d07dcc2804c8b562f6c7896a45643d34b2f] Linux 6.0
> git bisect bad 4fe89d07dcc2804c8b562f6c7896a45643d34b2f
> # good: [d7227785e384d4422b3ca189aa5bf19f462337cc] Merge tag 'sound-5.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
> git bisect good d7227785e384d4422b3ca189aa5bf19f462337cc
> # good: [526942b8134cc34d25d27f95dfff98b8ce2f6fcd] Merge tag 'ata-5.20-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
> git bisect good 526942b8134cc34d25d27f95dfff98b8ce2f6fcd
> # good: [328141e51e6fc79d21168bfd4e356dddc2ec7491] Merge tag 'mmc-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
> git bisect good 328141e51e6fc79d21168bfd4e356dddc2ec7491
> # bad: [eb555cb5b794f4e12a9897f3d46d5a72104cd4a7] Merge tag '5.20-rc-ksmbd-server-fixes' of git://git.samba.org/ksmbd
> git bisect bad eb555cb5b794f4e12a9897f3d46d5a72104cd4a7
> # bad: [f20c95b46b8fa3ad34b3ea2e134337f88591468b] Merge tag 'tpmdd-next-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd
> git bisect bad f20c95b46b8fa3ad34b3ea2e134337f88591468b
> # bad: [fad235ed4338749a66ddf32971d4042b9ef47f44] Merge tag 'arm-late-6.0' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
> git bisect bad fad235ed4338749a66ddf32971d4042b9ef47f44
> # good: [e495274793ea602415d050452088a496abcd9e6c] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
> git bisect good e495274793ea602415d050452088a496abcd9e6c
> # good: [9daee913dc8d15eb65e0ff560803ab1c28bb480b] Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
> git bisect good 9daee913dc8d15eb65e0ff560803ab1c28bb480b
> # bad: [29b1d469f3f6842ee4115f0b21f018fc44176468] Merge tag 'trace-rtla-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
> git bisect bad 29b1d469f3f6842ee4115f0b21f018fc44176468
> # good: [932b42c66cb5d0ca9800b128415b4ad6b1952b3e] xfs: replace XFS_IFORK_Q with a proper predicate function
> git bisect good 932b42c66cb5d0ca9800b128415b4ad6b1952b3e
> # bad: [35c5a09f5346e690df7ff2c9075853e340ee10b3] Merge tag 'xfs-buf-lockless-lookup-5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs into xfs-5.20-mergeB
> git bisect bad 35c5a09f5346e690df7ff2c9075853e340ee10b3
> # bad: [fad743d7cd8bd92d03c09e71f29eace860f50415] xfs: add log item precommit operation
> git bisect bad fad743d7cd8bd92d03c09e71f29eace860f50415
> # bad: [04755d2e5821b3afbaadd09fe5df58d04de36484] xfs: refactor xlog_recover_process_iunlinks()
> git bisect bad 04755d2e5821b3afbaadd09fe5df58d04de36484
> # good: [a4454cd69c66bf3e3bbda352b049732f836fc6b2] xfs: factor the xfs_iunlink functions
> git bisect good a4454cd69c66bf3e3bbda352b049732f836fc6b2
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [4fcc94d653270fcc7800dbaf3b11f78cb462b293] xfs: track the iunlink list pointer in the xfs_inode
>
>
> Please reach out, in case any more details are needed. sent with very limited
> knowledge of xfs system. these logs are from 5.19 kernel.
>
> # xfs_info /home
> meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=13107200 blks
> = sectsz=4096 attr=2, projid32bit=1
> = crc=1 finobt=1, sparse=1, rmapbt=0
> = reflink=1 bigtime=0 inobtcount=0
> data = bsize=4096 blocks=52428800, imaxpct=25
> = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0, ftype=1
> log =internal log bsize=4096 blocks=25600, version=2
> = sectsz=4096 sunit=1 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
> # xfs_info -V
> xfs_info version 5.0.0
>
> # uname -a
> 5.19.0-rc2
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-02-17 16:53 ` Darrick J. Wong
@ 2023-02-17 20:25 ` Dave Chinner
2023-02-18 7:17 ` shrikanth hegde
1 sibling, 0 replies; 28+ messages in thread
From: Dave Chinner @ 2023-02-17 20:25 UTC (permalink / raw)
To: Darrick J. Wong
Cc: shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On Fri, Feb 17, 2023 at 08:53:32AM -0800, Darrick J. Wong wrote:
> On Fri, Feb 17, 2023 at 04:45:12PM +0530, shrikanth hegde wrote:
> > We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in
> > one of our systems. System fails to come up. System was booting well
> > with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel.
> >
> > Panic Log is below.
> > [ 333.390539] ------------[ cut here ]------------
> > [ 333.390552] WARNING: CPU: 56 PID: 12450 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
>
> Hmm, ok, so this is the same if (WARN_ON_ONCE(!ip || !ip->i_ino)) line
> in xfs_iunlink_lookup that I've been bonking my head on the past
> several days. 333 seconds uptime, so I guess this is a pretty recent
> mount. You didn't post a full dmesg, so I can only assume there weren't
> any *other* obvious complaints from XFS when the fs was mounted...
>
> > [ 333.390615] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
> > [ 333.390645] CPU: 56 PID: 12450 Comm: rm Not tainted 6.2.0-rc4ssh+ #4
> > [ 333.390649] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> > [ 333.390652] NIP: c0080000004bfa80 LR: c0080000004bfa4c CTR: c000000000ea28d0
> > [ 333.390655] REGS: c0000000442bb8c0 TRAP: 0700 Not tainted (6.2.0-rc4ssh+)
> > [ 333.390658] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24002842 XER: 00000000
> > [ 333.390666] CFAR: c0080000004bfa54 IRQMASK: 0
> > [ 333.390666] GPR00: c00000003b69c0c8 c0000000442bbb60 c008000000568300 0000000000000000
> > [ 333.390666] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000004b27d78
> > [ 333.390666] GPR08: 0000000000000000 c000000004b27e28 0000000000000000 fffffffffffffffd
> > [ 333.390666] GPR12: 0000000000000040 c000004afecc5880 0000000106620918 0000000000000001
> > [ 333.390666] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
> > [ 333.390666] GPR20: 0000000106620e30 c0000000880ba938 0000000000200000 00000000002ec44d
> > [ 333.390666] GPR24: 000000000008170d 000000000000000d c0000000519f4800 00000000002ec44d
> > [ 333.390666] GPR28: c0000000880ba800 c00000003b69c000 c0000000833edd20 000000000008170d
> > [ 333.390702] NIP [c0080000004bfa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
> > [ 333.390756] LR [c0080000004bfa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
> > [ 333.390810] Call Trace:
> > [ 333.390811] [c0000000442bbb60] [c0000000833edd20] 0xc0000000833edd20 (unreliable)
> > [ 333.390816] [c0000000442bbb80] [c0080000004c0094] xfs_iunlink+0x1bc/0x280 [xfs]
> > [ 333.390869] [c0000000442bbc00] [c0080000004c3f84] xfs_remove+0x1dc/0x310 [xfs]
> > [ 333.390922] [c0000000442bbc70] [c0080000004be180] xfs_vn_unlink+0x68/0xf0 [xfs]
> > [ 333.390975] [c0000000442bbcd0] [c000000000576b24] vfs_unlink+0x1b4/0x3d0
>
> ...that trips when rm tries to remove a file, which means that the call
> stack is
>
> xfs_remove -> xfs_iunlink -> xfs_iunlink_insert_inode ->
> xfs_iunlink_update_backref -> xfs_iunlink_lookup <kaboom>
>
> It looks as though "rm foo" unlinked foo from the directory and was
> trying to insert it at the head of one of the unlinked lists in the AGI
> buffer. The AGI claims that the list points to an ondisk inode, so the
> iunlink code tries to find the incore inode to update the incore list,
> fails to find an incore inode, and this is the result...
This implies that unlinked inode recovery failed for some reason,
and we didn't clear the unlinked list from the AGI properly.
> > we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
> > as the bad commit.
> > Short description of commit:
> > commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad)
> > Author: Dave Chinner <dchinner@redhat.com>
> > Date: Thu Jul 14 11:42:39 2022 +1000
> >
> > xfs: refactor xlog_recover_process_iunlinks()
>
> ...which was in the middle of the series that reworked thev mount time
> iunlink clearing. Oddly, I don't spot any obvious errors in /that/
> patch that didn't already exist. But this does make me wonder, does
> xfs_repair -n have anything to say about unlinked or orphaned inodes?
>
> The runtime code expects that every ondisk inode in an iunlink chain has
> an incore inode that is linked (via i_{next,prev}_unlinked) to the other
> incore inodes in that same chain. If this requirement is not met, then
> the WARNings you see will trip, and the fs shuts down.
>
> My hypothesis here is that one of the AGs has an unprocessed unlinked
> list. At mount time, the ondisk log was clean, so mount time log
> recovery didn't invoke xlog_recover_process_iunlinks, and the list was
> not cleared. The mount code does not construct the incore unlinked list
> from an existing ondisk iunlink list, hence the WARNing. Prior to 5.17,
> we only manipulated the ondisk unlink list, and the code never noticed
> or cared if there were mystery inodes in the list that never went away.
Yup, that's what I'm thinking.
But, hmmm, why is xlog_recover_clear_agi_bucket() not actually
clearing the bucket head at that point?
Oh, because we don't (and never have) capture errors from inode
inactivation? Or maybe the filesystem has shut down due to the
unlink failure?
I'd love to know how the filesystem got to this state in the first
place, but at the moment I'll settle for a metadata of a broken
filesystem....
> (Obviously, if something blew up earlier in dmesg, that would be
> relevant here.)
>
> It's possible that we could end up in this situation (clean log,
> unlinked inodes) if a previous log recovery was only partially
> successful at clearing the unlinked list, since all that code ignores
> errors. If that happens, we ... succeed at mounting and clean the log.
>
> If you're willing to patch your kernels, it would be interesting
> to printk if the xfs_read_agi or the xlog_recover_iunlink_bucket calls
> in xlog_recover_iunlink_ag returns an error code. It might be too late
> to capture that, hence my suggestion of seeing if xfs_repair -n will
> tell us anything else.
>
> I've long thought that the iunlink recovery ought to complain loudly and
> fail the mount if it can't clear all the unlinked files. Given the new
> iunlink design, I think it's pretty much required now. The uglier piece
> is that now we either (a) have to clear iunlinks at mount time
> unconditionally as Eric has been saying for years; or (b) construct the
> incore list at a convenient time so that the incore list always exists.
Recovery does actually construct the incore list sufficient to
unlink it (i.e. that's what the next/prev reference looping does).
We could walk the entire list first and bring it into memory,
but the problem there, I think, is that we have to hold references
to all the inodes we bring into memory during recovery otherwise
they are immediately reclaimed once we drop the reference.
I suspect we need to work out why xlog_recover_clear_agi_bucket() is
not triggering and clearing the bucket on error, because that is
supposed to avoid this exact "could not process all unlinked inodes"
and it warns loudly when it triggers....
-Dave.
--
Dave Chinner
david@fromorbit.com
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-02-17 16:53 ` Darrick J. Wong
2023-02-17 20:25 ` Dave Chinner
@ 2023-02-18 7:17 ` shrikanth hegde
2023-02-22 16:41 ` Darrick J. Wong
1 sibling, 1 reply; 28+ messages in thread
From: shrikanth hegde @ 2023-02-18 7:17 UTC (permalink / raw)
To: Darrick J. Wong; +Cc: dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On 2/17/23 10:23 PM, Darrick J. Wong wrote:
> On Fri, Feb 17, 2023 at 04:45:12PM +0530, shrikanth hegde wrote:
>> We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in
>> one of our systems. System fails to come up. System was booting well
>> with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel.
>>
>> Panic Log is below.
>> [ 333.390539] ------------[ cut here ]------------
>> [ 333.390552] WARNING: CPU: 56 PID: 12450 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
>
> Hmm, ok, so this is the same if (WARN_ON_ONCE(!ip || !ip->i_ino)) line
> in xfs_iunlink_lookup that I've been bonking my head on the past
> several days. 333 seconds uptime, so I guess this is a pretty recent
> mount. You didn't post a full dmesg, so I can only assume there weren't
> any *other* obvious complaints from XFS when the fs was mounted...
>
Darrick, Dave. Thank you for taking a look at this. sorry i didnt paste the full log.
Please find the full dmesg below. it was kexec from 5.17-rc2 to 6.2-rc8
Starting Reboot via kexec...
[ 71.134231] printk: systemd-shutdow: 37 output lines suppressed due to ratelimiting
[ 71.158255] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 71.160419] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 71.214007] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 71.233182] systemd-shutdown[1]: Unmounting file systems.
[ 71.233845] [2287]: Remounting '/home' read-only in with options 'attr2,inode64,logbufs=8,logbsize=32k,noquota'.
[ 71.234873] [2288]: Unmounting '/home'.
[ 71.237859] XFS (nvme0n1p1): Unmounting Filesystem
[ 71.524111] [2289]: Remounting '/' read-only in with options 'attr2,inode64,logbufs=8,logbsize=32k,noquota'.
[ 71.810094] systemd-shutdown[1]: All filesystems unmounted.
[ 71.810103] systemd-shutdown[1]: Deactivating swaps.
[ 71.810121] systemd-shutdown[1]: All swaps deactivated. pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/li[ 71.810126] systemd-shutdown[1]: Detaching loop devices.'
[ 71.810227] systemd-shutdown[1]: All loop devices detached.
[ 71.810232] systemd-shutdown[1]: Detaching DM devices.
[ 71.932097] printk: shutdown: 8 output lines suppressed due to ratelimiting
[ 71.954484] dracut Warning: Killing all remaining processes
dracut Warning: Killing all remaining processes
[ 72.001360] XFS (dm-0): Unmounting Filesystem
[ 72.393816] dracut Warning: Unmounted /oldroot.
[ 72.409893] dracut: Disassembling device-mapper devices
[ 72.527853] Removing IBM Power 842 compression device
[ 78.084038] kexec_core: Starting new kernel
[ 78.104094] kexec: waiting for cpu 26 (physical 26) to enter 1 state
[ 78.104102] kexec: waiting for cpu 87 (physical 87) to enter 1 state
[ 78.104109] kexec: waiting for cpu 1 (physical 1) to enter 2 state
[ 78.104248] kexec: waiting for cpu 2 (physical 2) to enter 2 state
[ 78.104275] kexec: waiting for cpu 3 (physical 3) to enter 2 state
[ 78.104289] kexec: waiting for cpu 4 (physical 4) to enter 2 state
[ 78.104303] kexec: waiting for cpu 5 (physical 5) to enter 2 state
[ 78.104315] kexec: waiting for cpu 8 (physical 8) to enter 2 state
[ 78.104352] kexec: waiting for cpu 48 (physical 48) to enter 2 state
[ 78.104357] kexec: waiting for cpu 49 (physical 49) to enter 2 state
[ 78.278072] kexec: Starting switchover sequence.
I'm in purgatory
[ 0.000000] radix-mmu: Page sizes from device-tree:
[ 0.000000] radix-mmu: Page size shift = 12 AP=0x0
[ 0.000000] radix-mmu: Page size shift = 16 AP=0x5
[ 0.000000] radix-mmu: Page size shift = 21 AP=0x1
[ 0.000000] radix-mmu: Page size shift = 30 AP=0x2
[ 0.000000] Activating Kernel Userspace Access Prevention
[ 0.000000] Activating Kernel Userspace Execution Prevention
[ 0.000000] radix-mmu: Mapped 0x0000000000000000-0x0000000002600000 with 2.00 MiB pages (exec)
[ 0.000000] radix-mmu: Mapped 0x0000000002600000-0x0000004b00000000 with 2.00 MiB pages
[ 0.000000] lpar: Using radix MMU under hypervisor
[ 0.000000] Linux version 6.2.0-rc8ssh (root@ltcden3-lp1.aus.stglabs.ibm.com) (gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10), GNU ld version 2.30-113.el8) #35 SMP Sat Feb 18 00:41:56 EST 2023
[ 0.000000] Found initrd at 0xc0000000061d0000:0xc00000000ac38d3b
[ 0.000000] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
[ 0.000000] printk: bootconsole [udbg0] enabled
[ 0.000000] Partition configured for 96 cpus.
[ 0.000000] CPU maps initialized for 8 threads per core
[ 0.000000] numa: Partition configured for 32 NUMA nodes.
[ 0.000000] -----------------------------------------------------
[ 0.000000] phys_mem_size = 0x4b00000000
[ 0.000000] dcache_bsize = 0x80
[ 0.000000] icache_bsize = 0x80
[ 0.000000] cpu_features = 0x000c00eb8f5f9187
[ 0.000000] possible = 0x000ffbfbcf5fb187
[ 0.000000] always = 0x0000000380008181
[ 0.000000] cpu_user_features = 0xdc0065c2 0xaef60000
[ 0.000000] mmu_features = 0xbc007641
[ 0.000000] firmware_features = 0x000005bfc55bfc57
[ 0.000000] vmalloc start = 0xc008000000000000
[ 0.000000] IO start = 0xc00a000000000000
[ 0.000000] vmemmap start = 0xc00c000000000000
[ 0.000000] -----------------------------------------------------
[ 0.000000] numa: NODE_DATA [mem 0x4afe663780-0x4afe66aeff]
[ 0.000000] rfi-flush: fallback displacement flush available
[ 0.000000] count-cache-flush: hardware flush enabled.
[ 0.000000] link-stack-flush: software flush enabled.
[ 0.000000] stf-barrier: eieio barrier available
[ 0.000000] PPC64 nvram contains 15360 bytes
[ 0.000000] barrier-nospec: using ORI speculation barrier
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000000000000-0x0000004affffffff]
[ 0.000000] Device empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 2: [mem 0x0000000000000000-0x0000004affffffff]
[ 0.000000] Initializing node 0 as memoryless
[ 0.000000] Initmem setup node 0 as memoryless
[ 0.000000] Initializing node 1 as memoryless
[ 0.000000] Initmem setup node 1 as memoryless
[ 0.000000] Initmem setup node 2 [mem 0x0000000000000000-0x0000004affffffff]
[ 0.000000] Initializing node 3 as memoryless
[ 0.000000] Initmem setup node 3 as memoryless
[ 0.000000] Initializing node 4 as memoryless
[ 0.000000] Initmem setup node 4 as memoryless
[ 0.000000] Initializing node 5 as memoryless
[ 0.000000] Initmem setup node 5 as memoryless
[ 0.000000] Initializing node 6 as memoryless
[ 0.000000] Initmem setup node 6 as memoryless
[ 0.000000] Initializing node 7 as memoryless
[ 0.000000] Initmem setup node 7 as memoryless
[ 0.000000] Initializing node 8 as memoryless
[ 0.000000] Initmem setup node 8 as memoryless
[ 0.000000] Initializing node 9 as memoryless
[ 0.000000] Initmem setup node 9 as memoryless
[ 0.000000] Initializing node 10 as memoryless
[ 0.000000] Initmem setup node 10 as memoryless
[ 0.000000] Initializing node 11 as memoryless
[ 0.000000] Initmem setup node 11 as memoryless
[ 0.000000] Initializing node 12 as memoryless
[ 0.000000] Initmem setup node 12 as memoryless
[ 0.000000] Initializing node 13 as memoryless
[ 0.000000] Initmem setup node 13 as memoryless
[ 0.000000] Initializing node 14 as memoryless
[ 0.000000] Initmem setup node 14 as memoryless
[ 0.000000] Initializing node 15 as memoryless
[ 0.000000] Initmem setup node 15 as memoryless
[ 0.000000] Initializing node 16 as memoryless
[ 0.000000] Initmem setup node 16 as memoryless
[ 0.000000] Initializing node 17 as memoryless
[ 0.000000] Initmem setup node 17 as memoryless
[ 0.000000] Initializing node 18 as memoryless
[ 0.000000] Initmem setup node 18 as memoryless
[ 0.000000] Initializing node 19 as memoryless
[ 0.000000] Initmem setup node 19 as memoryless
[ 0.000000] Initializing node 20 as memoryless
[ 0.000000] Initmem setup node 20 as memoryless
[ 0.000000] Initializing node 21 as memoryless
[ 0.000000] Initmem setup node 21 as memoryless
[ 0.000000] Initializing node 22 as memoryless
[ 0.000000] Initmem setup node 22 as memoryless
[ 0.000000] Initializing node 23 as memoryless
[ 0.000000] Initmem setup node 23 as memoryless
[ 0.000000] Initializing node 24 as memoryless
[ 0.000000] Initmem setup node 24 as memoryless
[ 0.000000] Initializing node 25 as memoryless
[ 0.000000] Initmem setup node 25 as memoryless
[ 0.000000] Initializing node 26 as memoryless
[ 0.000000] Initmem setup node 26 as memoryless
[ 0.000000] Initializing node 27 as memoryless
[ 0.000000] Initmem setup node 27 as memoryless
[ 0.000000] Initializing node 28 as memoryless
[ 0.000000] Initmem setup node 28 as memoryless
[ 0.000000] Initializing node 29 as memoryless
[ 0.000000] Initmem setup node 29 as memoryless
[ 0.000000] Initializing node 30 as memoryless
[ 0.000000] Initmem setup node 30 as memoryless
[ 0.000000] Initializing node 31 as memoryless
[ 0.000000] Initmem setup node 31 as memoryless
[ 0.000000] percpu: Embedded 10 pages/cpu s601512 r0 d53848 u655360
[ 0.000000] Fallback order for Node 0: 0 2
[ 0.000000] Fallback order for Node 1: 1 2
[ 0.000000] Fallback order for Node 2: 2
[ 0.000000] Fallback order for Node 3: 3 2
[ 0.000000] Fallback order for Node 4: 4 2
[ 0.000000] Fallback order for Node 5: 5 2
[ 0.000000] Fallback order for Node 6: 6 2
[ 0.000000] Fallback order for Node 7: 7 2
[ 0.000000] Fallback order for Node 8: 8 2
[ 0.000000] Fallback order for Node 9: 9 2
[ 0.000000] Fallback order for Node 10: 10 2
[ 0.000000] Fallback order for Node 11: 11 2
[ 0.000000] Fallback order for Node 12: 12 2
[ 0.000000] Fallback order for Node 13: 13 2
[ 0.000000] Fallback order for Node 14: 14 2
[ 0.000000] Fallback order for Node 15: 15 2
[ 0.000000] Fallback order for Node 16: 16 2
[ 0.000000] Fallback order for Node 17: 17 2
[ 0.000000] Fallback order for Node 18: 18 2
[ 0.000000] Fallback order for Node 19: 19 2
[ 0.000000] Fallback order for Node 20: 20 2
[ 0.000000] Fallback order for Node 21: 21 2
[ 0.000000] Fallback order for Node 22: 22 2
[ 0.000000] Fallback order for Node 23: 23 2
[ 0.000000] Fallback order for Node 24: 24 2
[ 0.000000] Fallback order for Node 25: 25 2
[ 0.000000] Fallback order for Node 26: 26 2
[ 0.000000] Fallback order for Node 27: 27 2
[ 0.000000] Fallback order for Node 28: 28 2
[ 0.000000] Fallback order for Node 29: 29 2
[ 0.000000] Fallback order for Node 30: 30 2
[ 0.000000] Fallback order for Node 31: 31 2
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 4910400
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: root=/dev/mapper/rhel_ltcden3--lp1-root
[ 0.000000] random: crng init done
[ 0.000000] Dentry cache hash table entries: 16777216 (order: 11, 134217728 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 8388608 (order: 10, 67108864 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 313817216K/314572800K available (15168K kernel code, 5632K rwdata, 17600K rodata, 5440K init, 2721K bss, 755584K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=96, Nodes=32
[ 0.000000] ftrace: allocating 38156 entries in 14 pages
[ 0.000000] ftrace: allocated 14 pages with 3 groups
[ 0.000000] trace event string verifier disabled
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=2048 to nr_cpu_ids=96.
[ 0.000000] Rude variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=96
[ 0.000000] NR_IRQS: 512, nr_irqs: 512, preallocated irqs: 16
[ 0.000000] xive: Using IRQ range [400000-40005f]
[ 0.000000] xive: Interrupt handling initialized with spapr backend
[ 0.000000] xive: Using priority 7 for all interrupts
[ 0.000000] xive: Using 64kB queues
[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000001] time_init: 56 bit decrementer (max: 7fffffffffffff)
[ 0.000021] clocksource: timebase: mask: 0xffffffffffffffff max_cycles: 0x761537d007, max_idle_ns: 440795202126 ns
[ 0.000055] clocksource: timebase mult[1f40000] shift[24] registered
[ 0.000233] Console: colour dummy device 80x25
[ 0.000252] printk: console [hvc0] enabled
[ 0.000252] printk: console [hvc0] enabled
[ 0.000269] printk: bootconsole [udbg0] disabled
[ 0.000269] printk: bootconsole [udbg0] disabled
[ 0.000360] pid_max: default: 98304 minimum: 768
[ 0.000481] LSM: initializing lsm=capability,yama,integrity,selinux,bpf
[ 0.000550] Yama: becoming mindful.
[ 0.000565] SELinux: Initializing.
[ 0.000568] SELinux: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE is non-zero. This is deprecated and will be rejected in a future kernel release.
[ 0.000573] SELinux: https://github.com/SELinuxProject/selinux-kernel/wiki/DEPRECATE-checkreqprot
[ 0.000747] LSM support for eBPF active
[ 0.000929] Mount-cache hash table entries: 262144 (order: 5, 2097152 bytes, linear)
[ 0.001056] Mountpoint-cache hash table entries: 262144 (order: 5, 2097152 bytes, linear)
[ 0.003430] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.003454] cblist_init_generic: Setting shift to 7 and lim to 1.
[ 0.003486] cblist_init_generic: Setting shift to 7 and lim to 1.
[ 0.003507] POWER10 performance monitor hardware support registered
[ 0.003537] rcu: Hierarchical SRCU implementation.
[ 0.003540] rcu: Max phase no-delay instances is 1000.
[ 0.004445] smp: Bringing up secondary CPUs ...
[ 0.022208] smp: Brought up 1 node, 96 CPUs
[ 0.022218] numa: Node 2 CPUs: 0-95
[ 0.022222] Big cores detected but using small core scheduling
[ 0.033289] devtmpfs: initialized
[ 0.042965] PCI host bridge /pci@800000020000019 ranges:
[ 0.042984] MEM 0x0000040080000000..0x00000400feffffff -> 0x0000000080000000
[ 0.042988] MEM 0x0000044000000000..0x0000047fffffffff -> 0x0006204000000000
[ 0.043060] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.043066] futex hash table entries: 32768 (order: 6, 4194304 bytes, linear)
[ 0.043643] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.043801] audit: initializing netlink subsys (disabled)
[ 0.043903] audit: type=2000 audit(1676701683.040:1): state=initialized audit_enabled=0 res=1
[ 0.043954] thermal_sys: Registered thermal governor 'fair_share'
[ 0.043955] thermal_sys: Registered thermal governor 'step_wise'
[ 0.044007] cpuidle: using governor menu
[ 0.044306] pstore: Registered nvram as persistent store backend
[ 0.044682] EEH: pSeries platform initialized
[ 0.055324] PCI: Probing PCI hardware
[ 0.055372] PCI host bridge to bus 0019:01
[ 0.055376] pci_bus 0019:01: root bus resource [mem 0x40080000000-0x400feffffff] (bus address [0x80000000-0xfeffffff])
[ 0.055381] pci_bus 0019:01: root bus resource [mem 0x44000000000-0x47fffffffff 64bit] (bus address [0x6204000000000-0x6207fffffffff])
[ 0.055386] pci_bus 0019:01: root bus resource [bus 01-ff]
[ 0.056001] pci 0019:01:00.0: No hypervisor support for SR-IOV on this device, IOV BARs disabled.
[ 0.064978] IOMMU table initialized, virtual merging enabled
[ 0.065086] pci 0019:01:00.0: Adding to iommu group 0
[ 0.066308] EEH: Capable adapter found: recovery enabled.
[ 0.066550] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
[ 0.066812] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.066817] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[ 0.066821] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.066824] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[ 0.085068] cryptd: max_cpu_qlen set to 1000
[ 0.085368] iommu: Default domain type: Translated
[ 0.085371] iommu: DMA domain TLB invalidation policy: strict mode
[ 0.085491] SCSI subsystem initialized
[ 0.085517] usbcore: registered new interface driver usbfs
[ 0.085523] usbcore: registered new interface driver hub
[ 0.085542] usbcore: registered new device driver usb
[ 0.085563] pps_core: LinuxPPS API ver. 1 registered
[ 0.085565] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.085569] PTP clock support registered
[ 0.085628] EDAC MC: Ver: 3.0.0
[ 0.085885] NetLabel: Initializing
[ 0.085887] NetLabel: domain hash size = 128
[ 0.085889] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.085903] NetLabel: unlabeled traffic allowed by default
[ 0.085956] vgaarb: loaded
[ 0.086157] clocksource: Switched to clocksource timebase
[ 0.086451] VFS: Disk quotas dquot_6.6.0
[ 0.086480] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)
[ 0.088080] NET: Registered PF_INET protocol family
[ 0.088237] IP idents hash table entries: 262144 (order: 5, 2097152 bytes, linear)
[ 0.091345] tcp_listen_portaddr_hash hash table entries: 65536 (order: 4, 1048576 bytes, linear)
[ 0.091454] Table-perturb hash table entries: 65536 (order: 2, 262144 bytes, linear)
[ 0.091480] TCP established hash table entries: 524288 (order: 6, 4194304 bytes, linear)
[ 0.092201] TCP bind hash table entries: 65536 (order: 5, 2097152 bytes, linear)
[ 0.092386] TCP: Hash tables configured (established 524288 bind 65536)
[ 0.092708] MPTCP token hash table entries: 65536 (order: 4, 1572864 bytes, linear)
[ 0.092826] UDP hash table entries: 65536 (order: 5, 2097152 bytes, linear)
[ 0.093046] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes, linear)
[ 0.093402] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.093413] NET: Registered PF_XDP protocol family
[ 0.093509] PCI: CLS 128 bytes, default 128
[ 0.093638] Unpacking initramfs...
[ 0.094862] vio_register_device_node: node lid missing 'reg'
[ 0.103665] vas: GZIP feature is available
[ 0.104512] hv-24x7: read 548 catalog entries, created 387 event attrs (0 failures), 387 descs
[ 0.108478] Initialise system trusted keyrings
[ 0.108493] Key type blacklist registered
[ 0.108560] workingset: timestamp_bits=38 max_order=23 bucket_order=0
[ 0.108587] zbud: loaded
[ 0.108988] integrity: Platform Keyring initialized
[ 0.119068] NET: Registered PF_ALG protocol family
[ 0.119083] Key type asymmetric registered
[ 0.119086] Asymmetric key parser 'x509' registered
[ 0.119120] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[ 0.119182] io scheduler mq-deadline registered
[ 0.119185] io scheduler kyber registered
[ 0.119198] io scheduler bfq registered
[ 0.120970] atomic64_test: passed
[ 0.121210] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 0.121214] PowerPC PowerNV PCI Hotplug Driver version: 0.1
[ 0.121532] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.121728] Non-volatile memory driver v1.3
[ 0.122174] rdac: device handler registered
[ 0.122215] hp_sw: device handler registered
[ 0.122218] emc: device handler registered
[ 0.122260] alua: device handler registered
[ 0.122450] usbcore: registered new interface driver usbserial_generic
[ 0.122457] usbserial: USB Serial support registered for generic
[ 0.122529] mousedev: PS/2 mouse device common for all mice
[ 0.122644] rtc-generic rtc-generic: registered as rtc0
[ 0.122676] rtc-generic rtc-generic: setting system clock to 2023-02-18T06:28:03 UTC (1676701683)
[ 0.122755] xcede: xcede_record_size = 10
[ 0.122758] xcede: Record 0 : hint = 1, latency = 0x1800 tb ticks, Wake-on-irq = 1
[ 0.122765] xcede: Record 1 : hint = 2, latency = 0x3c00 tb ticks, Wake-on-irq = 0
[ 0.122769] cpuidle: Skipping the 2 Extended CEDE idle states
[ 0.122771] cpuidle: Fixed up CEDE exit latency to 12 us
[ 0.123865] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sync_size new:65536 old:0
[ 0.123871] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sync_sg new:510 old:0
[ 0.123875] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sg_len new:4080 old:0
[ 0.124018] hid: raw HID events driver (C) Jiri Kosina
[ 0.124042] usbcore: registered new interface driver usbhid
[ 0.124048] usbhid: USB HID core driver
[ 0.124069] drop_monitor: Initializing network drop monitor service
[ 0.134168] Initializing XFRM netlink socket
[ 0.134234] NET: Registered PF_INET6 protocol family
[ 0.134747] Segment Routing with IPv6
[ 0.134756] In-situ OAM (IOAM) with IPv6
[ 0.134776] NET: Registered PF_PACKET protocol family
[ 0.134817] mpls_gso: MPLS GSO support
[ 0.134836] secvar-sysfs: secvar: failed to retrieve secvar operations.
[ 0.139134] registered taskstats version 1
[ 0.140964] Loading compiled-in X.509 certificates
[ 0.156881] Loaded X.509 cert 'Build time autogenerated kernel key: 7b04a1cdeda81c05f7a701657946db5548da6201'
[ 0.157494] zswap: loaded using pool lzo/zbud
[ 0.160050] page_owner is disabled
[ 0.160226] pstore: Using crash dump compression: deflate
[ 0.972073] Freeing initrd memory: 76160K
[ 0.974020] Key type encrypted registered
[ 0.974056] Secure boot mode disabled
[ 0.974060] ima: No TPM chip found, activating TPM-bypass!
[ 0.974067] Loading compiled-in module X.509 certificates
[ 0.974567] Loaded X.509 cert 'Build time autogenerated kernel key: 7b04a1cdeda81c05f7a701657946db5548da6201'
[ 0.974571] ima: Allocated hash algorithm: sha256
[ 0.974598] Secure boot mode disabled
[ 0.974615] Trusted boot mode disabled
[ 0.974617] ima: No architecture policies found
[ 0.974629] evm: Initialising EVM extended attributes:
[ 0.974631] evm: security.selinux
[ 0.974633] evm: security.SMACK64 (disabled)
[ 0.974635] evm: security.SMACK64EXEC (disabled)
[ 0.974637] evm: security.SMACK64TRANSMUTE (disabled)
[ 0.974639] evm: security.SMACK64MMAP (disabled)
[ 0.974641] evm: security.apparmor (disabled)
[ 0.974642] evm: security.ima
[ 0.974644] evm: security.capability
[ 0.974646] evm: HMAC attrs: 0x1
[ 0.974676] alg: No test for 842 (842-nx)
[ 0.982519] Freeing unused kernel image (initmem) memory: 5440K
[ 1.086157] Run /init as init process
[ 1.092664] systemd[1]: systemd 239 (239-58.el8) running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy)
[ 1.092708] systemd[1]: Detected virtualization powervm.
[ 1.092714] systemd[1]: Detected architecture ppc64-le.
[ 1.092718] systemd[1]: Running in initial RAM disk.
Welcome to Red Hat Enterprise Linux 8.6 (Ootpa) dracut-049-201.git20220131.el8 (Initramfs)!
[ 1.246394] systemd[1]: Set hostname to <ltcden3-lp1.aus.stglabs.ibm.com>.
[ 1.321102] systemd[1]: Listening on Journal Socket.
[ OK ] Listening on Journal Socket.
[ 1.322421] systemd[1]: Started Hardware RNG Entropy Gatherer Daemon.
[ OK ] Started Hardware RNG Entropy Gatherer Daemon.
[ 1.323252] systemd[1]: Starting Create list of required static device nodes for the current kernel...
Starting Create list of required st…ce nodes for the current kernel...
[ 1.323333] systemd[1]: Reached target Local File Systems.
[ OK ] Reached target Local File Systems.
[ 1.324085] systemd[1]: Started Memstrack Anylazing Service.
[ OK ] Started Memstrack Anylazing Service.
[ OK ] Reached target Slices.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Listening on Journal Socket (/dev/log).
Starting Journal Service...
Starting Create Volatile Files and Directories...
[ OK ] Reached target Swap.
[ OK ] Reached target Timers.
Starting Setup Virtual Console...
Starting Load Kernel Modules...
[ OK ] Listening on udev Control Socket.
[ OK ] Reached target Sockets.
[ OK ] Started Create list of required sta…vice nodes for the current kernel.
[ OK ] Started Create Volatile Files and Directories.
Starting Create Static Device Nodes in /dev...
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
Starting Apply Kernel Variables...
[ OK ] Started Create Static Device Nodes in /dev.
[ OK ] Started Apply Kernel Variables.
[ OK ] Started Journal Service.
[ OK ] Started Setup Virtual Console.
Starting dracut cmdline hook...
[ OK ] Started dracut cmdline hook.
Starting dracut pre-udev hook...
[ 1.477216] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[ 1.477252] device-mapper: uevent: version 1.0.3
[ 1.477339] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[ OK ] Started dracut pre-udev hook.
Starting udev Kernel Device Manager...
[ OK ] Started udev Kernel Device Manager.
Starting udev Coldplug all Devices...
Mounting Kernel Configuration File System...
[ OK ] Mounted Kernel Configuration File System.
[ 1.651355] synth uevent: /devices/vio: failed to send uevent
[ 1.651365] vio vio: uevent: failed to send synthetic uevent: -19
[ 1.651402] synth uevent: /devices/vio/4000: failed to send uevent
[ 1.651406] vio 4000: uevent: failed to send synthetic uevent: -19
[ 1.651415] synth uevent: /devices/vio/4001: failed to send uevent
[ 1.651418] vio 4001: uevent: failed to send synthetic uevent: -19
[ 1.651428] synth uevent: /devices/vio/4002: failed to send uevent
[ 1.651431] vio 4002: uevent: failed to send synthetic uevent: -19
[ 1.651441] synth uevent: /devices/vio/4004: failed to send uevent
[ 1.651444] vio 4004: uevent: failed to send synthetic uevent: -19
[ OK ] Started udev Coldplug all Devices.
[ OK ] Reached target System Initialization.
Starting Show Plymouth Boot Screen...
Starting dracut initqueue hook...
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Started Forward Password Requests to Plymouth Directory Watch.
[ OK ] Reached target Paths.
[ OK ] Reached target Basic System.
[ 1.709851] ibmveth 30000002 net0: renamed from eth0
[ 1.712196] nvme nvme0: pci function 0019:01:00.0
[ 1.714161] ibmvscsi 30000065: SRP_VERSION: 16.a
[ 1.714223] ibmvscsi 30000065: Maximum ID: 64 Maximum LUN: 32 Maximum Channel: 3
[ 1.714227] scsi host0: IBM POWER Virtual SCSI Adapter 1.5.9
[ 1.714365] ibmvscsi 30000065: partner initialization complete
[ 1.714391] ibmvscsi 30000065: host srp version: 16.a, host partition ltcden3-vios1 (100), OS 3, max io 524288
[ 1.714421] ibmvscsi 30000065: Client reserve enabled
[ 1.714426] ibmvscsi 30000065: sent SRP login
[ 1.714448] ibmvscsi 30000065: SRP_LOGIN succeeded
[ 1.721611] nvme nvme0: Shutdown timeout set to 8 seconds
[ 1.737117] scsi 0:0:1:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
[ 1.738038] scsi 0:0:2:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
[ 1.738364] scsi 0:0:3:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
[ 1.750754] nvme nvme0: 32/0/0 default/read/poll queues
[ 1.754482] nvme0n1: p1 p2 p3
[ 1.772868] scsi 0:0:1:0: Attached scsi generic sg0 type 0
[ 1.772898] scsi 0:0:2:0: Attached scsi generic sg1 type 0
[ 1.772920] scsi 0:0:3:0: Attached scsi generic sg2 type 0
[ 1.794722] sd 0:0:2:0: [sda] 629145600 512-byte logical blocks: (322 GB/300 GiB)
[ 1.794757] sd 0:0:2:0: [sda] Write Protect is off
[ 1.794758] sd 0:0:1:0: [sdb] 209715200 512-byte logical blocks: (107 GB/100 GiB)
[ 1.794790] sd 0:0:2:0: [sda] Cache data unavailable
[ 1.794792] sd 0:0:1:0: [sdb] Write Protect is off
[ 1.794796] sd 0:0:2:0: [sda] Assuming drive cache: write through
[ 1.794826] sd 0:0:1:0: [sdb] Cache data unavailable
[ 1.794829] sd 0:0:1:0: [sdb] Assuming drive cache: write through
[ 1.794943] sd 0:0:3:0: [sdc] 91750400 4096-byte logical blocks: (376 GB/350 GiB)
[ 1.794979] sd 0:0:3:0: [sdc] Write Protect is off
[ 1.795008] sd 0:0:3:0: [sdc] Cache data unavailable
[ 1.795011] sd 0:0:3:0: [sdc] Assuming drive cache: write through
[ 1.796625] sdb: sdb1 sdb2 sdb3
[ 1.796717] sdc: sdc1
[ 1.796720] sda: sda1 sda2
[ 1.796752] sd 0:0:1:0: [sdb] Attached SCSI disk
[ 1.796820] sd 0:0:3:0: [sdc] Attached SCSI disk
[ 1.796841] sd 0:0:2:0: [sda] Attached SCSI disk
[ OK ] Found device /dev/mapper/rhel_ltcden3--lp1-root.
[ OK ] Reached target Initrd Root Device.
[ OK ] Started dracut initqueue hook.
Starting File System Check on /dev/mapper/rhel_ltcden3--lp1-root...
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
[ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
Mounting /sysroot...
[ 3.060638] SGI XFS with ACLs, security attributes, quota, no debug enabled
[ 3.062369] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
[ 3.109076] XFS (dm-0): Ending clean mount
[ OK ] Mounted /sysroot.
[ OK ] Reached target Initrd Root File System.
Starting Reload Configuration from the Real Root...
[ OK ] Started Reload Configuration from the Real Root.
[ OK ] Reached target Initrd File Systems.
[ OK ] Reached target Initrd Default Target.
Starting dracut pre-pivot and cleanup hook...
[ OK ] Started dracut pre-pivot and cleanup hook.
Starting Cleaning Up and Shutting Down Daemons...
[ OK ] Stopped dracut pre-pivot and cleanup hook.
[ OK ] Stopped target Remote File Systems.
[ OK ] Stopped target Initrd Default Target.
[ OK ] Stopped target Timers.
[ OK ] Stopped target Initrd Root Device.
[ OK ] Stopped target Remote File Systems (Pre).
[ OK ] Stopped dracut initqueue hook.
Starting Setup Virtual Console...
[ OK ] Stopped target Basic System.
[ OK ] Stopped target System Initialization.
[ OK ] Stopped Create Volatile Files and Directories.
[ OK ] Stopped Apply Kernel Variables.
[ OK ] Stopped udev Coldplug all Devices.
Stopping udev Kernel Device Manager...
[ OK ] Stopped target Swap.
[ OK ] Stopped target Paths.
[ OK ] Stopped target Sockets.
[ OK ] Stopped target Slices.
Starting Plymouth switch root service...
[ OK ] Stopped target Local File Systems.
[ OK ] Started Cleaning Up and Shutting Down Daemons.
[ OK ] Started Plymouth switch root service.
[ OK ] Started Setup Virtual Console.
[ OK ] Stopped udev Kernel Device Manager.
[ OK ] Stopped Create Static Device Nodes in /dev.
[ OK ] Stopped Create list of required sta…vice nodes for the current kernel.
Stopping Hardware RNG Entropy Gatherer Daemon...
[ OK ] Stopped dracut pre-udev hook.
[ OK ] Stopped dracut cmdline hook.
[ OK ] Closed udev Control Socket.
[ OK ] Closed udev Kernel Socket.
Starting Cleanup udevd DB...
[ OK ] Stopped Hardware RNG Entropy Gatherer Daemon.
[ OK ] Started Cleanup udevd DB.
[ OK ] Reached target Switch Root.
Starting Switch Root...
[ 3.449370] printk: systemd: 22 output lines suppressed due to ratelimiting
[ 3.593463] SELinux: Runtime disable is deprecated, use selinux=0 on the kernel cmdline.
[ 3.593471] SELinux: https://github.com/SELinuxProject/selinux-kernel/wiki/DEPRECATE-runtime-disable
[ 19.036134] SELinux: Disabled at runtime.
[ 19.196154] audit: type=1404 audit(1676701702.570:2): enforcing=0 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=0 old-enabled=1 lsm=selinux res=1
[ 19.201608] systemd[1]: systemd 239 (239-58.el8) running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy)
[ 19.201637] systemd[1]: Detected virtualization powervm.
[ 19.201642] systemd[1]: Detected architecture ppc64-le.
Welcome to Red Hat Enterprise Linux 8.6 (Ootpa)!
[ 19.202637] systemd[1]: Set hostname to <ltcden3-lp1.aus.stglabs.ibm.com>.
[ 21.777702] systemd[1]: systemd-journald.service: Succeeded.
[ 21.778191] systemd[1]: initrd-switch-root.service: Succeeded.
[ 21.778387] systemd[1]: Stopped Switch Root.
[ OK ] Stopped Switch Root.
[ 21.778748] systemd[1]: systemd-journald.service: Service has no hold-off time (RestartSec=0), scheduling restart.
[ 21.778795] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
[ 21.778847] systemd[1]: Stopped Journal Service.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[ OK ] Stopped Plymouth switch root service.
[ OK ] Stopped target Switch Root.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Listening on initctl Compatibility Named Pipe.
[ OK ] Listening on Process Core Dump Socket.
Mounting Huge Pages File System...
Starting Load Kernel Modules...
Starting Read and set NIS domainname from /etc/sysconfig/network...
Activating swap /dev/mapper/rhel_ltcden3--lp1-swap...
[ OK ] Created slice system-serial\x2dgetty.slice.
[ OK ] Created slice system-getty.slice.
Starting Create list of required st…ce nodes for the current kernel...
[ OK ] Created slice User and Session Slice.
[ OK ] Reached target Slices.
[ OK ] Listening on RPCbind Server Activation Socket.
[ OK ] Reached target RPC Port Mapper.
Mounting POSIX Message Queue File System...
[ OK ] Stopped File System Check on Root Device.
Starting Remount Root and Kernel File Systems...
[ OK ] Started Forward Password Requests to Wall Directory Watch.
[ OK ] Reached target Local Encrypted Volumes.
[ 21.912238] Adding 4194240k swap on /dev/mapper/rhel_ltcden3--lp1-swap. Priority:-2 extents:1 across:4194240k FS
[ OK ] Listening on Device-mapper event daemon FIFOs.
Starting Monitoring of LVM2 mirrors…ng dmeventd or progress polling...
Starting Setup Virtual Console...
[ OK ] Stopped target Initrd Root File System.
Mounting Kernel Debug File System...
[ OK ] Listening on udev Control Socket.
Starting udev Coldplug all Devices...
[ OK ] Created slice system-sshd\x2dkeygen.slice.
[ OK ] Stopped target Initrd File Systems.
[ OK ] Listening on LVM2 poll daemon socket.
[ OK ] Activated swap /dev/mapper/rhel_ltcden3--lp1-swap.
[ OK ] Mounted Huge Pages File System.
[ OK ] Started Read and set NIS domainname from /etc/sysconfig/network.
[ OK ] Started Create list of required sta…vice nodes for the current kernel.
[ OK ] Started Journal Service.
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Mounted Kernel Debug File System.
[ OK ] Reached target Swap.
[ 22.217261] xfs filesystem being remounted at / supports timestamps until 2038 (0x7fffffff)
[ OK ] Started Remount Root and Kernel File Systems.
[ OK ] Started Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
Starting Create Static Device Nodes in /dev...
Starting Load/Save Random Seed...
Starting Flush Journal to Persistent Storage...
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
Starting Apply Kernel Variables...
[ 22.341308] synth uevent: /devices/vio: failed to send uevent
[ 22.341317] vio vio: uevent: failed to send synthetic uevent: -19
[ 22.341597] synth uevent: /devices/vio/4000: failed to send uevent
[ 22.341600] vio 4000: uevent: failed to send synthetic uevent: -19
[ 22.341610] synth uevent: /devices/vio/4001: failed to send uevent
[ 22.341613] vio 4001: uevent: failed to send synthetic uevent: -19
[ 22.341622] synth uevent: /devices/vio/4002: failed to send uevent
[ 22.341625] vio 4002: uevent: failed to send synthetic uevent: -19
[ 22.341633] synth uevent: /devices/vio/4004: failed to send uevent
[ 22.341636] vio 4004: uevent: failed to send synthetic uevent: -19
[ OK ] Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization...
[ OK ] Started Load/Save Random Seed.
[ OK ] Started Flush Journal to Persistent Storage.
[ OK ] Started Setup Virtual Console.
[ OK ] Started Apply Kernel Variables.
[ OK ] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager...
[ OK ] Started udev Kernel Device Manager.
[ 24.100485] pseries_rng: Registering IBM pSeries RNG driver
[ OK ] Created slice system-lvm2\x2dpvscan.slice.
Starting LVM event activation on device 8:19...
[ OK ] Started LVM event activation on device 8:19.
[ OK ] Started udev Wait for Complete Device Initialization.
[ OK ] Reached target Local File Systems (Pre).
Mounting /home...
Mounting /home2...
Mounting /boot...
[ 25.049055] XFS (nvme0n1p1): Mounting V5 Filesystem 31458cd5-8eb4-48b4-8f5a-112217ef59df
[ 25.049822] XFS (dm-1): Mounting V5 Filesystem 0ac3d742-375d-4cd7-bdd2-72b0559b1957
[ 25.050953] XFS (sdb2): Mounting V5 Filesystem c72725b8-35e3-42b4-b5cb-f8435cada964
[ 25.055813] XFS (nvme0n1p1): Ending clean mount
[ 25.056844] xfs filesystem being mounted at /home supports timestamps until 2038 (0x7fffffff)
[ OK ] Mounted /home.
[ 25.389921] XFS (dm-1): Ending clean mount
[ 25.513566] xfs filesystem being mounted at /home2 supports timestamps until 2038 (0x7fffffff)
[ OK ] Mounted /home2.
[ 26.797307] XFS (sdb2): Ending clean mount
[ 26.857340] xfs filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
[ OK ] Mounted /boot.
[ OK ] Reached target Local File Systems.
Starting Tell Plymouth To Write Out Runtime Data...
Starting Restore /run/initramfs on shutdown...
Starting Import network configuration from initramfs...
[ OK ] Started Restore /run/initramfs on shutdown.
[ OK ] Started Import network configuration from initramfs.
Starting Create Volatile Files and Directories...
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Create Volatile Files and Directories.
Mounting RPC Pipe File System...
Starting Security Auditing Service...
Starting RPC Bind...
[ OK ] Started RPC Bind.
[ 27.888702] RPC: Registered named UNIX socket transport module.
[ 27.888714] RPC: Registered udp transport module.
[ 27.888717] RPC: Registered tcp transport module.
[ 27.888719] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ OK ] Mounted RPC Pipe File System.
[ OK ] Reached target rpc_pipefs.target.
[ OK ] Started Security Auditing Service.
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Listening on Open-iSCSI iscsid Socket.
[ OK ] Listening on CUPS Scheduler.
[ OK ] Started Run system activity accounting tool every 10 minutes.
[ OK ] Started CUPS Scheduler.
[ OK ] Reached target Paths.
[ OK ] Listening on SSSD Kerberos Cache Manager responder socket.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Started Generate summary of yesterday's process accounting.
[ OK ] Started daily update of the root trust anchor for DNSSEC.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Started dnf makecache --timer.
[ OK ] Reached target Timers.
[ OK ] Listening on Open-iSCSI iscsiuio Socket.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting NTP client/server...
Starting Hardware RNG Entropy Gatherer Wake threshold service...
[ OK ] Started libstoragemgmt plug-in server daemon.
[ OK ] Started irqbalance daemon.
Starting Resets System Activity Logs...
Starting ppc64-diag rtas_errd (platform error handling) Service...
Starting Self Monitoring and Reporting Technology (SMART) Daemon...
[ OK ] Reached target sshd-keygen.target.
Starting ABRT Automated Bug Reporting Tool...
Starting System Security Services Daemon...
Starting Authorization Manager...
[ OK ] Started D-Bus System Message Bus.
Starting Avahi mDNS/DNS-SD Stack...
[ OK ] Started Hardware RNG Entropy Gatherer Wake threshold service.
[ OK ] Started Hardware RNG Entropy Gatherer Daemon.
[ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
[ OK ] Started Resets System Activity Logs.
[ OK ] Started ppc64-diag rtas_errd (platform error handling) Service.
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Started NTP client/server.
[ OK ] Started System Security Services Daemon.
[ OK ] Reached target User and Group Name Lookups.
Starting Login Service...
[ OK ] Started Login Service.
[ OK ] Started Authorization Manager.
Starting firewalld - dynamic firewall daemon...
Starting Modem Manager...
[ OK ] Started Modem Manager.
[ OK ] Started firewalld - dynamic firewall daemon.
[ OK ] Reached target Network (Pre).
Starting Network Manager...
[ OK ] Started Network Manager.
Starting hybrid virtual network scan and config...
Starting Network Manager Wait Online...
[ OK ] Reached target Network.
Starting Enable periodic update of entitlement certificates....
Starting CUPS Scheduler...
Starting GSSAPI Proxy Daemon...
Starting OpenSSH server daemon...
Starting Logout off all iSCSI sessions on shutdown...
[ OK ] Started Logout off all iSCSI sessions on shutdown.
[ OK ] Started Enable periodic update of entitlement certificates..
Starting Hostname Service...
[ OK ] Started ABRT Automated Bug Reporting Tool.
[ OK ] Started ABRT kernel log watcher.
[ OK ] Started ABRT Xorg log watcher.
[ OK ] Started Creates ABRT problems from coredumpctl messages.
[ OK ] Started Hostname Service.
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[FAILED] Failed to start hybrid virtual network scan and config.
See 'systemctl status hcn-init.service' for details.
[ OK ] Started OpenSSH server daemon.
[ OK ] Started GSSAPI Proxy Daemon.
[ OK ] Reached target NFS client services.
Starting Network Manager Script Dispatcher Service...
[ OK ] Started CUPS Scheduler.
[ OK ] Started Network Manager Script Dispatcher Service.
[ OK ] Started Network Manager Wait Online.
[ OK ] Reached target Network is Online.
Starting Notify NFS peers of a restart...
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
Starting Harvest vmcores for ABRT...
Starting Permit User Sessions...
Starting System Logging Service...
[ OK ] Started Notify NFS peers of a restart.
[ OK ] Started Permit User Sessions.
[ OK ] Started Job spooling tools.
Starting Terminate Plymouth Boot Screen...
[ OK ] Started Command Scheduler.
Starting Hold until boot process finishes up...
[ OK ] Started System Logging Service.
[ 44.801795] ------------[ cut here ]------------
[ 44.801810] WARNING: CPU: 24 PID: 1906 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
[ 44.801895] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set rfkill nf_tables nfnetlink sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi nvme ibmveth scsi_transport_srp nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
[ 44.801926] CPU: 24 PID: 1906 Comm: in:imjournal Not tainted 6.2.0-rc8ssh #35
[ 44.801930] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
[ 44.801933] NIP: c00800000062fa80 LR: c00800000062fa4c CTR: c000000000ea4d40
[ 44.801936] REGS: c00000001984b690 TRAP: 0700 Not tainted (6.2.0-rc8ssh)
[ 44.801939] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24224842 XER: 00000000
[ 44.801947] CFAR: c00800000062fa54 IRQMASK: 0
[ 44.801947] GPR00: c0000000091cbec8 c00000001984b930 c0080000006d8300 0000000000000000
[ 44.801947] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000051aa4d90
[ 44.801947] GPR08: 0000000000000000 c000000051aa4e40 0000000000000000 fffffffffffffffd
[ 44.801947] GPR12: 0000000000000040 c000004afece5880 0000000000000000 0000000004000000
[ 44.801947] GPR16: c00000001984bb38 c00000001984ba38 c00000001984ba68 c00000002c323c00
[ 44.801947] GPR20: c0000000091cbe00 0000000000008000 c0000000516e5800 00000000002ec44d
[ 44.801947] GPR24: 000000000030af4d 000000000000000d c000000008d71680 00000000002ec44d
[ 44.801947] GPR28: c00000002c322400 c0000000091cbe00 c000000054c05618 000000000030af4d
[ 44.801983] NIP [c00800000062fa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
[ 44.802037] LR [c00800000062fa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
[ 44.802090] Call Trace:
[ 44.802091] [c00000001984b930] [c000000054c05618] 0xc000000054c05618 (unreliable)
[ 44.802096] [c00000001984b950] [c008000000630094] xfs_iunlink+0x1bc/0x280 [xfs]
[ 44.802149] [c00000001984b9d0] [c008000000634754] xfs_rename+0x69c/0xd10 [xfs]
[ 44.802202] [c00000001984bb10] [c00800000062e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
[ 44.802255] [c00000001984bba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
[ 44.802261] [c00000001984bc90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
[ 44.802265] [c00000001984bde0] [c000000000580520] sys_rename+0x60/0x80
[ 44.802269] [c00000001984be10] [c000000000033630] system_call_exception+0x150/0x3b0
[ 44.802274] [c00000001984be50] [c00000000000c554] system_call_common+0xf4/0x258
[ 44.802280] --- interrupt: c00 at 0x7fffa6482e20
[ 44.802282] NIP: 00007fffa6482e20 LR: 00007fffa6055e24 CTR: 0000000000000000
[ 44.802285] REGS: c00000001984be80 TRAP: 0c00 Not tainted (6.2.0-rc8ssh)
[ 44.802288] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
[ 44.802297] IRQMASK: 0
[ 44.802297] GPR00: 0000000000000026 00007fffa536d220 00007fffa6607300 00007fffa536d288
[ 44.802297] GPR04: 000000014f7a6b70 0000000000000000 0700000000000000 0000000000000002
[ 44.802297] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 44.802297] GPR12: 0000000000000000 00007fffa53766e0 000000014f795930 0000000000000000
[ 44.802297] GPR16: 0000000126b67648 00007fffa6057ce0 0000000000000003 000000000000002b
[ 44.802297] GPR20: 0000000000000212 00007fffa536e3a0 00007fffa536e398 00007fff98008690
[ 44.802297] GPR24: 0000000000000000 00007fffa536e388 00007fffa536e378 00007fffa536e3b0
[ 44.802297] GPR28: 00007fffa6070000 00007fffa60705e0 00007fff98000c10 00007fffa536d288
[ 44.802331] NIP [00007fffa6482e20] 0x7fffa6482e20
[ 44.802334] LR [00007fffa6055e24] 0x7fffa6055e24
[ 44.802336] --- interrupt: c00
[ 44.802338] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
[ 44.802352] ---[ end trace 0000000000000000 ]---
[ 44.802356] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x9cc/0xd10 [xfs]
[ 44.802412] CPU: 24 PID: 1906 Comm: in:imjournal Tainted: G W 6.2.0-rc8ssh #35
[ 44.802415] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
[ 44.802418] Call Trace:
[ 44.802420] [c00000001984b8f0] [c000000000e87328] dump_stack_lvl+0x6c/0x9c (unreliable)
[ 44.802425] [c00000001984b920] [c008000000616a84] xfs_error_report+0x5c/0x80 [xfs]
[ 44.802478] [c00000001984b980] [c0080000006467b0] xfs_trans_cancel+0x178/0x1b0 [xfs]
[ 44.802533] [c00000001984b9d0] [c008000000634a84] xfs_rename+0x9cc/0xd10 [xfs]
[ 44.802586] [c00000001984bb10] [c00800000062e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
[ 44.802641] [c00000001984bba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
[ 44.802644] [c00000001984bc90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
[ 44.802648] [c00000001984bde0] [c000000000580520] sys_rename+0x60/0x80
[ 44.802652] [c00000001984be10] [c000000000033630] system_call_exception+0x150/0x3b0
[ 44.802657] [c00000001984be50] [c00000000000c554] system_call_common+0xf4/0x258
[ 44.802661] --- interrupt: c00 at 0x7fffa6482e20
[ 44.802664] NIP: 00007fffa6482e20 LR: 00007fffa6055e24 CTR: 0000000000000000
[ 44.802667] REGS: c00000001984be80 TRAP: 0c00 Tainted: G W (6.2.0-rc8ssh)
[ 44.802670] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
[ 44.802678] IRQMASK: 0
[ 44.802678] GPR00: 0000000000000026 00007fffa536d220 00007fffa6607300 00007fffa536d288
[ 44.802678] GPR04: 000000014f7a6b70 0000000000000000 0700000000000000 0000000000000002
[ 44.802678] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 44.802678] GPR12: 0000000000000000 00007fffa53766e0 000000014f795930 0000000000000000
[ 44.802678] GPR16: 0000000126b67648 00007fffa6057ce0 0000000000000003 000000000000002b
[ 44.802678] GPR20: 0000000000000212 00007fffa536e3a0 00007fffa536e398 00007fff98008690
[ 44.802678] GPR24: 0000000000000000 00007fffa536e388 00007fffa536e378 00007fffa536e3b0
[ 44.802678] GPR28: 00007fffa6070000 00007fffa60705e0 00007fff98000c10 00007fffa536d288
[ 44.802712] NIP [00007fffa6482e20] 0x7fffa6482e20
[ 44.802715] LR [00007fffa6055e24] 0x7fffa6055e24
[ 44.802717] --- interrupt: c00
[ 44.804354] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
[ 44.804413] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
>> [ 333.390615] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
>> [ 333.390645] CPU: 56 PID: 12450 Comm: rm Not tainted 6.2.0-rc4ssh+ #4
>> [ 333.390649] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
>> [ 333.390652] NIP: c0080000004bfa80 LR: c0080000004bfa4c CTR: c000000000ea28d0
>> [ 333.390655] REGS: c0000000442bb8c0 TRAP: 0700 Not tainted (6.2.0-rc4ssh+)
>> [ 333.390658] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24002842 XER: 00000000
>> [ 333.390666] CFAR: c0080000004bfa54 IRQMASK: 0
>> [ 333.390666] GPR00: c00000003b69c0c8 c0000000442bbb60 c008000000568300 0000000000000000
>> [ 333.390666] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000004b27d78
>> [ 333.390666] GPR08: 0000000000000000 c000000004b27e28 0000000000000000 fffffffffffffffd
>> [ 333.390666] GPR12: 0000000000000040 c000004afecc5880 0000000106620918 0000000000000001
>> [ 333.390666] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
>> [ 333.390666] GPR20: 0000000106620e30 c0000000880ba938 0000000000200000 00000000002ec44d
>> [ 333.390666] GPR24: 000000000008170d 000000000000000d c0000000519f4800 00000000002ec44d
>> [ 333.390666] GPR28: c0000000880ba800 c00000003b69c000 c0000000833edd20 000000000008170d
>> [ 333.390702] NIP [c0080000004bfa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
>> [ 333.390756] LR [c0080000004bfa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
>> [ 333.390810] Call Trace:
>> [ 333.390811] [c0000000442bbb60] [c0000000833edd20] 0xc0000000833edd20 (unreliable)
>> [ 333.390816] [c0000000442bbb80] [c0080000004c0094] xfs_iunlink+0x1bc/0x280 [xfs]
>> [ 333.390869] [c0000000442bbc00] [c0080000004c3f84] xfs_remove+0x1dc/0x310 [xfs]
>> [ 333.390922] [c0000000442bbc70] [c0080000004be180] xfs_vn_unlink+0x68/0xf0 [xfs]
>> [ 333.390975] [c0000000442bbcd0] [c000000000576b24] vfs_unlink+0x1b4/0x3d0
>
> ...that trips when rm tries to remove a file, which means that the call
> stack is
>
> xfs_remove -> xfs_iunlink -> xfs_iunlink_insert_inode ->
> xfs_iunlink_update_backref -> xfs_iunlink_lookup <kaboom>
>
> It looks as though "rm foo" unlinked foo from the directory and was
> trying to insert it at the head of one of the unlinked lists in the AGI
> buffer. The AGI claims that the list points to an ondisk inode, so the
> iunlink code tries to find the incore inode to update the incore list,
> fails to find an incore inode, and this is the result...
This seems to happen for rename as well. i.e xfs_rename.
Does rename path calls rm first, and then create?
>>
>>
>> we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
>> as the bad commit.
>> Short description of commit:
>> commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad)
>> Author: Dave Chinner <dchinner@redhat.com>
>> Date: Thu Jul 14 11:42:39 2022 +1000
>>
>> xfs: refactor xlog_recover_process_iunlinks()
>
> ...which was in the middle of the series that reworked thev mount time
> iunlink clearing. Oddly, I don't spot any obvious errors in /that/
> patch that didn't already exist. But this does make me wonder, does
> xfs_repair -n have anything to say about unlinked or orphaned inodes?
>
> The runtime code expects that every ondisk inode in an iunlink chain has
> an incore inode that is linked (via i_{next,prev}_unlinked) to the other
> incore inodes in that same chain. If this requirement is not met, then
> the WARNings you see will trip, and the fs shuts down.
>
> My hypothesis here is that one of the AGs has an unprocessed unlinked
> list. At mount time, the ondisk log was clean, so mount time log
> recovery didn't invoke xlog_recover_process_iunlinks, and the list was
> not cleared. The mount code does not construct the incore unlinked list
> from an existing ondisk iunlink list, hence the WARNing. Prior to 5.17,
> we only manipulated the ondisk unlink list, and the code never noticed
> or cared if there were mystery inodes in the list that never went away.
>
> (Obviously, if something blew up earlier in dmesg, that would be
> relevant here.)
>
> It's possible that we could end up in this situation (clean log,
> unlinked inodes) if a previous log recovery was only partially
> successful at clearing the unlinked list, since all that code ignores
> errors. If that happens, we ... succeed at mounting and clean the log.
>
> If you're willing to patch your kernels, it would be interesting
> to printk if the xfs_read_agi or the xlog_recover_iunlink_bucket calls
> in xlog_recover_iunlink_ag returns an error code. It might be too late
We can try. Please provide the Patch.
> to capture that, hence my suggestion of seeing if xfs_repair -n will
> tell us anything else.
>
Could you please clarify? We should run xfs_repair -n from 5.17-rc2 kernel?
> I've long thought that the iunlink recovery ought to complain loudly and
> fail the mount if it can't clear all the unlinked files. Given the new
> iunlink design, I think it's pretty much required now. The uglier piece
> is that now we either (a) have to clear iunlinks at mount time
> unconditionally as Eric has been saying for years; or (b) construct the
> incore list at a convenient time so that the incore list always exists.
>
> Thanks for the detailed report!
>
> --D
>
>>
>> Git bisect log:
>> git bisect start
>> # good: [26291c54e111ff6ba87a164d85d4a4e134b7315c] Linux 5.17-rc2
>> git bisect good 26291c54e111ff6ba87a164d85d4a4e134b7315c
>> # bad: [4fe89d07dcc2804c8b562f6c7896a45643d34b2f] Linux 6.0
>> git bisect bad 4fe89d07dcc2804c8b562f6c7896a45643d34b2f
>> # good: [d7227785e384d4422b3ca189aa5bf19f462337cc] Merge tag 'sound-5.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
>> git bisect good d7227785e384d4422b3ca189aa5bf19f462337cc
>> # good: [526942b8134cc34d25d27f95dfff98b8ce2f6fcd] Merge tag 'ata-5.20-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
>> git bisect good 526942b8134cc34d25d27f95dfff98b8ce2f6fcd
>> # good: [328141e51e6fc79d21168bfd4e356dddc2ec7491] Merge tag 'mmc-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
>> git bisect good 328141e51e6fc79d21168bfd4e356dddc2ec7491
>> # bad: [eb555cb5b794f4e12a9897f3d46d5a72104cd4a7] Merge tag '5.20-rc-ksmbd-server-fixes' of git://git.samba.org/ksmbd
>> git bisect bad eb555cb5b794f4e12a9897f3d46d5a72104cd4a7
>> # bad: [f20c95b46b8fa3ad34b3ea2e134337f88591468b] Merge tag 'tpmdd-next-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd
>> git bisect bad f20c95b46b8fa3ad34b3ea2e134337f88591468b
>> # bad: [fad235ed4338749a66ddf32971d4042b9ef47f44] Merge tag 'arm-late-6.0' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
>> git bisect bad fad235ed4338749a66ddf32971d4042b9ef47f44
>> # good: [e495274793ea602415d050452088a496abcd9e6c] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
>> git bisect good e495274793ea602415d050452088a496abcd9e6c
>> # good: [9daee913dc8d15eb65e0ff560803ab1c28bb480b] Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
>> git bisect good 9daee913dc8d15eb65e0ff560803ab1c28bb480b
>> # bad: [29b1d469f3f6842ee4115f0b21f018fc44176468] Merge tag 'trace-rtla-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
>> git bisect bad 29b1d469f3f6842ee4115f0b21f018fc44176468
>> # good: [932b42c66cb5d0ca9800b128415b4ad6b1952b3e] xfs: replace XFS_IFORK_Q with a proper predicate function
>> git bisect good 932b42c66cb5d0ca9800b128415b4ad6b1952b3e
>> # bad: [35c5a09f5346e690df7ff2c9075853e340ee10b3] Merge tag 'xfs-buf-lockless-lookup-5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs into xfs-5.20-mergeB
>> git bisect bad 35c5a09f5346e690df7ff2c9075853e340ee10b3
>> # bad: [fad743d7cd8bd92d03c09e71f29eace860f50415] xfs: add log item precommit operation
>> git bisect bad fad743d7cd8bd92d03c09e71f29eace860f50415
>> # bad: [04755d2e5821b3afbaadd09fe5df58d04de36484] xfs: refactor xlog_recover_process_iunlinks()
>> git bisect bad 04755d2e5821b3afbaadd09fe5df58d04de36484
>> # good: [a4454cd69c66bf3e3bbda352b049732f836fc6b2] xfs: factor the xfs_iunlink functions
>> git bisect good a4454cd69c66bf3e3bbda352b049732f836fc6b2
>> Bisecting: 0 revisions left to test after this (roughly 0 steps)
>> [4fcc94d653270fcc7800dbaf3b11f78cb462b293] xfs: track the iunlink list pointer in the xfs_inode
>>
>>
>> Please reach out, in case any more details are needed. sent with very limited
>> knowledge of xfs system. these logs are from 5.19 kernel.
>>
>> # xfs_info /home
>> meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=13107200 blks
>> = sectsz=4096 attr=2, projid32bit=1
>> = crc=1 finobt=1, sparse=1, rmapbt=0
>> = reflink=1 bigtime=0 inobtcount=0
>> data = bsize=4096 blocks=52428800, imaxpct=25
>> = sunit=0 swidth=0 blks
>> naming =version 2 bsize=4096 ascii-ci=0, ftype=1
>> log =internal log bsize=4096 blocks=25600, version=2
>> = sectsz=4096 sunit=1 blks, lazy-count=1
>> realtime =none extsz=4096 blocks=0, rtextents=0
>>
>> # xfs_info -V
>> xfs_info version 5.0.0
>>
>> # uname -a
>> 5.19.0-rc2
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-02-18 7:17 ` shrikanth hegde
@ 2023-02-22 16:41 ` Darrick J. Wong
2023-02-24 8:04 ` shrikanth hegde
2023-03-09 14:26 ` Ritesh Harjani
0 siblings, 2 replies; 28+ messages in thread
From: Darrick J. Wong @ 2023-02-22 16:41 UTC (permalink / raw)
To: shrikanth hegde; +Cc: dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On Sat, Feb 18, 2023 at 12:47:48PM +0530, shrikanth hegde wrote:
>
>
> On 2/17/23 10:23 PM, Darrick J. Wong wrote:
> > On Fri, Feb 17, 2023 at 04:45:12PM +0530, shrikanth hegde wrote:
> >> We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in
> >> one of our systems. System fails to come up. System was booting well
> >> with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel.
> >>
> >> Panic Log is below.
> >> [ 333.390539] ------------[ cut here ]------------
> >> [ 333.390552] WARNING: CPU: 56 PID: 12450 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
> >
> > Hmm, ok, so this is the same if (WARN_ON_ONCE(!ip || !ip->i_ino)) line
> > in xfs_iunlink_lookup that I've been bonking my head on the past
> > several days. 333 seconds uptime, so I guess this is a pretty recent
> > mount. You didn't post a full dmesg, so I can only assume there weren't
> > any *other* obvious complaints from XFS when the fs was mounted...
> >
>
> Darrick, Dave. Thank you for taking a look at this. sorry i didnt paste the full log.
> Please find the full dmesg below. it was kexec from 5.17-rc2 to 6.2-rc8
>
>
> Starting Reboot via kexec...
> [ 71.134231] printk: systemd-shutdow: 37 output lines suppressed due to ratelimiting
> [ 71.158255] systemd-shutdown[1]: Syncing filesystems and block devices.
> [ 71.160419] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
> [ 71.214007] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
> [ 71.233182] systemd-shutdown[1]: Unmounting file systems.
> [ 71.233845] [2287]: Remounting '/home' read-only in with options 'attr2,inode64,logbufs=8,logbsize=32k,noquota'.
> [ 71.234873] [2288]: Unmounting '/home'.
> [ 71.237859] XFS (nvme0n1p1): Unmounting Filesystem
> [ 71.524111] [2289]: Remounting '/' read-only in with options 'attr2,inode64,logbufs=8,logbsize=32k,noquota'.
> [ 71.810094] systemd-shutdown[1]: All filesystems unmounted.
> [ 71.810103] systemd-shutdown[1]: Deactivating swaps.
> [ 71.810121] systemd-shutdown[1]: All swaps deactivated. pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/li[ 71.810126] systemd-shutdown[1]: Detaching loop devices.'
> [ 71.810227] systemd-shutdown[1]: All loop devices detached.
> [ 71.810232] systemd-shutdown[1]: Detaching DM devices.
> [ 71.932097] printk: shutdown: 8 output lines suppressed due to ratelimiting
> [ 71.954484] dracut Warning: Killing all remaining processes
> dracut Warning: Killing all remaining processes
> [ 72.001360] XFS (dm-0): Unmounting Filesystem
> [ 72.393816] dracut Warning: Unmounted /oldroot.
> [ 72.409893] dracut: Disassembling device-mapper devices
> [ 72.527853] Removing IBM Power 842 compression device
> [ 78.084038] kexec_core: Starting new kernel
> [ 78.104094] kexec: waiting for cpu 26 (physical 26) to enter 1 state
> [ 78.104102] kexec: waiting for cpu 87 (physical 87) to enter 1 state
> [ 78.104109] kexec: waiting for cpu 1 (physical 1) to enter 2 state
> [ 78.104248] kexec: waiting for cpu 2 (physical 2) to enter 2 state
> [ 78.104275] kexec: waiting for cpu 3 (physical 3) to enter 2 state
> [ 78.104289] kexec: waiting for cpu 4 (physical 4) to enter 2 state
> [ 78.104303] kexec: waiting for cpu 5 (physical 5) to enter 2 state
> [ 78.104315] kexec: waiting for cpu 8 (physical 8) to enter 2 state
> [ 78.104352] kexec: waiting for cpu 48 (physical 48) to enter 2 state
> [ 78.104357] kexec: waiting for cpu 49 (physical 49) to enter 2 state
> [ 78.278072] kexec: Starting switchover sequence.
> I'm in purgatory
> [ 0.000000] radix-mmu: Page sizes from device-tree:
> [ 0.000000] radix-mmu: Page size shift = 12 AP=0x0
> [ 0.000000] radix-mmu: Page size shift = 16 AP=0x5
> [ 0.000000] radix-mmu: Page size shift = 21 AP=0x1
> [ 0.000000] radix-mmu: Page size shift = 30 AP=0x2
> [ 0.000000] Activating Kernel Userspace Access Prevention
> [ 0.000000] Activating Kernel Userspace Execution Prevention
> [ 0.000000] radix-mmu: Mapped 0x0000000000000000-0x0000000002600000 with 2.00 MiB pages (exec)
> [ 0.000000] radix-mmu: Mapped 0x0000000002600000-0x0000004b00000000 with 2.00 MiB pages
> [ 0.000000] lpar: Using radix MMU under hypervisor
> [ 0.000000] Linux version 6.2.0-rc8ssh (root@ltcden3-lp1.aus.stglabs.ibm.com) (gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10), GNU ld version 2.30-113.el8) #35 SMP Sat Feb 18 00:41:56 EST 2023
> [ 0.000000] Found initrd at 0xc0000000061d0000:0xc00000000ac38d3b
> [ 0.000000] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> [ 0.000000] printk: bootconsole [udbg0] enabled
> [ 0.000000] Partition configured for 96 cpus.
> [ 0.000000] CPU maps initialized for 8 threads per core
> [ 0.000000] numa: Partition configured for 32 NUMA nodes.
> [ 0.000000] -----------------------------------------------------
> [ 0.000000] phys_mem_size = 0x4b00000000
> [ 0.000000] dcache_bsize = 0x80
> [ 0.000000] icache_bsize = 0x80
> [ 0.000000] cpu_features = 0x000c00eb8f5f9187
> [ 0.000000] possible = 0x000ffbfbcf5fb187
> [ 0.000000] always = 0x0000000380008181
> [ 0.000000] cpu_user_features = 0xdc0065c2 0xaef60000
> [ 0.000000] mmu_features = 0xbc007641
> [ 0.000000] firmware_features = 0x000005bfc55bfc57
> [ 0.000000] vmalloc start = 0xc008000000000000
> [ 0.000000] IO start = 0xc00a000000000000
> [ 0.000000] vmemmap start = 0xc00c000000000000
> [ 0.000000] -----------------------------------------------------
> [ 0.000000] numa: NODE_DATA [mem 0x4afe663780-0x4afe66aeff]
> [ 0.000000] rfi-flush: fallback displacement flush available
> [ 0.000000] count-cache-flush: hardware flush enabled.
> [ 0.000000] link-stack-flush: software flush enabled.
> [ 0.000000] stf-barrier: eieio barrier available
> [ 0.000000] PPC64 nvram contains 15360 bytes
> [ 0.000000] barrier-nospec: using ORI speculation barrier
> [ 0.000000] Zone ranges:
> [ 0.000000] Normal [mem 0x0000000000000000-0x0000004affffffff]
> [ 0.000000] Device empty
> [ 0.000000] Movable zone start for each node
> [ 0.000000] Early memory node ranges
> [ 0.000000] node 2: [mem 0x0000000000000000-0x0000004affffffff]
> [ 0.000000] Initializing node 0 as memoryless
> [ 0.000000] Initmem setup node 0 as memoryless
> [ 0.000000] Initializing node 1 as memoryless
> [ 0.000000] Initmem setup node 1 as memoryless
> [ 0.000000] Initmem setup node 2 [mem 0x0000000000000000-0x0000004affffffff]
> [ 0.000000] Initializing node 3 as memoryless
> [ 0.000000] Initmem setup node 3 as memoryless
> [ 0.000000] Initializing node 4 as memoryless
> [ 0.000000] Initmem setup node 4 as memoryless
> [ 0.000000] Initializing node 5 as memoryless
> [ 0.000000] Initmem setup node 5 as memoryless
> [ 0.000000] Initializing node 6 as memoryless
> [ 0.000000] Initmem setup node 6 as memoryless
> [ 0.000000] Initializing node 7 as memoryless
> [ 0.000000] Initmem setup node 7 as memoryless
> [ 0.000000] Initializing node 8 as memoryless
> [ 0.000000] Initmem setup node 8 as memoryless
> [ 0.000000] Initializing node 9 as memoryless
> [ 0.000000] Initmem setup node 9 as memoryless
> [ 0.000000] Initializing node 10 as memoryless
> [ 0.000000] Initmem setup node 10 as memoryless
> [ 0.000000] Initializing node 11 as memoryless
> [ 0.000000] Initmem setup node 11 as memoryless
> [ 0.000000] Initializing node 12 as memoryless
> [ 0.000000] Initmem setup node 12 as memoryless
> [ 0.000000] Initializing node 13 as memoryless
> [ 0.000000] Initmem setup node 13 as memoryless
> [ 0.000000] Initializing node 14 as memoryless
> [ 0.000000] Initmem setup node 14 as memoryless
> [ 0.000000] Initializing node 15 as memoryless
> [ 0.000000] Initmem setup node 15 as memoryless
> [ 0.000000] Initializing node 16 as memoryless
> [ 0.000000] Initmem setup node 16 as memoryless
> [ 0.000000] Initializing node 17 as memoryless
> [ 0.000000] Initmem setup node 17 as memoryless
> [ 0.000000] Initializing node 18 as memoryless
> [ 0.000000] Initmem setup node 18 as memoryless
> [ 0.000000] Initializing node 19 as memoryless
> [ 0.000000] Initmem setup node 19 as memoryless
> [ 0.000000] Initializing node 20 as memoryless
> [ 0.000000] Initmem setup node 20 as memoryless
> [ 0.000000] Initializing node 21 as memoryless
> [ 0.000000] Initmem setup node 21 as memoryless
> [ 0.000000] Initializing node 22 as memoryless
> [ 0.000000] Initmem setup node 22 as memoryless
> [ 0.000000] Initializing node 23 as memoryless
> [ 0.000000] Initmem setup node 23 as memoryless
> [ 0.000000] Initializing node 24 as memoryless
> [ 0.000000] Initmem setup node 24 as memoryless
> [ 0.000000] Initializing node 25 as memoryless
> [ 0.000000] Initmem setup node 25 as memoryless
> [ 0.000000] Initializing node 26 as memoryless
> [ 0.000000] Initmem setup node 26 as memoryless
> [ 0.000000] Initializing node 27 as memoryless
> [ 0.000000] Initmem setup node 27 as memoryless
> [ 0.000000] Initializing node 28 as memoryless
> [ 0.000000] Initmem setup node 28 as memoryless
> [ 0.000000] Initializing node 29 as memoryless
> [ 0.000000] Initmem setup node 29 as memoryless
> [ 0.000000] Initializing node 30 as memoryless
> [ 0.000000] Initmem setup node 30 as memoryless
> [ 0.000000] Initializing node 31 as memoryless
> [ 0.000000] Initmem setup node 31 as memoryless
> [ 0.000000] percpu: Embedded 10 pages/cpu s601512 r0 d53848 u655360
> [ 0.000000] Fallback order for Node 0: 0 2
> [ 0.000000] Fallback order for Node 1: 1 2
> [ 0.000000] Fallback order for Node 2: 2
> [ 0.000000] Fallback order for Node 3: 3 2
> [ 0.000000] Fallback order for Node 4: 4 2
> [ 0.000000] Fallback order for Node 5: 5 2
> [ 0.000000] Fallback order for Node 6: 6 2
> [ 0.000000] Fallback order for Node 7: 7 2
> [ 0.000000] Fallback order for Node 8: 8 2
> [ 0.000000] Fallback order for Node 9: 9 2
> [ 0.000000] Fallback order for Node 10: 10 2
> [ 0.000000] Fallback order for Node 11: 11 2
> [ 0.000000] Fallback order for Node 12: 12 2
> [ 0.000000] Fallback order for Node 13: 13 2
> [ 0.000000] Fallback order for Node 14: 14 2
> [ 0.000000] Fallback order for Node 15: 15 2
> [ 0.000000] Fallback order for Node 16: 16 2
> [ 0.000000] Fallback order for Node 17: 17 2
> [ 0.000000] Fallback order for Node 18: 18 2
> [ 0.000000] Fallback order for Node 19: 19 2
> [ 0.000000] Fallback order for Node 20: 20 2
> [ 0.000000] Fallback order for Node 21: 21 2
> [ 0.000000] Fallback order for Node 22: 22 2
> [ 0.000000] Fallback order for Node 23: 23 2
> [ 0.000000] Fallback order for Node 24: 24 2
> [ 0.000000] Fallback order for Node 25: 25 2
> [ 0.000000] Fallback order for Node 26: 26 2
> [ 0.000000] Fallback order for Node 27: 27 2
> [ 0.000000] Fallback order for Node 28: 28 2
> [ 0.000000] Fallback order for Node 29: 29 2
> [ 0.000000] Fallback order for Node 30: 30 2
> [ 0.000000] Fallback order for Node 31: 31 2
> [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 4910400
> [ 0.000000] Policy zone: Normal
> [ 0.000000] Kernel command line: root=/dev/mapper/rhel_ltcden3--lp1-root
> [ 0.000000] random: crng init done
> [ 0.000000] Dentry cache hash table entries: 16777216 (order: 11, 134217728 bytes, linear)
> [ 0.000000] Inode-cache hash table entries: 8388608 (order: 10, 67108864 bytes, linear)
> [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
> [ 0.000000] Memory: 313817216K/314572800K available (15168K kernel code, 5632K rwdata, 17600K rodata, 5440K init, 2721K bss, 755584K reserved, 0K cma-reserved)
> [ 0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=96, Nodes=32
> [ 0.000000] ftrace: allocating 38156 entries in 14 pages
> [ 0.000000] ftrace: allocated 14 pages with 3 groups
> [ 0.000000] trace event string verifier disabled
> [ 0.000000] rcu: Hierarchical RCU implementation.
> [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=2048 to nr_cpu_ids=96.
> [ 0.000000] Rude variant of Tasks RCU enabled.
> [ 0.000000] Tracing variant of Tasks RCU enabled.
> [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
> [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=96
> [ 0.000000] NR_IRQS: 512, nr_irqs: 512, preallocated irqs: 16
> [ 0.000000] xive: Using IRQ range [400000-40005f]
> [ 0.000000] xive: Interrupt handling initialized with spapr backend
> [ 0.000000] xive: Using priority 7 for all interrupts
> [ 0.000000] xive: Using 64kB queues
> [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
> [ 0.000001] time_init: 56 bit decrementer (max: 7fffffffffffff)
> [ 0.000021] clocksource: timebase: mask: 0xffffffffffffffff max_cycles: 0x761537d007, max_idle_ns: 440795202126 ns
> [ 0.000055] clocksource: timebase mult[1f40000] shift[24] registered
> [ 0.000233] Console: colour dummy device 80x25
> [ 0.000252] printk: console [hvc0] enabled
> [ 0.000252] printk: console [hvc0] enabled
> [ 0.000269] printk: bootconsole [udbg0] disabled
> [ 0.000269] printk: bootconsole [udbg0] disabled
> [ 0.000360] pid_max: default: 98304 minimum: 768
> [ 0.000481] LSM: initializing lsm=capability,yama,integrity,selinux,bpf
> [ 0.000550] Yama: becoming mindful.
> [ 0.000565] SELinux: Initializing.
> [ 0.000568] SELinux: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE is non-zero. This is deprecated and will be rejected in a future kernel release.
> [ 0.000573] SELinux: https://github.com/SELinuxProject/selinux-kernel/wiki/DEPRECATE-checkreqprot
> [ 0.000747] LSM support for eBPF active
> [ 0.000929] Mount-cache hash table entries: 262144 (order: 5, 2097152 bytes, linear)
> [ 0.001056] Mountpoint-cache hash table entries: 262144 (order: 5, 2097152 bytes, linear)
> [ 0.003430] cblist_init_generic: Setting adjustable number of callback queues.
> [ 0.003454] cblist_init_generic: Setting shift to 7 and lim to 1.
> [ 0.003486] cblist_init_generic: Setting shift to 7 and lim to 1.
> [ 0.003507] POWER10 performance monitor hardware support registered
> [ 0.003537] rcu: Hierarchical SRCU implementation.
> [ 0.003540] rcu: Max phase no-delay instances is 1000.
> [ 0.004445] smp: Bringing up secondary CPUs ...
> [ 0.022208] smp: Brought up 1 node, 96 CPUs
> [ 0.022218] numa: Node 2 CPUs: 0-95
> [ 0.022222] Big cores detected but using small core scheduling
> [ 0.033289] devtmpfs: initialized
> [ 0.042965] PCI host bridge /pci@800000020000019 ranges:
> [ 0.042984] MEM 0x0000040080000000..0x00000400feffffff -> 0x0000000080000000
> [ 0.042988] MEM 0x0000044000000000..0x0000047fffffffff -> 0x0006204000000000
> [ 0.043060] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
> [ 0.043066] futex hash table entries: 32768 (order: 6, 4194304 bytes, linear)
> [ 0.043643] NET: Registered PF_NETLINK/PF_ROUTE protocol family
> [ 0.043801] audit: initializing netlink subsys (disabled)
> [ 0.043903] audit: type=2000 audit(1676701683.040:1): state=initialized audit_enabled=0 res=1
> [ 0.043954] thermal_sys: Registered thermal governor 'fair_share'
> [ 0.043955] thermal_sys: Registered thermal governor 'step_wise'
> [ 0.044007] cpuidle: using governor menu
> [ 0.044306] pstore: Registered nvram as persistent store backend
> [ 0.044682] EEH: pSeries platform initialized
> [ 0.055324] PCI: Probing PCI hardware
> [ 0.055372] PCI host bridge to bus 0019:01
> [ 0.055376] pci_bus 0019:01: root bus resource [mem 0x40080000000-0x400feffffff] (bus address [0x80000000-0xfeffffff])
> [ 0.055381] pci_bus 0019:01: root bus resource [mem 0x44000000000-0x47fffffffff 64bit] (bus address [0x6204000000000-0x6207fffffffff])
> [ 0.055386] pci_bus 0019:01: root bus resource [bus 01-ff]
> [ 0.056001] pci 0019:01:00.0: No hypervisor support for SR-IOV on this device, IOV BARs disabled.
> [ 0.064978] IOMMU table initialized, virtual merging enabled
> [ 0.065086] pci 0019:01:00.0: Adding to iommu group 0
> [ 0.066308] EEH: Capable adapter found: recovery enabled.
> [ 0.066550] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
> [ 0.066812] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
> [ 0.066817] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
> [ 0.066821] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
> [ 0.066824] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
> [ 0.085068] cryptd: max_cpu_qlen set to 1000
> [ 0.085368] iommu: Default domain type: Translated
> [ 0.085371] iommu: DMA domain TLB invalidation policy: strict mode
> [ 0.085491] SCSI subsystem initialized
> [ 0.085517] usbcore: registered new interface driver usbfs
> [ 0.085523] usbcore: registered new interface driver hub
> [ 0.085542] usbcore: registered new device driver usb
> [ 0.085563] pps_core: LinuxPPS API ver. 1 registered
> [ 0.085565] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
> [ 0.085569] PTP clock support registered
> [ 0.085628] EDAC MC: Ver: 3.0.0
> [ 0.085885] NetLabel: Initializing
> [ 0.085887] NetLabel: domain hash size = 128
> [ 0.085889] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
> [ 0.085903] NetLabel: unlabeled traffic allowed by default
> [ 0.085956] vgaarb: loaded
> [ 0.086157] clocksource: Switched to clocksource timebase
> [ 0.086451] VFS: Disk quotas dquot_6.6.0
> [ 0.086480] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)
> [ 0.088080] NET: Registered PF_INET protocol family
> [ 0.088237] IP idents hash table entries: 262144 (order: 5, 2097152 bytes, linear)
> [ 0.091345] tcp_listen_portaddr_hash hash table entries: 65536 (order: 4, 1048576 bytes, linear)
> [ 0.091454] Table-perturb hash table entries: 65536 (order: 2, 262144 bytes, linear)
> [ 0.091480] TCP established hash table entries: 524288 (order: 6, 4194304 bytes, linear)
> [ 0.092201] TCP bind hash table entries: 65536 (order: 5, 2097152 bytes, linear)
> [ 0.092386] TCP: Hash tables configured (established 524288 bind 65536)
> [ 0.092708] MPTCP token hash table entries: 65536 (order: 4, 1572864 bytes, linear)
> [ 0.092826] UDP hash table entries: 65536 (order: 5, 2097152 bytes, linear)
> [ 0.093046] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes, linear)
> [ 0.093402] NET: Registered PF_UNIX/PF_LOCAL protocol family
> [ 0.093413] NET: Registered PF_XDP protocol family
> [ 0.093509] PCI: CLS 128 bytes, default 128
> [ 0.093638] Unpacking initramfs...
> [ 0.094862] vio_register_device_node: node lid missing 'reg'
> [ 0.103665] vas: GZIP feature is available
> [ 0.104512] hv-24x7: read 548 catalog entries, created 387 event attrs (0 failures), 387 descs
> [ 0.108478] Initialise system trusted keyrings
> [ 0.108493] Key type blacklist registered
> [ 0.108560] workingset: timestamp_bits=38 max_order=23 bucket_order=0
> [ 0.108587] zbud: loaded
> [ 0.108988] integrity: Platform Keyring initialized
> [ 0.119068] NET: Registered PF_ALG protocol family
> [ 0.119083] Key type asymmetric registered
> [ 0.119086] Asymmetric key parser 'x509' registered
> [ 0.119120] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
> [ 0.119182] io scheduler mq-deadline registered
> [ 0.119185] io scheduler kyber registered
> [ 0.119198] io scheduler bfq registered
> [ 0.120970] atomic64_test: passed
> [ 0.121210] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
> [ 0.121214] PowerPC PowerNV PCI Hotplug Driver version: 0.1
> [ 0.121532] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> [ 0.121728] Non-volatile memory driver v1.3
> [ 0.122174] rdac: device handler registered
> [ 0.122215] hp_sw: device handler registered
> [ 0.122218] emc: device handler registered
> [ 0.122260] alua: device handler registered
> [ 0.122450] usbcore: registered new interface driver usbserial_generic
> [ 0.122457] usbserial: USB Serial support registered for generic
> [ 0.122529] mousedev: PS/2 mouse device common for all mice
> [ 0.122644] rtc-generic rtc-generic: registered as rtc0
> [ 0.122676] rtc-generic rtc-generic: setting system clock to 2023-02-18T06:28:03 UTC (1676701683)
> [ 0.122755] xcede: xcede_record_size = 10
> [ 0.122758] xcede: Record 0 : hint = 1, latency = 0x1800 tb ticks, Wake-on-irq = 1
> [ 0.122765] xcede: Record 1 : hint = 2, latency = 0x3c00 tb ticks, Wake-on-irq = 0
> [ 0.122769] cpuidle: Skipping the 2 Extended CEDE idle states
> [ 0.122771] cpuidle: Fixed up CEDE exit latency to 12 us
> [ 0.123865] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sync_size new:65536 old:0
> [ 0.123871] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sync_sg new:510 old:0
> [ 0.123875] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sg_len new:4080 old:0
> [ 0.124018] hid: raw HID events driver (C) Jiri Kosina
> [ 0.124042] usbcore: registered new interface driver usbhid
> [ 0.124048] usbhid: USB HID core driver
> [ 0.124069] drop_monitor: Initializing network drop monitor service
> [ 0.134168] Initializing XFRM netlink socket
> [ 0.134234] NET: Registered PF_INET6 protocol family
> [ 0.134747] Segment Routing with IPv6
> [ 0.134756] In-situ OAM (IOAM) with IPv6
> [ 0.134776] NET: Registered PF_PACKET protocol family
> [ 0.134817] mpls_gso: MPLS GSO support
> [ 0.134836] secvar-sysfs: secvar: failed to retrieve secvar operations.
> [ 0.139134] registered taskstats version 1
> [ 0.140964] Loading compiled-in X.509 certificates
> [ 0.156881] Loaded X.509 cert 'Build time autogenerated kernel key: 7b04a1cdeda81c05f7a701657946db5548da6201'
> [ 0.157494] zswap: loaded using pool lzo/zbud
> [ 0.160050] page_owner is disabled
> [ 0.160226] pstore: Using crash dump compression: deflate
> [ 0.972073] Freeing initrd memory: 76160K
> [ 0.974020] Key type encrypted registered
> [ 0.974056] Secure boot mode disabled
> [ 0.974060] ima: No TPM chip found, activating TPM-bypass!
> [ 0.974067] Loading compiled-in module X.509 certificates
> [ 0.974567] Loaded X.509 cert 'Build time autogenerated kernel key: 7b04a1cdeda81c05f7a701657946db5548da6201'
> [ 0.974571] ima: Allocated hash algorithm: sha256
> [ 0.974598] Secure boot mode disabled
> [ 0.974615] Trusted boot mode disabled
> [ 0.974617] ima: No architecture policies found
> [ 0.974629] evm: Initialising EVM extended attributes:
> [ 0.974631] evm: security.selinux
> [ 0.974633] evm: security.SMACK64 (disabled)
> [ 0.974635] evm: security.SMACK64EXEC (disabled)
> [ 0.974637] evm: security.SMACK64TRANSMUTE (disabled)
> [ 0.974639] evm: security.SMACK64MMAP (disabled)
> [ 0.974641] evm: security.apparmor (disabled)
> [ 0.974642] evm: security.ima
> [ 0.974644] evm: security.capability
> [ 0.974646] evm: HMAC attrs: 0x1
> [ 0.974676] alg: No test for 842 (842-nx)
> [ 0.982519] Freeing unused kernel image (initmem) memory: 5440K
> [ 1.086157] Run /init as init process
> [ 1.092664] systemd[1]: systemd 239 (239-58.el8) running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy)
> [ 1.092708] systemd[1]: Detected virtualization powervm.
> [ 1.092714] systemd[1]: Detected architecture ppc64-le.
> [ 1.092718] systemd[1]: Running in initial RAM disk.
>
> Welcome to Red Hat Enterprise Linux 8.6 (Ootpa) dracut-049-201.git20220131.el8 (Initramfs)!
>
> [ 1.246394] systemd[1]: Set hostname to <ltcden3-lp1.aus.stglabs.ibm.com>.
> [ 1.321102] systemd[1]: Listening on Journal Socket.
> [ OK ] Listening on Journal Socket.
> [ 1.322421] systemd[1]: Started Hardware RNG Entropy Gatherer Daemon.
> [ OK ] Started Hardware RNG Entropy Gatherer Daemon.
> [ 1.323252] systemd[1]: Starting Create list of required static device nodes for the current kernel...
> Starting Create list of required st…ce nodes for the current kernel...
> [ 1.323333] systemd[1]: Reached target Local File Systems.
> [ OK ] Reached target Local File Systems.
> [ 1.324085] systemd[1]: Started Memstrack Anylazing Service.
> [ OK ] Started Memstrack Anylazing Service.
> [ OK ] Reached target Slices.
> [ OK ] Listening on udev Kernel Socket.
> [ OK ] Listening on Journal Socket (/dev/log).
> Starting Journal Service...
> Starting Create Volatile Files and Directories...
> [ OK ] Reached target Swap.
> [ OK ] Reached target Timers.
> Starting Setup Virtual Console...
> Starting Load Kernel Modules...
> [ OK ] Listening on udev Control Socket.
> [ OK ] Reached target Sockets.
> [ OK ] Started Create list of required sta…vice nodes for the current kernel.
> [ OK ] Started Create Volatile Files and Directories.
> Starting Create Static Device Nodes in /dev...
> [FAILED] Failed to start Load Kernel Modules.
> See 'systemctl status systemd-modules-load.service' for details.
> Starting Apply Kernel Variables...
> [ OK ] Started Create Static Device Nodes in /dev.
> [ OK ] Started Apply Kernel Variables.
> [ OK ] Started Journal Service.
> [ OK ] Started Setup Virtual Console.
> Starting dracut cmdline hook...
> [ OK ] Started dracut cmdline hook.
> Starting dracut pre-udev hook...
> [ 1.477216] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
> [ 1.477252] device-mapper: uevent: version 1.0.3
> [ 1.477339] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
> [ OK ] Started dracut pre-udev hook.
> Starting udev Kernel Device Manager...
> [ OK ] Started udev Kernel Device Manager.
> Starting udev Coldplug all Devices...
> Mounting Kernel Configuration File System...
> [ OK ] Mounted Kernel Configuration File System.
> [ 1.651355] synth uevent: /devices/vio: failed to send uevent
> [ 1.651365] vio vio: uevent: failed to send synthetic uevent: -19
> [ 1.651402] synth uevent: /devices/vio/4000: failed to send uevent
> [ 1.651406] vio 4000: uevent: failed to send synthetic uevent: -19
> [ 1.651415] synth uevent: /devices/vio/4001: failed to send uevent
> [ 1.651418] vio 4001: uevent: failed to send synthetic uevent: -19
> [ 1.651428] synth uevent: /devices/vio/4002: failed to send uevent
> [ 1.651431] vio 4002: uevent: failed to send synthetic uevent: -19
> [ 1.651441] synth uevent: /devices/vio/4004: failed to send uevent
> [ 1.651444] vio 4004: uevent: failed to send synthetic uevent: -19
> [ OK ] Started udev Coldplug all Devices.
> [ OK ] Reached target System Initialization.
> Starting Show Plymouth Boot Screen...
> Starting dracut initqueue hook...
> [ OK ] Started Show Plymouth Boot Screen.
> [ OK ] Started Forward Password Requests to Plymouth Directory Watch.
> [ OK ] Reached target Paths.
> [ OK ] Reached target Basic System.
> [ 1.709851] ibmveth 30000002 net0: renamed from eth0
> [ 1.712196] nvme nvme0: pci function 0019:01:00.0
> [ 1.714161] ibmvscsi 30000065: SRP_VERSION: 16.a
> [ 1.714223] ibmvscsi 30000065: Maximum ID: 64 Maximum LUN: 32 Maximum Channel: 3
> [ 1.714227] scsi host0: IBM POWER Virtual SCSI Adapter 1.5.9
> [ 1.714365] ibmvscsi 30000065: partner initialization complete
> [ 1.714391] ibmvscsi 30000065: host srp version: 16.a, host partition ltcden3-vios1 (100), OS 3, max io 524288
> [ 1.714421] ibmvscsi 30000065: Client reserve enabled
> [ 1.714426] ibmvscsi 30000065: sent SRP login
> [ 1.714448] ibmvscsi 30000065: SRP_LOGIN succeeded
> [ 1.721611] nvme nvme0: Shutdown timeout set to 8 seconds
> [ 1.737117] scsi 0:0:1:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
> [ 1.738038] scsi 0:0:2:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
> [ 1.738364] scsi 0:0:3:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
> [ 1.750754] nvme nvme0: 32/0/0 default/read/poll queues
> [ 1.754482] nvme0n1: p1 p2 p3
> [ 1.772868] scsi 0:0:1:0: Attached scsi generic sg0 type 0
> [ 1.772898] scsi 0:0:2:0: Attached scsi generic sg1 type 0
> [ 1.772920] scsi 0:0:3:0: Attached scsi generic sg2 type 0
> [ 1.794722] sd 0:0:2:0: [sda] 629145600 512-byte logical blocks: (322 GB/300 GiB)
> [ 1.794757] sd 0:0:2:0: [sda] Write Protect is off
> [ 1.794758] sd 0:0:1:0: [sdb] 209715200 512-byte logical blocks: (107 GB/100 GiB)
> [ 1.794790] sd 0:0:2:0: [sda] Cache data unavailable
> [ 1.794792] sd 0:0:1:0: [sdb] Write Protect is off
> [ 1.794796] sd 0:0:2:0: [sda] Assuming drive cache: write through
> [ 1.794826] sd 0:0:1:0: [sdb] Cache data unavailable
> [ 1.794829] sd 0:0:1:0: [sdb] Assuming drive cache: write through
> [ 1.794943] sd 0:0:3:0: [sdc] 91750400 4096-byte logical blocks: (376 GB/350 GiB)
> [ 1.794979] sd 0:0:3:0: [sdc] Write Protect is off
> [ 1.795008] sd 0:0:3:0: [sdc] Cache data unavailable
> [ 1.795011] sd 0:0:3:0: [sdc] Assuming drive cache: write through
> [ 1.796625] sdb: sdb1 sdb2 sdb3
> [ 1.796717] sdc: sdc1
> [ 1.796720] sda: sda1 sda2
> [ 1.796752] sd 0:0:1:0: [sdb] Attached SCSI disk
> [ 1.796820] sd 0:0:3:0: [sdc] Attached SCSI disk
> [ 1.796841] sd 0:0:2:0: [sda] Attached SCSI disk
> [ OK ] Found device /dev/mapper/rhel_ltcden3--lp1-root.
> [ OK ] Reached target Initrd Root Device.
> [ OK ] Started dracut initqueue hook.
> Starting File System Check on /dev/mapper/rhel_ltcden3--lp1-root...
> [ OK ] Reached target Remote File Systems (Pre).
> [ OK ] Reached target Remote File Systems.
> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
> Mounting /sysroot...
> [ 3.060638] SGI XFS with ACLs, security attributes, quota, no debug enabled
> [ 3.062369] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
> [ 3.109076] XFS (dm-0): Ending clean mount
> [ OK ] Mounted /sysroot.
> [ OK ] Reached target Initrd Root File System.
> Starting Reload Configuration from the Real Root...
> [ OK ] Started Reload Configuration from the Real Root.
> [ OK ] Reached target Initrd File Systems.
> [ OK ] Reached target Initrd Default Target.
> Starting dracut pre-pivot and cleanup hook...
> [ OK ] Started dracut pre-pivot and cleanup hook.
> Starting Cleaning Up and Shutting Down Daemons...
> [ OK ] Stopped dracut pre-pivot and cleanup hook.
> [ OK ] Stopped target Remote File Systems.
> [ OK ] Stopped target Initrd Default Target.
> [ OK ] Stopped target Timers.
> [ OK ] Stopped target Initrd Root Device.
> [ OK ] Stopped target Remote File Systems (Pre).
> [ OK ] Stopped dracut initqueue hook.
> Starting Setup Virtual Console...
> [ OK ] Stopped target Basic System.
> [ OK ] Stopped target System Initialization.
> [ OK ] Stopped Create Volatile Files and Directories.
> [ OK ] Stopped Apply Kernel Variables.
> [ OK ] Stopped udev Coldplug all Devices.
> Stopping udev Kernel Device Manager...
> [ OK ] Stopped target Swap.
> [ OK ] Stopped target Paths.
> [ OK ] Stopped target Sockets.
> [ OK ] Stopped target Slices.
> Starting Plymouth switch root service...
> [ OK ] Stopped target Local File Systems.
> [ OK ] Started Cleaning Up and Shutting Down Daemons.
> [ OK ] Started Plymouth switch root service.
> [ OK ] Started Setup Virtual Console.
> [ OK ] Stopped udev Kernel Device Manager.
> [ OK ] Stopped Create Static Device Nodes in /dev.
> [ OK ] Stopped Create list of required sta…vice nodes for the current kernel.
> Stopping Hardware RNG Entropy Gatherer Daemon...
> [ OK ] Stopped dracut pre-udev hook.
> [ OK ] Stopped dracut cmdline hook.
> [ OK ] Closed udev Control Socket.
> [ OK ] Closed udev Kernel Socket.
> Starting Cleanup udevd DB...
> [ OK ] Stopped Hardware RNG Entropy Gatherer Daemon.
> [ OK ] Started Cleanup udevd DB.
> [ OK ] Reached target Switch Root.
> Starting Switch Root...
> [ 3.449370] printk: systemd: 22 output lines suppressed due to ratelimiting
> [ 3.593463] SELinux: Runtime disable is deprecated, use selinux=0 on the kernel cmdline.
> [ 3.593471] SELinux: https://github.com/SELinuxProject/selinux-kernel/wiki/DEPRECATE-runtime-disable
> [ 19.036134] SELinux: Disabled at runtime.
> [ 19.196154] audit: type=1404 audit(1676701702.570:2): enforcing=0 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=0 old-enabled=1 lsm=selinux res=1
> [ 19.201608] systemd[1]: systemd 239 (239-58.el8) running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy)
> [ 19.201637] systemd[1]: Detected virtualization powervm.
> [ 19.201642] systemd[1]: Detected architecture ppc64-le.
>
> Welcome to Red Hat Enterprise Linux 8.6 (Ootpa)!
>
> [ 19.202637] systemd[1]: Set hostname to <ltcden3-lp1.aus.stglabs.ibm.com>.
> [ 21.777702] systemd[1]: systemd-journald.service: Succeeded.
> [ 21.778191] systemd[1]: initrd-switch-root.service: Succeeded.
> [ 21.778387] systemd[1]: Stopped Switch Root.
> [ OK ] Stopped Switch Root.
> [ 21.778748] systemd[1]: systemd-journald.service: Service has no hold-off time (RestartSec=0), scheduling restart.
> [ 21.778795] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
> [ 21.778847] systemd[1]: Stopped Journal Service.
> [ OK ] Stopped Journal Service.
> Starting Journal Service...
> [ OK ] Stopped Plymouth switch root service.
> [ OK ] Stopped target Switch Root.
> [ OK ] Listening on udev Kernel Socket.
> [ OK ] Listening on initctl Compatibility Named Pipe.
> [ OK ] Listening on Process Core Dump Socket.
> Mounting Huge Pages File System...
> Starting Load Kernel Modules...
> Starting Read and set NIS domainname from /etc/sysconfig/network...
> Activating swap /dev/mapper/rhel_ltcden3--lp1-swap...
> [ OK ] Created slice system-serial\x2dgetty.slice.
> [ OK ] Created slice system-getty.slice.
> Starting Create list of required st…ce nodes for the current kernel...
> [ OK ] Created slice User and Session Slice.
> [ OK ] Reached target Slices.
> [ OK ] Listening on RPCbind Server Activation Socket.
> [ OK ] Reached target RPC Port Mapper.
> Mounting POSIX Message Queue File System...
> [ OK ] Stopped File System Check on Root Device.
> Starting Remount Root and Kernel File Systems...
> [ OK ] Started Forward Password Requests to Wall Directory Watch.
> [ OK ] Reached target Local Encrypted Volumes.
> [ 21.912238] Adding 4194240k swap on /dev/mapper/rhel_ltcden3--lp1-swap. Priority:-2 extents:1 across:4194240k FS
> [ OK ] Listening on Device-mapper event daemon FIFOs.
> Starting Monitoring of LVM2 mirrors…ng dmeventd or progress polling...
> Starting Setup Virtual Console...
> [ OK ] Stopped target Initrd Root File System.
> Mounting Kernel Debug File System...
> [ OK ] Listening on udev Control Socket.
> Starting udev Coldplug all Devices...
> [ OK ] Created slice system-sshd\x2dkeygen.slice.
> [ OK ] Stopped target Initrd File Systems.
> [ OK ] Listening on LVM2 poll daemon socket.
> [ OK ] Activated swap /dev/mapper/rhel_ltcden3--lp1-swap.
> [ OK ] Mounted Huge Pages File System.
> [ OK ] Started Read and set NIS domainname from /etc/sysconfig/network.
> [ OK ] Started Create list of required sta…vice nodes for the current kernel.
> [ OK ] Started Journal Service.
> [ OK ] Mounted POSIX Message Queue File System.
> [ OK ] Mounted Kernel Debug File System.
> [ OK ] Reached target Swap.
> [ 22.217261] xfs filesystem being remounted at / supports timestamps until 2038 (0x7fffffff)
> [ OK ] Started Remount Root and Kernel File Systems.
> [ OK ] Started Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
> Starting Create Static Device Nodes in /dev...
> Starting Load/Save Random Seed...
> Starting Flush Journal to Persistent Storage...
> [FAILED] Failed to start Load Kernel Modules.
> See 'systemctl status systemd-modules-load.service' for details.
> Starting Apply Kernel Variables...
> [ 22.341308] synth uevent: /devices/vio: failed to send uevent
> [ 22.341317] vio vio: uevent: failed to send synthetic uevent: -19
> [ 22.341597] synth uevent: /devices/vio/4000: failed to send uevent
> [ 22.341600] vio 4000: uevent: failed to send synthetic uevent: -19
> [ 22.341610] synth uevent: /devices/vio/4001: failed to send uevent
> [ 22.341613] vio 4001: uevent: failed to send synthetic uevent: -19
> [ 22.341622] synth uevent: /devices/vio/4002: failed to send uevent
> [ 22.341625] vio 4002: uevent: failed to send synthetic uevent: -19
> [ 22.341633] synth uevent: /devices/vio/4004: failed to send uevent
> [ 22.341636] vio 4004: uevent: failed to send synthetic uevent: -19
> [ OK ] Started udev Coldplug all Devices.
> Starting udev Wait for Complete Device Initialization...
> [ OK ] Started Load/Save Random Seed.
> [ OK ] Started Flush Journal to Persistent Storage.
> [ OK ] Started Setup Virtual Console.
> [ OK ] Started Apply Kernel Variables.
> [ OK ] Started Create Static Device Nodes in /dev.
> Starting udev Kernel Device Manager...
> [ OK ] Started udev Kernel Device Manager.
> [ 24.100485] pseries_rng: Registering IBM pSeries RNG driver
> [ OK ] Created slice system-lvm2\x2dpvscan.slice.
> Starting LVM event activation on device 8:19...
> [ OK ] Started LVM event activation on device 8:19.
> [ OK ] Started udev Wait for Complete Device Initialization.
> [ OK ] Reached target Local File Systems (Pre).
> Mounting /home...
> Mounting /home2...
> Mounting /boot...
> [ 25.049055] XFS (nvme0n1p1): Mounting V5 Filesystem 31458cd5-8eb4-48b4-8f5a-112217ef59df
> [ 25.049822] XFS (dm-1): Mounting V5 Filesystem 0ac3d742-375d-4cd7-bdd2-72b0559b1957
> [ 25.050953] XFS (sdb2): Mounting V5 Filesystem c72725b8-35e3-42b4-b5cb-f8435cada964
> [ 25.055813] XFS (nvme0n1p1): Ending clean mount
> [ 25.056844] xfs filesystem being mounted at /home supports timestamps until 2038 (0x7fffffff)
> [ OK ] Mounted /home.
> [ 25.389921] XFS (dm-1): Ending clean mount
> [ 25.513566] xfs filesystem being mounted at /home2 supports timestamps until 2038 (0x7fffffff)
> [ OK ] Mounted /home2.
> [ 26.797307] XFS (sdb2): Ending clean mount
> [ 26.857340] xfs filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
> [ OK ] Mounted /boot.
> [ OK ] Reached target Local File Systems.
> Starting Tell Plymouth To Write Out Runtime Data...
> Starting Restore /run/initramfs on shutdown...
> Starting Import network configuration from initramfs...
> [ OK ] Started Restore /run/initramfs on shutdown.
> [ OK ] Started Import network configuration from initramfs.
> Starting Create Volatile Files and Directories...
> [ OK ] Started Tell Plymouth To Write Out Runtime Data.
> [ OK ] Started Create Volatile Files and Directories.
> Mounting RPC Pipe File System...
> Starting Security Auditing Service...
> Starting RPC Bind...
> [ OK ] Started RPC Bind.
> [ 27.888702] RPC: Registered named UNIX socket transport module.
> [ 27.888714] RPC: Registered udp transport module.
> [ 27.888717] RPC: Registered tcp transport module.
> [ 27.888719] RPC: Registered tcp NFSv4.1 backchannel transport module.
> [ OK ] Mounted RPC Pipe File System.
> [ OK ] Reached target rpc_pipefs.target.
> [ OK ] Started Security Auditing Service.
> Starting Update UTMP about System Boot/Shutdown...
> [ OK ] Started Update UTMP about System Boot/Shutdown.
> [ OK ] Reached target System Initialization.
> [ OK ] Listening on Open-iSCSI iscsid Socket.
> [ OK ] Listening on CUPS Scheduler.
> [ OK ] Started Run system activity accounting tool every 10 minutes.
> [ OK ] Started CUPS Scheduler.
> [ OK ] Reached target Paths.
> [ OK ] Listening on SSSD Kerberos Cache Manager responder socket.
> [ OK ] Listening on D-Bus System Message Bus Socket.
> [ OK ] Started Generate summary of yesterday's process accounting.
> [ OK ] Started daily update of the root trust anchor for DNSSEC.
> [ OK ] Started Daily Cleanup of Temporary Directories.
> [ OK ] Started dnf makecache --timer.
> [ OK ] Reached target Timers.
> [ OK ] Listening on Open-iSCSI iscsiuio Socket.
> [ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
> [ OK ] Reached target Sockets.
> [ OK ] Reached target Basic System.
> Starting NTP client/server...
> Starting Hardware RNG Entropy Gatherer Wake threshold service...
> [ OK ] Started libstoragemgmt plug-in server daemon.
> [ OK ] Started irqbalance daemon.
> Starting Resets System Activity Logs...
> Starting ppc64-diag rtas_errd (platform error handling) Service...
> Starting Self Monitoring and Reporting Technology (SMART) Daemon...
> [ OK ] Reached target sshd-keygen.target.
> Starting ABRT Automated Bug Reporting Tool...
> Starting System Security Services Daemon...
> Starting Authorization Manager...
> [ OK ] Started D-Bus System Message Bus.
> Starting Avahi mDNS/DNS-SD Stack...
> [ OK ] Started Hardware RNG Entropy Gatherer Wake threshold service.
> [ OK ] Started Hardware RNG Entropy Gatherer Daemon.
> [ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
> [ OK ] Started Resets System Activity Logs.
> [ OK ] Started ppc64-diag rtas_errd (platform error handling) Service.
> [ OK ] Started Avahi mDNS/DNS-SD Stack.
> [ OK ] Started NTP client/server.
> [ OK ] Started System Security Services Daemon.
> [ OK ] Reached target User and Group Name Lookups.
> Starting Login Service...
> [ OK ] Started Login Service.
> [ OK ] Started Authorization Manager.
> Starting firewalld - dynamic firewall daemon...
> Starting Modem Manager...
> [ OK ] Started Modem Manager.
> [ OK ] Started firewalld - dynamic firewall daemon.
> [ OK ] Reached target Network (Pre).
> Starting Network Manager...
> [ OK ] Started Network Manager.
> Starting hybrid virtual network scan and config...
> Starting Network Manager Wait Online...
> [ OK ] Reached target Network.
> Starting Enable periodic update of entitlement certificates....
> Starting CUPS Scheduler...
> Starting GSSAPI Proxy Daemon...
> Starting OpenSSH server daemon...
> Starting Logout off all iSCSI sessions on shutdown...
> [ OK ] Started Logout off all iSCSI sessions on shutdown.
> [ OK ] Started Enable periodic update of entitlement certificates..
> Starting Hostname Service...
> [ OK ] Started ABRT Automated Bug Reporting Tool.
> [ OK ] Started ABRT kernel log watcher.
> [ OK ] Started ABRT Xorg log watcher.
> [ OK ] Started Creates ABRT problems from coredumpctl messages.
> [ OK ] Started Hostname Service.
> [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
> [FAILED] Failed to start hybrid virtual network scan and config.
> See 'systemctl status hcn-init.service' for details.
> [ OK ] Started OpenSSH server daemon.
> [ OK ] Started GSSAPI Proxy Daemon.
> [ OK ] Reached target NFS client services.
> Starting Network Manager Script Dispatcher Service...
> [ OK ] Started CUPS Scheduler.
> [ OK ] Started Network Manager Script Dispatcher Service.
> [ OK ] Started Network Manager Wait Online.
> [ OK ] Reached target Network is Online.
> Starting Notify NFS peers of a restart...
> [ OK ] Reached target Remote File Systems (Pre).
> [ OK ] Reached target Remote File Systems.
> Starting Harvest vmcores for ABRT...
> Starting Permit User Sessions...
> Starting System Logging Service...
> [ OK ] Started Notify NFS peers of a restart.
> [ OK ] Started Permit User Sessions.
> [ OK ] Started Job spooling tools.
> Starting Terminate Plymouth Boot Screen...
> [ OK ] Started Command Scheduler.
> Starting Hold until boot process finishes up...
> [ OK ] Started System Logging Service.
> [ 44.801795] ------------[ cut here ]------------
> [ 44.801810] WARNING: CPU: 24 PID: 1906 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
> [ 44.801895] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set rfkill nf_tables nfnetlink sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi nvme ibmveth scsi_transport_srp nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
> [ 44.801926] CPU: 24 PID: 1906 Comm: in:imjournal Not tainted 6.2.0-rc8ssh #35
> [ 44.801930] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> [ 44.801933] NIP: c00800000062fa80 LR: c00800000062fa4c CTR: c000000000ea4d40
> [ 44.801936] REGS: c00000001984b690 TRAP: 0700 Not tainted (6.2.0-rc8ssh)
> [ 44.801939] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24224842 XER: 00000000
> [ 44.801947] CFAR: c00800000062fa54 IRQMASK: 0
> [ 44.801947] GPR00: c0000000091cbec8 c00000001984b930 c0080000006d8300 0000000000000000
> [ 44.801947] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000051aa4d90
> [ 44.801947] GPR08: 0000000000000000 c000000051aa4e40 0000000000000000 fffffffffffffffd
> [ 44.801947] GPR12: 0000000000000040 c000004afece5880 0000000000000000 0000000004000000
> [ 44.801947] GPR16: c00000001984bb38 c00000001984ba38 c00000001984ba68 c00000002c323c00
> [ 44.801947] GPR20: c0000000091cbe00 0000000000008000 c0000000516e5800 00000000002ec44d
> [ 44.801947] GPR24: 000000000030af4d 000000000000000d c000000008d71680 00000000002ec44d
> [ 44.801947] GPR28: c00000002c322400 c0000000091cbe00 c000000054c05618 000000000030af4d
> [ 44.801983] NIP [c00800000062fa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
> [ 44.802037] LR [c00800000062fa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
> [ 44.802090] Call Trace:
> [ 44.802091] [c00000001984b930] [c000000054c05618] 0xc000000054c05618 (unreliable)
> [ 44.802096] [c00000001984b950] [c008000000630094] xfs_iunlink+0x1bc/0x280 [xfs]
> [ 44.802149] [c00000001984b9d0] [c008000000634754] xfs_rename+0x69c/0xd10 [xfs]
> [ 44.802202] [c00000001984bb10] [c00800000062e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
> [ 44.802255] [c00000001984bba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
> [ 44.802261] [c00000001984bc90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
> [ 44.802265] [c00000001984bde0] [c000000000580520] sys_rename+0x60/0x80
> [ 44.802269] [c00000001984be10] [c000000000033630] system_call_exception+0x150/0x3b0
> [ 44.802274] [c00000001984be50] [c00000000000c554] system_call_common+0xf4/0x258
> [ 44.802280] --- interrupt: c00 at 0x7fffa6482e20
> [ 44.802282] NIP: 00007fffa6482e20 LR: 00007fffa6055e24 CTR: 0000000000000000
> [ 44.802285] REGS: c00000001984be80 TRAP: 0c00 Not tainted (6.2.0-rc8ssh)
> [ 44.802288] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
> [ 44.802297] IRQMASK: 0
> [ 44.802297] GPR00: 0000000000000026 00007fffa536d220 00007fffa6607300 00007fffa536d288
> [ 44.802297] GPR04: 000000014f7a6b70 0000000000000000 0700000000000000 0000000000000002
> [ 44.802297] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> [ 44.802297] GPR12: 0000000000000000 00007fffa53766e0 000000014f795930 0000000000000000
> [ 44.802297] GPR16: 0000000126b67648 00007fffa6057ce0 0000000000000003 000000000000002b
> [ 44.802297] GPR20: 0000000000000212 00007fffa536e3a0 00007fffa536e398 00007fff98008690
> [ 44.802297] GPR24: 0000000000000000 00007fffa536e388 00007fffa536e378 00007fffa536e3b0
> [ 44.802297] GPR28: 00007fffa6070000 00007fffa60705e0 00007fff98000c10 00007fffa536d288
> [ 44.802331] NIP [00007fffa6482e20] 0x7fffa6482e20
> [ 44.802334] LR [00007fffa6055e24] 0x7fffa6055e24
> [ 44.802336] --- interrupt: c00
> [ 44.802338] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
> [ 44.802352] ---[ end trace 0000000000000000 ]---
> [ 44.802356] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x9cc/0xd10 [xfs]
> [ 44.802412] CPU: 24 PID: 1906 Comm: in:imjournal Tainted: G W 6.2.0-rc8ssh #35
> [ 44.802415] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> [ 44.802418] Call Trace:
> [ 44.802420] [c00000001984b8f0] [c000000000e87328] dump_stack_lvl+0x6c/0x9c (unreliable)
> [ 44.802425] [c00000001984b920] [c008000000616a84] xfs_error_report+0x5c/0x80 [xfs]
> [ 44.802478] [c00000001984b980] [c0080000006467b0] xfs_trans_cancel+0x178/0x1b0 [xfs]
> [ 44.802533] [c00000001984b9d0] [c008000000634a84] xfs_rename+0x9cc/0xd10 [xfs]
> [ 44.802586] [c00000001984bb10] [c00800000062e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
> [ 44.802641] [c00000001984bba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
> [ 44.802644] [c00000001984bc90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
> [ 44.802648] [c00000001984bde0] [c000000000580520] sys_rename+0x60/0x80
> [ 44.802652] [c00000001984be10] [c000000000033630] system_call_exception+0x150/0x3b0
> [ 44.802657] [c00000001984be50] [c00000000000c554] system_call_common+0xf4/0x258
> [ 44.802661] --- interrupt: c00 at 0x7fffa6482e20
> [ 44.802664] NIP: 00007fffa6482e20 LR: 00007fffa6055e24 CTR: 0000000000000000
> [ 44.802667] REGS: c00000001984be80 TRAP: 0c00 Tainted: G W (6.2.0-rc8ssh)
> [ 44.802670] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
> [ 44.802678] IRQMASK: 0
> [ 44.802678] GPR00: 0000000000000026 00007fffa536d220 00007fffa6607300 00007fffa536d288
> [ 44.802678] GPR04: 000000014f7a6b70 0000000000000000 0700000000000000 0000000000000002
> [ 44.802678] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> [ 44.802678] GPR12: 0000000000000000 00007fffa53766e0 000000014f795930 0000000000000000
> [ 44.802678] GPR16: 0000000126b67648 00007fffa6057ce0 0000000000000003 000000000000002b
> [ 44.802678] GPR20: 0000000000000212 00007fffa536e3a0 00007fffa536e398 00007fff98008690
> [ 44.802678] GPR24: 0000000000000000 00007fffa536e388 00007fffa536e378 00007fffa536e3b0
> [ 44.802678] GPR28: 00007fffa6070000 00007fffa60705e0 00007fff98000c10 00007fffa536d288
> [ 44.802712] NIP [00007fffa6482e20] 0x7fffa6482e20
> [ 44.802715] LR [00007fffa6055e24] 0x7fffa6055e24
> [ 44.802717] --- interrupt: c00
> [ 44.804354] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
> [ 44.804413] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
>
>
>
> >> [ 333.390615] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
> >> [ 333.390645] CPU: 56 PID: 12450 Comm: rm Not tainted 6.2.0-rc4ssh+ #4
> >> [ 333.390649] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> >> [ 333.390652] NIP: c0080000004bfa80 LR: c0080000004bfa4c CTR: c000000000ea28d0
> >> [ 333.390655] REGS: c0000000442bb8c0 TRAP: 0700 Not tainted (6.2.0-rc4ssh+)
> >> [ 333.390658] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24002842 XER: 00000000
> >> [ 333.390666] CFAR: c0080000004bfa54 IRQMASK: 0
> >> [ 333.390666] GPR00: c00000003b69c0c8 c0000000442bbb60 c008000000568300 0000000000000000
> >> [ 333.390666] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000004b27d78
> >> [ 333.390666] GPR08: 0000000000000000 c000000004b27e28 0000000000000000 fffffffffffffffd
> >> [ 333.390666] GPR12: 0000000000000040 c000004afecc5880 0000000106620918 0000000000000001
> >> [ 333.390666] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
> >> [ 333.390666] GPR20: 0000000106620e30 c0000000880ba938 0000000000200000 00000000002ec44d
> >> [ 333.390666] GPR24: 000000000008170d 000000000000000d c0000000519f4800 00000000002ec44d
> >> [ 333.390666] GPR28: c0000000880ba800 c00000003b69c000 c0000000833edd20 000000000008170d
> >> [ 333.390702] NIP [c0080000004bfa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
> >> [ 333.390756] LR [c0080000004bfa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
> >> [ 333.390810] Call Trace:
> >> [ 333.390811] [c0000000442bbb60] [c0000000833edd20] 0xc0000000833edd20 (unreliable)
> >> [ 333.390816] [c0000000442bbb80] [c0080000004c0094] xfs_iunlink+0x1bc/0x280 [xfs]
> >> [ 333.390869] [c0000000442bbc00] [c0080000004c3f84] xfs_remove+0x1dc/0x310 [xfs]
> >> [ 333.390922] [c0000000442bbc70] [c0080000004be180] xfs_vn_unlink+0x68/0xf0 [xfs]
> >> [ 333.390975] [c0000000442bbcd0] [c000000000576b24] vfs_unlink+0x1b4/0x3d0
> >
> > ...that trips when rm tries to remove a file, which means that the call
> > stack is
> >
> > xfs_remove -> xfs_iunlink -> xfs_iunlink_insert_inode ->
> > xfs_iunlink_update_backref -> xfs_iunlink_lookup <kaboom>
> >
> > It looks as though "rm foo" unlinked foo from the directory and was
> > trying to insert it at the head of one of the unlinked lists in the AGI
> > buffer. The AGI claims that the list points to an ondisk inode, so the
> > iunlink code tries to find the incore inode to update the incore list,
> > fails to find an incore inode, and this is the result...
>
> This seems to happen for rename as well. i.e xfs_rename.
> Does rename path calls rm first, and then create?
Effectively, yes. A "mv a b" will unlink b, and that calls the same
internal unlink code as an unlink syscall.
> >>
> >>
> >> we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
> >> as the bad commit.
> >> Short description of commit:
> >> commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad)
> >> Author: Dave Chinner <dchinner@redhat.com>
> >> Date: Thu Jul 14 11:42:39 2022 +1000
> >>
> >> xfs: refactor xlog_recover_process_iunlinks()
> >
> > ...which was in the middle of the series that reworked thev mount time
> > iunlink clearing. Oddly, I don't spot any obvious errors in /that/
> > patch that didn't already exist. But this does make me wonder, does
> > xfs_repair -n have anything to say about unlinked or orphaned inodes?
> >
> > The runtime code expects that every ondisk inode in an iunlink chain has
> > an incore inode that is linked (via i_{next,prev}_unlinked) to the other
> > incore inodes in that same chain. If this requirement is not met, then
> > the WARNings you see will trip, and the fs shuts down.
> >
> > My hypothesis here is that one of the AGs has an unprocessed unlinked
> > list. At mount time, the ondisk log was clean, so mount time log
> > recovery didn't invoke xlog_recover_process_iunlinks, and the list was
> > not cleared. The mount code does not construct the incore unlinked list
> > from an existing ondisk iunlink list, hence the WARNing. Prior to 5.17,
> > we only manipulated the ondisk unlink list, and the code never noticed
> > or cared if there were mystery inodes in the list that never went away.
> >
> > (Obviously, if something blew up earlier in dmesg, that would be
> > relevant here.)
> >
> > It's possible that we could end up in this situation (clean log,
> > unlinked inodes) if a previous log recovery was only partially
> > successful at clearing the unlinked list, since all that code ignores
> > errors. If that happens, we ... succeed at mounting and clean the log.
> >
> > If you're willing to patch your kernels, it would be interesting
> > to printk if the xfs_read_agi or the xlog_recover_iunlink_bucket calls
> > in xlog_recover_iunlink_ag returns an error code. It might be too late
>
> We can try. Please provide the Patch.
>
> > to capture that, hence my suggestion of seeing if xfs_repair -n will
> > tell us anything else.
> >
>
> Could you please clarify? We should run xfs_repair -n from 5.17-rc2 kernel?
Whatever xfs_repair is installed on the system should suffice to report
an unlinked inode list and any other errors on the filesystem. That
evidence will guide us towards a kernel patch.
--D
>
> > I've long thought that the iunlink recovery ought to complain loudly and
> > fail the mount if it can't clear all the unlinked files. Given the new
> > iunlink design, I think it's pretty much required now. The uglier piece
> > is that now we either (a) have to clear iunlinks at mount time
> > unconditionally as Eric has been saying for years; or (b) construct the
> > incore list at a convenient time so that the incore list always exists.
> >
> > Thanks for the detailed report!
> >
> > --D
> >
> >>
> >> Git bisect log:
> >> git bisect start
> >> # good: [26291c54e111ff6ba87a164d85d4a4e134b7315c] Linux 5.17-rc2
> >> git bisect good 26291c54e111ff6ba87a164d85d4a4e134b7315c
> >> # bad: [4fe89d07dcc2804c8b562f6c7896a45643d34b2f] Linux 6.0
> >> git bisect bad 4fe89d07dcc2804c8b562f6c7896a45643d34b2f
> >> # good: [d7227785e384d4422b3ca189aa5bf19f462337cc] Merge tag 'sound-5.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
> >> git bisect good d7227785e384d4422b3ca189aa5bf19f462337cc
> >> # good: [526942b8134cc34d25d27f95dfff98b8ce2f6fcd] Merge tag 'ata-5.20-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
> >> git bisect good 526942b8134cc34d25d27f95dfff98b8ce2f6fcd
> >> # good: [328141e51e6fc79d21168bfd4e356dddc2ec7491] Merge tag 'mmc-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
> >> git bisect good 328141e51e6fc79d21168bfd4e356dddc2ec7491
> >> # bad: [eb555cb5b794f4e12a9897f3d46d5a72104cd4a7] Merge tag '5.20-rc-ksmbd-server-fixes' of git://git.samba.org/ksmbd
> >> git bisect bad eb555cb5b794f4e12a9897f3d46d5a72104cd4a7
> >> # bad: [f20c95b46b8fa3ad34b3ea2e134337f88591468b] Merge tag 'tpmdd-next-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd
> >> git bisect bad f20c95b46b8fa3ad34b3ea2e134337f88591468b
> >> # bad: [fad235ed4338749a66ddf32971d4042b9ef47f44] Merge tag 'arm-late-6.0' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
> >> git bisect bad fad235ed4338749a66ddf32971d4042b9ef47f44
> >> # good: [e495274793ea602415d050452088a496abcd9e6c] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
> >> git bisect good e495274793ea602415d050452088a496abcd9e6c
> >> # good: [9daee913dc8d15eb65e0ff560803ab1c28bb480b] Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
> >> git bisect good 9daee913dc8d15eb65e0ff560803ab1c28bb480b
> >> # bad: [29b1d469f3f6842ee4115f0b21f018fc44176468] Merge tag 'trace-rtla-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
> >> git bisect bad 29b1d469f3f6842ee4115f0b21f018fc44176468
> >> # good: [932b42c66cb5d0ca9800b128415b4ad6b1952b3e] xfs: replace XFS_IFORK_Q with a proper predicate function
> >> git bisect good 932b42c66cb5d0ca9800b128415b4ad6b1952b3e
> >> # bad: [35c5a09f5346e690df7ff2c9075853e340ee10b3] Merge tag 'xfs-buf-lockless-lookup-5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs into xfs-5.20-mergeB
> >> git bisect bad 35c5a09f5346e690df7ff2c9075853e340ee10b3
> >> # bad: [fad743d7cd8bd92d03c09e71f29eace860f50415] xfs: add log item precommit operation
> >> git bisect bad fad743d7cd8bd92d03c09e71f29eace860f50415
> >> # bad: [04755d2e5821b3afbaadd09fe5df58d04de36484] xfs: refactor xlog_recover_process_iunlinks()
> >> git bisect bad 04755d2e5821b3afbaadd09fe5df58d04de36484
> >> # good: [a4454cd69c66bf3e3bbda352b049732f836fc6b2] xfs: factor the xfs_iunlink functions
> >> git bisect good a4454cd69c66bf3e3bbda352b049732f836fc6b2
> >> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> >> [4fcc94d653270fcc7800dbaf3b11f78cb462b293] xfs: track the iunlink list pointer in the xfs_inode
> >>
> >>
> >> Please reach out, in case any more details are needed. sent with very limited
> >> knowledge of xfs system. these logs are from 5.19 kernel.
> >>
> >> # xfs_info /home
> >> meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=13107200 blks
> >> = sectsz=4096 attr=2, projid32bit=1
> >> = crc=1 finobt=1, sparse=1, rmapbt=0
> >> = reflink=1 bigtime=0 inobtcount=0
> >> data = bsize=4096 blocks=52428800, imaxpct=25
> >> = sunit=0 swidth=0 blks
> >> naming =version 2 bsize=4096 ascii-ci=0, ftype=1
> >> log =internal log bsize=4096 blocks=25600, version=2
> >> = sectsz=4096 sunit=1 blks, lazy-count=1
> >> realtime =none extsz=4096 blocks=0, rtextents=0
> >>
> >> # xfs_info -V
> >> xfs_info version 5.0.0
> >>
> >> # uname -a
> >> 5.19.0-rc2
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-02-22 16:41 ` Darrick J. Wong
@ 2023-02-24 8:04 ` shrikanth hegde
2023-02-24 21:18 ` Darrick J. Wong
2023-03-09 14:26 ` Ritesh Harjani
1 sibling, 1 reply; 28+ messages in thread
From: shrikanth hegde @ 2023-02-24 8:04 UTC (permalink / raw)
To: Darrick J. Wong; +Cc: dchinner, linux-xfs, Srikar Dronamraju, ojaswin
>>> ...that trips when rm tries to remove a file, which means that the call
>>> stack is
>>>
>>> xfs_remove -> xfs_iunlink -> xfs_iunlink_insert_inode ->
>>> xfs_iunlink_update_backref -> xfs_iunlink_lookup <kaboom>
>>>
>>> It looks as though "rm foo" unlinked foo from the directory and was
>>> trying to insert it at the head of one of the unlinked lists in the AGI
>>> buffer. The AGI claims that the list points to an ondisk inode, so the
>>> iunlink code tries to find the incore inode to update the incore list,
>>> fails to find an incore inode, and this is the result...
>>
>> This seems to happen for rename as well. i.e xfs_rename.
>> Does rename path calls rm first, and then create?
>
> Effectively, yes. A "mv a b" will unlink b, and that calls the same
> internal unlink code as an unlink syscall.
>
>>>>
>>>>
>>>> we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
>>>> as the bad commit.
>>>> Short description of commit:
>>>> commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad)
>>>> Author: Dave Chinner <dchinner@redhat.com>
>>>> Date: Thu Jul 14 11:42:39 2022 +1000
>>>>
>>>> xfs: refactor xlog_recover_process_iunlinks()
>>>
>>> ...which was in the middle of the series that reworked thev mount time
>>> iunlink clearing. Oddly, I don't spot any obvious errors in /that/
>>> patch that didn't already exist. But this does make me wonder, does
>>> xfs_repair -n have anything to say about unlinked or orphaned inodes?
>>>
>>> The runtime code expects that every ondisk inode in an iunlink chain has
>>> an incore inode that is linked (via i_{next,prev}_unlinked) to the other
>>> incore inodes in that same chain. If this requirement is not met, then
>>> the WARNings you see will trip, and the fs shuts down.
>>>
>>> My hypothesis here is that one of the AGs has an unprocessed unlinked
>>> list. At mount time, the ondisk log was clean, so mount time log
>>> recovery didn't invoke xlog_recover_process_iunlinks, and the list was
>>> not cleared. The mount code does not construct the incore unlinked list
>>> from an existing ondisk iunlink list, hence the WARNing. Prior to 5.17,
>>> we only manipulated the ondisk unlink list, and the code never noticed
>>> or cared if there were mystery inodes in the list that never went away.
>>>
>>> (Obviously, if something blew up earlier in dmesg, that would be
>>> relevant here.)
>>>
>>> It's possible that we could end up in this situation (clean log,
>>> unlinked inodes) if a previous log recovery was only partially
>>> successful at clearing the unlinked list, since all that code ignores
>>> errors. If that happens, we ... succeed at mounting and clean the log.
>>>
>>> If you're willing to patch your kernels, it would be interesting
>>> to printk if the xfs_read_agi or the xlog_recover_iunlink_bucket calls
>>> in xlog_recover_iunlink_ag returns an error code. It might be too late
>>
>> We can try. Please provide the Patch.
>>
>>> to capture that, hence my suggestion of seeing if xfs_repair -n will
>>> tell us anything else.
>>>
>>
>> Could you please clarify? We should run xfs_repair -n from 5.17-rc2 kernel?
>
> Whatever xfs_repair is installed on the system should suffice to report
> an unlinked inode list and any other errors on the filesystem. That
> evidence will guide us towards a kernel patch.
>
> --D
>
# xfs_info /
meta-data=/dev/mapper/rhel_ltc--lp1-root isize=512 agcount=4, agsize=4183040 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1 bigtime=0 inobtcount=0
data = bsize=4096 blocks=16732160, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=8170, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
#
#
# xfs_repair -n /
xfs_repair: can't determine device size
#
>>
>>> I've long thought that the iunlink recovery ought to complain loudly and
>>> fail the mount if it can't clear all the unlinked files. Given the new
>>> iunlink design, I think it's pretty much required now. The uglier piece
>>> is that now we either (a) have to clear iunlinks at mount time
>>> unconditionally as Eric has been saying for years; or (b) construct the
>>> incore list at a convenient time so that the incore list always exists.
>>>
>>> Thanks for the detailed report!
>>>
>>> --D
>>>
>>>>
>>>> Git bisect log:
>>>> git bisect start
>>>> # good: [26291c54e111ff6ba87a164d85d4a4e134b7315c] Linux 5.17-rc2
>>>> git bisect good 26291c54e111ff6ba87a164d85d4a4e134b7315c
>>>> # bad: [4fe89d07dcc2804c8b562f6c7896a45643d34b2f] Linux 6.0
>>>> git bisect bad 4fe89d07dcc2804c8b562f6c7896a45643d34b2f
>>>> # good: [d7227785e384d4422b3ca189aa5bf19f462337cc] Merge tag 'sound-5.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
>>>> git bisect good d7227785e384d4422b3ca189aa5bf19f462337cc
>>>> # good: [526942b8134cc34d25d27f95dfff98b8ce2f6fcd] Merge tag 'ata-5.20-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
>>>> git bisect good 526942b8134cc34d25d27f95dfff98b8ce2f6fcd
>>>> # good: [328141e51e6fc79d21168bfd4e356dddc2ec7491] Merge tag 'mmc-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
>>>> git bisect good 328141e51e6fc79d21168bfd4e356dddc2ec7491
>>>> # bad: [eb555cb5b794f4e12a9897f3d46d5a72104cd4a7] Merge tag '5.20-rc-ksmbd-server-fixes' of git://git.samba.org/ksmbd
>>>> git bisect bad eb555cb5b794f4e12a9897f3d46d5a72104cd4a7
>>>> # bad: [f20c95b46b8fa3ad34b3ea2e134337f88591468b] Merge tag 'tpmdd-next-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd
>>>> git bisect bad f20c95b46b8fa3ad34b3ea2e134337f88591468b
>>>> # bad: [fad235ed4338749a66ddf32971d4042b9ef47f44] Merge tag 'arm-late-6.0' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
>>>> git bisect bad fad235ed4338749a66ddf32971d4042b9ef47f44
>>>> # good: [e495274793ea602415d050452088a496abcd9e6c] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
>>>> git bisect good e495274793ea602415d050452088a496abcd9e6c
>>>> # good: [9daee913dc8d15eb65e0ff560803ab1c28bb480b] Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
>>>> git bisect good 9daee913dc8d15eb65e0ff560803ab1c28bb480b
>>>> # bad: [29b1d469f3f6842ee4115f0b21f018fc44176468] Merge tag 'trace-rtla-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
>>>> git bisect bad 29b1d469f3f6842ee4115f0b21f018fc44176468
>>>> # good: [932b42c66cb5d0ca9800b128415b4ad6b1952b3e] xfs: replace XFS_IFORK_Q with a proper predicate function
>>>> git bisect good 932b42c66cb5d0ca9800b128415b4ad6b1952b3e
>>>> # bad: [35c5a09f5346e690df7ff2c9075853e340ee10b3] Merge tag 'xfs-buf-lockless-lookup-5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs into xfs-5.20-mergeB
>>>> git bisect bad 35c5a09f5346e690df7ff2c9075853e340ee10b3
>>>> # bad: [fad743d7cd8bd92d03c09e71f29eace860f50415] xfs: add log item precommit operation
>>>> git bisect bad fad743d7cd8bd92d03c09e71f29eace860f50415
>>>> # bad: [04755d2e5821b3afbaadd09fe5df58d04de36484] xfs: refactor xlog_recover_process_iunlinks()
>>>> git bisect bad 04755d2e5821b3afbaadd09fe5df58d04de36484
>>>> # good: [a4454cd69c66bf3e3bbda352b049732f836fc6b2] xfs: factor the xfs_iunlink functions
>>>> git bisect good a4454cd69c66bf3e3bbda352b049732f836fc6b2
>>>> Bisecting: 0 revisions left to test after this (roughly 0 steps)
>>>> [4fcc94d653270fcc7800dbaf3b11f78cb462b293] xfs: track the iunlink list pointer in the xfs_inode
>>>>
>>>>
>>>> Please reach out, in case any more details are needed. sent with very limited
>>>> knowledge of xfs system. these logs are from 5.19 kernel.
>>>>
>>>> # xfs_info /home
>>>> meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=13107200 blks
>>>> = sectsz=4096 attr=2, projid32bit=1
>>>> = crc=1 finobt=1, sparse=1, rmapbt=0
>>>> = reflink=1 bigtime=0 inobtcount=0
>>>> data = bsize=4096 blocks=52428800, imaxpct=25
>>>> = sunit=0 swidth=0 blks
>>>> naming =version 2 bsize=4096 ascii-ci=0, ftype=1
>>>> log =internal log bsize=4096 blocks=25600, version=2
>>>> = sectsz=4096 sunit=1 blks, lazy-count=1
>>>> realtime =none extsz=4096 blocks=0, rtextents=0
>>>>
>>>> # xfs_info -V
>>>> xfs_info version 5.0.0
>>>>
>>>> # uname -a
>>>> 5.19.0-rc2
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-02-24 8:04 ` shrikanth hegde
@ 2023-02-24 21:18 ` Darrick J. Wong
0 siblings, 0 replies; 28+ messages in thread
From: Darrick J. Wong @ 2023-02-24 21:18 UTC (permalink / raw)
To: shrikanth hegde; +Cc: dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On Fri, Feb 24, 2023 at 01:34:01PM +0530, shrikanth hegde wrote:
>
> >>> ...that trips when rm tries to remove a file, which means that the call
> >>> stack is
> >>>
> >>> xfs_remove -> xfs_iunlink -> xfs_iunlink_insert_inode ->
> >>> xfs_iunlink_update_backref -> xfs_iunlink_lookup <kaboom>
> >>>
> >>> It looks as though "rm foo" unlinked foo from the directory and was
> >>> trying to insert it at the head of one of the unlinked lists in the AGI
> >>> buffer. The AGI claims that the list points to an ondisk inode, so the
> >>> iunlink code tries to find the incore inode to update the incore list,
> >>> fails to find an incore inode, and this is the result...
> >>
> >> This seems to happen for rename as well. i.e xfs_rename.
> >> Does rename path calls rm first, and then create?
> >
> > Effectively, yes. A "mv a b" will unlink b, and that calls the same
> > internal unlink code as an unlink syscall.
> >
> >>>>
> >>>>
> >>>> we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
> >>>> as the bad commit.
> >>>> Short description of commit:
> >>>> commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad)
> >>>> Author: Dave Chinner <dchinner@redhat.com>
> >>>> Date: Thu Jul 14 11:42:39 2022 +1000
> >>>>
> >>>> xfs: refactor xlog_recover_process_iunlinks()
> >>>
> >>> ...which was in the middle of the series that reworked thev mount time
> >>> iunlink clearing. Oddly, I don't spot any obvious errors in /that/
> >>> patch that didn't already exist. But this does make me wonder, does
> >>> xfs_repair -n have anything to say about unlinked or orphaned inodes?
> >>>
> >>> The runtime code expects that every ondisk inode in an iunlink chain has
> >>> an incore inode that is linked (via i_{next,prev}_unlinked) to the other
> >>> incore inodes in that same chain. If this requirement is not met, then
> >>> the WARNings you see will trip, and the fs shuts down.
> >>>
> >>> My hypothesis here is that one of the AGs has an unprocessed unlinked
> >>> list. At mount time, the ondisk log was clean, so mount time log
> >>> recovery didn't invoke xlog_recover_process_iunlinks, and the list was
> >>> not cleared. The mount code does not construct the incore unlinked list
> >>> from an existing ondisk iunlink list, hence the WARNing. Prior to 5.17,
> >>> we only manipulated the ondisk unlink list, and the code never noticed
> >>> or cared if there were mystery inodes in the list that never went away.
> >>>
> >>> (Obviously, if something blew up earlier in dmesg, that would be
> >>> relevant here.)
> >>>
> >>> It's possible that we could end up in this situation (clean log,
> >>> unlinked inodes) if a previous log recovery was only partially
> >>> successful at clearing the unlinked list, since all that code ignores
> >>> errors. If that happens, we ... succeed at mounting and clean the log.
> >>>
> >>> If you're willing to patch your kernels, it would be interesting
> >>> to printk if the xfs_read_agi or the xlog_recover_iunlink_bucket calls
> >>> in xlog_recover_iunlink_ag returns an error code. It might be too late
> >>
> >> We can try. Please provide the Patch.
> >>
> >>> to capture that, hence my suggestion of seeing if xfs_repair -n will
> >>> tell us anything else.
> >>>
> >>
> >> Could you please clarify? We should run xfs_repair -n from 5.17-rc2 kernel?
> >
> > Whatever xfs_repair is installed on the system should suffice to report
> > an unlinked inode list and any other errors on the filesystem. That
> > evidence will guide us towards a kernel patch.
> >
> > --D
> >
>
> # xfs_info /
> meta-data=/dev/mapper/rhel_ltc--lp1-root isize=512 agcount=4, agsize=4183040 blks
> = sectsz=512 attr=2, projid32bit=1
> = crc=1 finobt=1, sparse=1, rmapbt=0
> = reflink=1 bigtime=0 inobtcount=0
> data = bsize=4096 blocks=16732160, imaxpct=25
> = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0, ftype=1
> log =internal log bsize=4096 blocks=8170, version=2
> = sectsz=512 sunit=0 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
> #
> #
> # xfs_repair -n /
> xfs_repair: can't determine device size
xfs_repair takes a path to a block device.
--D
>
> >>
> >>> I've long thought that the iunlink recovery ought to complain loudly and
> >>> fail the mount if it can't clear all the unlinked files. Given the new
> >>> iunlink design, I think it's pretty much required now. The uglier piece
> >>> is that now we either (a) have to clear iunlinks at mount time
> >>> unconditionally as Eric has been saying for years; or (b) construct the
> >>> incore list at a convenient time so that the incore list always exists.
> >>>
> >>> Thanks for the detailed report!
> >>>
> >>> --D
> >>>
> >>>>
> >>>> Git bisect log:
> >>>> git bisect start
> >>>> # good: [26291c54e111ff6ba87a164d85d4a4e134b7315c] Linux 5.17-rc2
> >>>> git bisect good 26291c54e111ff6ba87a164d85d4a4e134b7315c
> >>>> # bad: [4fe89d07dcc2804c8b562f6c7896a45643d34b2f] Linux 6.0
> >>>> git bisect bad 4fe89d07dcc2804c8b562f6c7896a45643d34b2f
> >>>> # good: [d7227785e384d4422b3ca189aa5bf19f462337cc] Merge tag 'sound-5.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
> >>>> git bisect good d7227785e384d4422b3ca189aa5bf19f462337cc
> >>>> # good: [526942b8134cc34d25d27f95dfff98b8ce2f6fcd] Merge tag 'ata-5.20-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
> >>>> git bisect good 526942b8134cc34d25d27f95dfff98b8ce2f6fcd
> >>>> # good: [328141e51e6fc79d21168bfd4e356dddc2ec7491] Merge tag 'mmc-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
> >>>> git bisect good 328141e51e6fc79d21168bfd4e356dddc2ec7491
> >>>> # bad: [eb555cb5b794f4e12a9897f3d46d5a72104cd4a7] Merge tag '5.20-rc-ksmbd-server-fixes' of git://git.samba.org/ksmbd
> >>>> git bisect bad eb555cb5b794f4e12a9897f3d46d5a72104cd4a7
> >>>> # bad: [f20c95b46b8fa3ad34b3ea2e134337f88591468b] Merge tag 'tpmdd-next-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd
> >>>> git bisect bad f20c95b46b8fa3ad34b3ea2e134337f88591468b
> >>>> # bad: [fad235ed4338749a66ddf32971d4042b9ef47f44] Merge tag 'arm-late-6.0' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
> >>>> git bisect bad fad235ed4338749a66ddf32971d4042b9ef47f44
> >>>> # good: [e495274793ea602415d050452088a496abcd9e6c] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
> >>>> git bisect good e495274793ea602415d050452088a496abcd9e6c
> >>>> # good: [9daee913dc8d15eb65e0ff560803ab1c28bb480b] Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
> >>>> git bisect good 9daee913dc8d15eb65e0ff560803ab1c28bb480b
> >>>> # bad: [29b1d469f3f6842ee4115f0b21f018fc44176468] Merge tag 'trace-rtla-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
> >>>> git bisect bad 29b1d469f3f6842ee4115f0b21f018fc44176468
> >>>> # good: [932b42c66cb5d0ca9800b128415b4ad6b1952b3e] xfs: replace XFS_IFORK_Q with a proper predicate function
> >>>> git bisect good 932b42c66cb5d0ca9800b128415b4ad6b1952b3e
> >>>> # bad: [35c5a09f5346e690df7ff2c9075853e340ee10b3] Merge tag 'xfs-buf-lockless-lookup-5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs into xfs-5.20-mergeB
> >>>> git bisect bad 35c5a09f5346e690df7ff2c9075853e340ee10b3
> >>>> # bad: [fad743d7cd8bd92d03c09e71f29eace860f50415] xfs: add log item precommit operation
> >>>> git bisect bad fad743d7cd8bd92d03c09e71f29eace860f50415
> >>>> # bad: [04755d2e5821b3afbaadd09fe5df58d04de36484] xfs: refactor xlog_recover_process_iunlinks()
> >>>> git bisect bad 04755d2e5821b3afbaadd09fe5df58d04de36484
> >>>> # good: [a4454cd69c66bf3e3bbda352b049732f836fc6b2] xfs: factor the xfs_iunlink functions
> >>>> git bisect good a4454cd69c66bf3e3bbda352b049732f836fc6b2
> >>>> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> >>>> [4fcc94d653270fcc7800dbaf3b11f78cb462b293] xfs: track the iunlink list pointer in the xfs_inode
> >>>>
> >>>>
> >>>> Please reach out, in case any more details are needed. sent with very limited
> >>>> knowledge of xfs system. these logs are from 5.19 kernel.
> >>>>
> >>>> # xfs_info /home
> >>>> meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=13107200 blks
> >>>> = sectsz=4096 attr=2, projid32bit=1
> >>>> = crc=1 finobt=1, sparse=1, rmapbt=0
> >>>> = reflink=1 bigtime=0 inobtcount=0
> >>>> data = bsize=4096 blocks=52428800, imaxpct=25
> >>>> = sunit=0 swidth=0 blks
> >>>> naming =version 2 bsize=4096 ascii-ci=0, ftype=1
> >>>> log =internal log bsize=4096 blocks=25600, version=2
> >>>> = sectsz=4096 sunit=1 blks, lazy-count=1
> >>>> realtime =none extsz=4096 blocks=0, rtextents=0
> >>>>
> >>>> # xfs_info -V
> >>>> xfs_info version 5.0.0
> >>>>
> >>>> # uname -a
> >>>> 5.19.0-rc2
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-02-22 16:41 ` Darrick J. Wong
2023-02-24 8:04 ` shrikanth hegde
@ 2023-03-09 14:26 ` Ritesh Harjani
2023-03-09 17:27 ` Darrick J. Wong
2023-03-10 0:29 ` Dave Chinner
1 sibling, 2 replies; 28+ messages in thread
From: Ritesh Harjani @ 2023-03-09 14:26 UTC (permalink / raw)
To: Darrick J. Wong, shrikanth hegde
Cc: dchinner, linux-xfs, Srikar Dronamraju, ojaswin
"Darrick J. Wong" <djwong@kernel.org> writes:
> On Sat, Feb 18, 2023 at 12:47:48PM +0530, shrikanth hegde wrote:
>>
>>
>> On 2/17/23 10:23 PM, Darrick J. Wong wrote:
>> > On Fri, Feb 17, 2023 at 04:45:12PM +0530, shrikanth hegde wrote:
>> >> We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in
>> >> one of our systems. System fails to come up. System was booting well
>> >> with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel.
>> >>
>> >> Panic Log is below.
>> >> [ 333.390539] ------------[ cut here ]------------
>> >> [ 333.390552] WARNING: CPU: 56 PID: 12450 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
>> >
>> > Hmm, ok, so this is the same if (WARN_ON_ONCE(!ip || !ip->i_ino)) line
>> > in xfs_iunlink_lookup that I've been bonking my head on the past
>> > several days. 333 seconds uptime, so I guess this is a pretty recent
>> > mount. You didn't post a full dmesg, so I can only assume there weren't
>> > any *other* obvious complaints from XFS when the fs was mounted...
>> >
>>
>> Darrick, Dave. Thank you for taking a look at this. sorry i didnt paste the full log.
>> Please find the full dmesg below. it was kexec from 5.17-rc2 to 6.2-rc8
>>
>>
>> Starting Reboot via kexec...
>> [ 71.134231] printk: systemd-shutdow: 37 output lines suppressed due to ratelimiting
>> [ 71.158255] systemd-shutdown[1]: Syncing filesystems and block devices.
>> [ 71.160419] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
>> [ 71.214007] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
>> [ 71.233182] systemd-shutdown[1]: Unmounting file systems.
>> [ 71.233845] [2287]: Remounting '/home' read-only in with options 'attr2,inode64,logbufs=8,logbsize=32k,noquota'.
>> [ 71.234873] [2288]: Unmounting '/home'.
>> [ 71.237859] XFS (nvme0n1p1): Unmounting Filesystem
>> [ 71.524111] [2289]: Remounting '/' read-only in with options 'attr2,inode64,logbufs=8,logbsize=32k,noquota'.
>> [ 71.810094] systemd-shutdown[1]: All filesystems unmounted.
>> [ 71.810103] systemd-shutdown[1]: Deactivating swaps.
>> [ 71.810121] systemd-shutdown[1]: All swaps deactivated. pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/li[ 71.810126] systemd-shutdown[1]: Detaching loop devices.'
>> [ 71.810227] systemd-shutdown[1]: All loop devices detached.
>> [ 71.810232] systemd-shutdown[1]: Detaching DM devices.
>> [ 71.932097] printk: shutdown: 8 output lines suppressed due to ratelimiting
>> [ 71.954484] dracut Warning: Killing all remaining processes
>> dracut Warning: Killing all remaining processes
>> [ 72.001360] XFS (dm-0): Unmounting Filesystem
>> [ 72.393816] dracut Warning: Unmounted /oldroot.
>> [ 72.409893] dracut: Disassembling device-mapper devices
>> [ 72.527853] Removing IBM Power 842 compression device
>> [ 78.084038] kexec_core: Starting new kernel
>> [ 78.104094] kexec: waiting for cpu 26 (physical 26) to enter 1 state
>> [ 78.104102] kexec: waiting for cpu 87 (physical 87) to enter 1 state
>> [ 78.104109] kexec: waiting for cpu 1 (physical 1) to enter 2 state
>> [ 78.104248] kexec: waiting for cpu 2 (physical 2) to enter 2 state
>> [ 78.104275] kexec: waiting for cpu 3 (physical 3) to enter 2 state
>> [ 78.104289] kexec: waiting for cpu 4 (physical 4) to enter 2 state
>> [ 78.104303] kexec: waiting for cpu 5 (physical 5) to enter 2 state
>> [ 78.104315] kexec: waiting for cpu 8 (physical 8) to enter 2 state
>> [ 78.104352] kexec: waiting for cpu 48 (physical 48) to enter 2 state
>> [ 78.104357] kexec: waiting for cpu 49 (physical 49) to enter 2 state
>> [ 78.278072] kexec: Starting switchover sequence.
>> I'm in purgatory
>> [ 0.000000] radix-mmu: Page sizes from device-tree:
>> [ 0.000000] radix-mmu: Page size shift = 12 AP=0x0
>> [ 0.000000] radix-mmu: Page size shift = 16 AP=0x5
>> [ 0.000000] radix-mmu: Page size shift = 21 AP=0x1
>> [ 0.000000] radix-mmu: Page size shift = 30 AP=0x2
>> [ 0.000000] Activating Kernel Userspace Access Prevention
>> [ 0.000000] Activating Kernel Userspace Execution Prevention
>> [ 0.000000] radix-mmu: Mapped 0x0000000000000000-0x0000000002600000 with 2.00 MiB pages (exec)
>> [ 0.000000] radix-mmu: Mapped 0x0000000002600000-0x0000004b00000000 with 2.00 MiB pages
>> [ 0.000000] lpar: Using radix MMU under hypervisor
>> [ 0.000000] Linux version 6.2.0-rc8ssh (root@ltcden3-lp1.aus.stglabs.ibm.com) (gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10), GNU ld version 2.30-113.el8) #35 SMP Sat Feb 18 00:41:56 EST 2023
>> [ 0.000000] Found initrd at 0xc0000000061d0000:0xc00000000ac38d3b
>> [ 0.000000] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
>> [ 0.000000] printk: bootconsole [udbg0] enabled
>> [ 0.000000] Partition configured for 96 cpus.
>> [ 0.000000] CPU maps initialized for 8 threads per core
>> [ 0.000000] numa: Partition configured for 32 NUMA nodes.
>> [ 0.000000] -----------------------------------------------------
>> [ 0.000000] phys_mem_size = 0x4b00000000
>> [ 0.000000] dcache_bsize = 0x80
>> [ 0.000000] icache_bsize = 0x80
>> [ 0.000000] cpu_features = 0x000c00eb8f5f9187
>> [ 0.000000] possible = 0x000ffbfbcf5fb187
>> [ 0.000000] always = 0x0000000380008181
>> [ 0.000000] cpu_user_features = 0xdc0065c2 0xaef60000
>> [ 0.000000] mmu_features = 0xbc007641
>> [ 0.000000] firmware_features = 0x000005bfc55bfc57
>> [ 0.000000] vmalloc start = 0xc008000000000000
>> [ 0.000000] IO start = 0xc00a000000000000
>> [ 0.000000] vmemmap start = 0xc00c000000000000
>> [ 0.000000] -----------------------------------------------------
>> [ 0.000000] numa: NODE_DATA [mem 0x4afe663780-0x4afe66aeff]
>> [ 0.000000] rfi-flush: fallback displacement flush available
>> [ 0.000000] count-cache-flush: hardware flush enabled.
>> [ 0.000000] link-stack-flush: software flush enabled.
>> [ 0.000000] stf-barrier: eieio barrier available
>> [ 0.000000] PPC64 nvram contains 15360 bytes
>> [ 0.000000] barrier-nospec: using ORI speculation barrier
>> [ 0.000000] Zone ranges:
>> [ 0.000000] Normal [mem 0x0000000000000000-0x0000004affffffff]
>> [ 0.000000] Device empty
>> [ 0.000000] Movable zone start for each node
>> [ 0.000000] Early memory node ranges
>> [ 0.000000] node 2: [mem 0x0000000000000000-0x0000004affffffff]
>> [ 0.000000] Initializing node 0 as memoryless
>> [ 0.000000] Initmem setup node 0 as memoryless
>> [ 0.000000] Initializing node 1 as memoryless
>> [ 0.000000] Initmem setup node 1 as memoryless
>> [ 0.000000] Initmem setup node 2 [mem 0x0000000000000000-0x0000004affffffff]
>> [ 0.000000] Initializing node 3 as memoryless
>> [ 0.000000] Initmem setup node 3 as memoryless
>> [ 0.000000] Initializing node 4 as memoryless
>> [ 0.000000] Initmem setup node 4 as memoryless
>> [ 0.000000] Initializing node 5 as memoryless
>> [ 0.000000] Initmem setup node 5 as memoryless
>> [ 0.000000] Initializing node 6 as memoryless
>> [ 0.000000] Initmem setup node 6 as memoryless
>> [ 0.000000] Initializing node 7 as memoryless
>> [ 0.000000] Initmem setup node 7 as memoryless
>> [ 0.000000] Initializing node 8 as memoryless
>> [ 0.000000] Initmem setup node 8 as memoryless
>> [ 0.000000] Initializing node 9 as memoryless
>> [ 0.000000] Initmem setup node 9 as memoryless
>> [ 0.000000] Initializing node 10 as memoryless
>> [ 0.000000] Initmem setup node 10 as memoryless
>> [ 0.000000] Initializing node 11 as memoryless
>> [ 0.000000] Initmem setup node 11 as memoryless
>> [ 0.000000] Initializing node 12 as memoryless
>> [ 0.000000] Initmem setup node 12 as memoryless
>> [ 0.000000] Initializing node 13 as memoryless
>> [ 0.000000] Initmem setup node 13 as memoryless
>> [ 0.000000] Initializing node 14 as memoryless
>> [ 0.000000] Initmem setup node 14 as memoryless
>> [ 0.000000] Initializing node 15 as memoryless
>> [ 0.000000] Initmem setup node 15 as memoryless
>> [ 0.000000] Initializing node 16 as memoryless
>> [ 0.000000] Initmem setup node 16 as memoryless
>> [ 0.000000] Initializing node 17 as memoryless
>> [ 0.000000] Initmem setup node 17 as memoryless
>> [ 0.000000] Initializing node 18 as memoryless
>> [ 0.000000] Initmem setup node 18 as memoryless
>> [ 0.000000] Initializing node 19 as memoryless
>> [ 0.000000] Initmem setup node 19 as memoryless
>> [ 0.000000] Initializing node 20 as memoryless
>> [ 0.000000] Initmem setup node 20 as memoryless
>> [ 0.000000] Initializing node 21 as memoryless
>> [ 0.000000] Initmem setup node 21 as memoryless
>> [ 0.000000] Initializing node 22 as memoryless
>> [ 0.000000] Initmem setup node 22 as memoryless
>> [ 0.000000] Initializing node 23 as memoryless
>> [ 0.000000] Initmem setup node 23 as memoryless
>> [ 0.000000] Initializing node 24 as memoryless
>> [ 0.000000] Initmem setup node 24 as memoryless
>> [ 0.000000] Initializing node 25 as memoryless
>> [ 0.000000] Initmem setup node 25 as memoryless
>> [ 0.000000] Initializing node 26 as memoryless
>> [ 0.000000] Initmem setup node 26 as memoryless
>> [ 0.000000] Initializing node 27 as memoryless
>> [ 0.000000] Initmem setup node 27 as memoryless
>> [ 0.000000] Initializing node 28 as memoryless
>> [ 0.000000] Initmem setup node 28 as memoryless
>> [ 0.000000] Initializing node 29 as memoryless
>> [ 0.000000] Initmem setup node 29 as memoryless
>> [ 0.000000] Initializing node 30 as memoryless
>> [ 0.000000] Initmem setup node 30 as memoryless
>> [ 0.000000] Initializing node 31 as memoryless
>> [ 0.000000] Initmem setup node 31 as memoryless
>> [ 0.000000] percpu: Embedded 10 pages/cpu s601512 r0 d53848 u655360
>> [ 0.000000] Fallback order for Node 0: 0 2
>> [ 0.000000] Fallback order for Node 1: 1 2
>> [ 0.000000] Fallback order for Node 2: 2
>> [ 0.000000] Fallback order for Node 3: 3 2
>> [ 0.000000] Fallback order for Node 4: 4 2
>> [ 0.000000] Fallback order for Node 5: 5 2
>> [ 0.000000] Fallback order for Node 6: 6 2
>> [ 0.000000] Fallback order for Node 7: 7 2
>> [ 0.000000] Fallback order for Node 8: 8 2
>> [ 0.000000] Fallback order for Node 9: 9 2
>> [ 0.000000] Fallback order for Node 10: 10 2
>> [ 0.000000] Fallback order for Node 11: 11 2
>> [ 0.000000] Fallback order for Node 12: 12 2
>> [ 0.000000] Fallback order for Node 13: 13 2
>> [ 0.000000] Fallback order for Node 14: 14 2
>> [ 0.000000] Fallback order for Node 15: 15 2
>> [ 0.000000] Fallback order for Node 16: 16 2
>> [ 0.000000] Fallback order for Node 17: 17 2
>> [ 0.000000] Fallback order for Node 18: 18 2
>> [ 0.000000] Fallback order for Node 19: 19 2
>> [ 0.000000] Fallback order for Node 20: 20 2
>> [ 0.000000] Fallback order for Node 21: 21 2
>> [ 0.000000] Fallback order for Node 22: 22 2
>> [ 0.000000] Fallback order for Node 23: 23 2
>> [ 0.000000] Fallback order for Node 24: 24 2
>> [ 0.000000] Fallback order for Node 25: 25 2
>> [ 0.000000] Fallback order for Node 26: 26 2
>> [ 0.000000] Fallback order for Node 27: 27 2
>> [ 0.000000] Fallback order for Node 28: 28 2
>> [ 0.000000] Fallback order for Node 29: 29 2
>> [ 0.000000] Fallback order for Node 30: 30 2
>> [ 0.000000] Fallback order for Node 31: 31 2
>> [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 4910400
>> [ 0.000000] Policy zone: Normal
>> [ 0.000000] Kernel command line: root=/dev/mapper/rhel_ltcden3--lp1-root
>> [ 0.000000] random: crng init done
>> [ 0.000000] Dentry cache hash table entries: 16777216 (order: 11, 134217728 bytes, linear)
>> [ 0.000000] Inode-cache hash table entries: 8388608 (order: 10, 67108864 bytes, linear)
>> [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
>> [ 0.000000] Memory: 313817216K/314572800K available (15168K kernel code, 5632K rwdata, 17600K rodata, 5440K init, 2721K bss, 755584K reserved, 0K cma-reserved)
>> [ 0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=96, Nodes=32
>> [ 0.000000] ftrace: allocating 38156 entries in 14 pages
>> [ 0.000000] ftrace: allocated 14 pages with 3 groups
>> [ 0.000000] trace event string verifier disabled
>> [ 0.000000] rcu: Hierarchical RCU implementation.
>> [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=2048 to nr_cpu_ids=96.
>> [ 0.000000] Rude variant of Tasks RCU enabled.
>> [ 0.000000] Tracing variant of Tasks RCU enabled.
>> [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
>> [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=96
>> [ 0.000000] NR_IRQS: 512, nr_irqs: 512, preallocated irqs: 16
>> [ 0.000000] xive: Using IRQ range [400000-40005f]
>> [ 0.000000] xive: Interrupt handling initialized with spapr backend
>> [ 0.000000] xive: Using priority 7 for all interrupts
>> [ 0.000000] xive: Using 64kB queues
>> [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
>> [ 0.000001] time_init: 56 bit decrementer (max: 7fffffffffffff)
>> [ 0.000021] clocksource: timebase: mask: 0xffffffffffffffff max_cycles: 0x761537d007, max_idle_ns: 440795202126 ns
>> [ 0.000055] clocksource: timebase mult[1f40000] shift[24] registered
>> [ 0.000233] Console: colour dummy device 80x25
>> [ 0.000252] printk: console [hvc0] enabled
>> [ 0.000252] printk: console [hvc0] enabled
>> [ 0.000269] printk: bootconsole [udbg0] disabled
>> [ 0.000269] printk: bootconsole [udbg0] disabled
>> [ 0.000360] pid_max: default: 98304 minimum: 768
>> [ 0.000481] LSM: initializing lsm=capability,yama,integrity,selinux,bpf
>> [ 0.000550] Yama: becoming mindful.
>> [ 0.000565] SELinux: Initializing.
>> [ 0.000568] SELinux: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE is non-zero. This is deprecated and will be rejected in a future kernel release.
>> [ 0.000573] SELinux: https://github.com/SELinuxProject/selinux-kernel/wiki/DEPRECATE-checkreqprot
>> [ 0.000747] LSM support for eBPF active
>> [ 0.000929] Mount-cache hash table entries: 262144 (order: 5, 2097152 bytes, linear)
>> [ 0.001056] Mountpoint-cache hash table entries: 262144 (order: 5, 2097152 bytes, linear)
>> [ 0.003430] cblist_init_generic: Setting adjustable number of callback queues.
>> [ 0.003454] cblist_init_generic: Setting shift to 7 and lim to 1.
>> [ 0.003486] cblist_init_generic: Setting shift to 7 and lim to 1.
>> [ 0.003507] POWER10 performance monitor hardware support registered
>> [ 0.003537] rcu: Hierarchical SRCU implementation.
>> [ 0.003540] rcu: Max phase no-delay instances is 1000.
>> [ 0.004445] smp: Bringing up secondary CPUs ...
>> [ 0.022208] smp: Brought up 1 node, 96 CPUs
>> [ 0.022218] numa: Node 2 CPUs: 0-95
>> [ 0.022222] Big cores detected but using small core scheduling
>> [ 0.033289] devtmpfs: initialized
>> [ 0.042965] PCI host bridge /pci@800000020000019 ranges:
>> [ 0.042984] MEM 0x0000040080000000..0x00000400feffffff -> 0x0000000080000000
>> [ 0.042988] MEM 0x0000044000000000..0x0000047fffffffff -> 0x0006204000000000
>> [ 0.043060] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
>> [ 0.043066] futex hash table entries: 32768 (order: 6, 4194304 bytes, linear)
>> [ 0.043643] NET: Registered PF_NETLINK/PF_ROUTE protocol family
>> [ 0.043801] audit: initializing netlink subsys (disabled)
>> [ 0.043903] audit: type=2000 audit(1676701683.040:1): state=initialized audit_enabled=0 res=1
>> [ 0.043954] thermal_sys: Registered thermal governor 'fair_share'
>> [ 0.043955] thermal_sys: Registered thermal governor 'step_wise'
>> [ 0.044007] cpuidle: using governor menu
>> [ 0.044306] pstore: Registered nvram as persistent store backend
>> [ 0.044682] EEH: pSeries platform initialized
>> [ 0.055324] PCI: Probing PCI hardware
>> [ 0.055372] PCI host bridge to bus 0019:01
>> [ 0.055376] pci_bus 0019:01: root bus resource [mem 0x40080000000-0x400feffffff] (bus address [0x80000000-0xfeffffff])
>> [ 0.055381] pci_bus 0019:01: root bus resource [mem 0x44000000000-0x47fffffffff 64bit] (bus address [0x6204000000000-0x6207fffffffff])
>> [ 0.055386] pci_bus 0019:01: root bus resource [bus 01-ff]
>> [ 0.056001] pci 0019:01:00.0: No hypervisor support for SR-IOV on this device, IOV BARs disabled.
>> [ 0.064978] IOMMU table initialized, virtual merging enabled
>> [ 0.065086] pci 0019:01:00.0: Adding to iommu group 0
>> [ 0.066308] EEH: Capable adapter found: recovery enabled.
>> [ 0.066550] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
>> [ 0.066812] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
>> [ 0.066817] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
>> [ 0.066821] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
>> [ 0.066824] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
>> [ 0.085068] cryptd: max_cpu_qlen set to 1000
>> [ 0.085368] iommu: Default domain type: Translated
>> [ 0.085371] iommu: DMA domain TLB invalidation policy: strict mode
>> [ 0.085491] SCSI subsystem initialized
>> [ 0.085517] usbcore: registered new interface driver usbfs
>> [ 0.085523] usbcore: registered new interface driver hub
>> [ 0.085542] usbcore: registered new device driver usb
>> [ 0.085563] pps_core: LinuxPPS API ver. 1 registered
>> [ 0.085565] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
>> [ 0.085569] PTP clock support registered
>> [ 0.085628] EDAC MC: Ver: 3.0.0
>> [ 0.085885] NetLabel: Initializing
>> [ 0.085887] NetLabel: domain hash size = 128
>> [ 0.085889] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
>> [ 0.085903] NetLabel: unlabeled traffic allowed by default
>> [ 0.085956] vgaarb: loaded
>> [ 0.086157] clocksource: Switched to clocksource timebase
>> [ 0.086451] VFS: Disk quotas dquot_6.6.0
>> [ 0.086480] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)
>> [ 0.088080] NET: Registered PF_INET protocol family
>> [ 0.088237] IP idents hash table entries: 262144 (order: 5, 2097152 bytes, linear)
>> [ 0.091345] tcp_listen_portaddr_hash hash table entries: 65536 (order: 4, 1048576 bytes, linear)
>> [ 0.091454] Table-perturb hash table entries: 65536 (order: 2, 262144 bytes, linear)
>> [ 0.091480] TCP established hash table entries: 524288 (order: 6, 4194304 bytes, linear)
>> [ 0.092201] TCP bind hash table entries: 65536 (order: 5, 2097152 bytes, linear)
>> [ 0.092386] TCP: Hash tables configured (established 524288 bind 65536)
>> [ 0.092708] MPTCP token hash table entries: 65536 (order: 4, 1572864 bytes, linear)
>> [ 0.092826] UDP hash table entries: 65536 (order: 5, 2097152 bytes, linear)
>> [ 0.093046] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes, linear)
>> [ 0.093402] NET: Registered PF_UNIX/PF_LOCAL protocol family
>> [ 0.093413] NET: Registered PF_XDP protocol family
>> [ 0.093509] PCI: CLS 128 bytes, default 128
>> [ 0.093638] Unpacking initramfs...
>> [ 0.094862] vio_register_device_node: node lid missing 'reg'
>> [ 0.103665] vas: GZIP feature is available
>> [ 0.104512] hv-24x7: read 548 catalog entries, created 387 event attrs (0 failures), 387 descs
>> [ 0.108478] Initialise system trusted keyrings
>> [ 0.108493] Key type blacklist registered
>> [ 0.108560] workingset: timestamp_bits=38 max_order=23 bucket_order=0
>> [ 0.108587] zbud: loaded
>> [ 0.108988] integrity: Platform Keyring initialized
>> [ 0.119068] NET: Registered PF_ALG protocol family
>> [ 0.119083] Key type asymmetric registered
>> [ 0.119086] Asymmetric key parser 'x509' registered
>> [ 0.119120] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
>> [ 0.119182] io scheduler mq-deadline registered
>> [ 0.119185] io scheduler kyber registered
>> [ 0.119198] io scheduler bfq registered
>> [ 0.120970] atomic64_test: passed
>> [ 0.121210] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
>> [ 0.121214] PowerPC PowerNV PCI Hotplug Driver version: 0.1
>> [ 0.121532] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> [ 0.121728] Non-volatile memory driver v1.3
>> [ 0.122174] rdac: device handler registered
>> [ 0.122215] hp_sw: device handler registered
>> [ 0.122218] emc: device handler registered
>> [ 0.122260] alua: device handler registered
>> [ 0.122450] usbcore: registered new interface driver usbserial_generic
>> [ 0.122457] usbserial: USB Serial support registered for generic
>> [ 0.122529] mousedev: PS/2 mouse device common for all mice
>> [ 0.122644] rtc-generic rtc-generic: registered as rtc0
>> [ 0.122676] rtc-generic rtc-generic: setting system clock to 2023-02-18T06:28:03 UTC (1676701683)
>> [ 0.122755] xcede: xcede_record_size = 10
>> [ 0.122758] xcede: Record 0 : hint = 1, latency = 0x1800 tb ticks, Wake-on-irq = 1
>> [ 0.122765] xcede: Record 1 : hint = 2, latency = 0x3c00 tb ticks, Wake-on-irq = 0
>> [ 0.122769] cpuidle: Skipping the 2 Extended CEDE idle states
>> [ 0.122771] cpuidle: Fixed up CEDE exit latency to 12 us
>> [ 0.123865] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sync_size new:65536 old:0
>> [ 0.123871] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sync_sg new:510 old:0
>> [ 0.123875] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sg_len new:4080 old:0
>> [ 0.124018] hid: raw HID events driver (C) Jiri Kosina
>> [ 0.124042] usbcore: registered new interface driver usbhid
>> [ 0.124048] usbhid: USB HID core driver
>> [ 0.124069] drop_monitor: Initializing network drop monitor service
>> [ 0.134168] Initializing XFRM netlink socket
>> [ 0.134234] NET: Registered PF_INET6 protocol family
>> [ 0.134747] Segment Routing with IPv6
>> [ 0.134756] In-situ OAM (IOAM) with IPv6
>> [ 0.134776] NET: Registered PF_PACKET protocol family
>> [ 0.134817] mpls_gso: MPLS GSO support
>> [ 0.134836] secvar-sysfs: secvar: failed to retrieve secvar operations.
>> [ 0.139134] registered taskstats version 1
>> [ 0.140964] Loading compiled-in X.509 certificates
>> [ 0.156881] Loaded X.509 cert 'Build time autogenerated kernel key: 7b04a1cdeda81c05f7a701657946db5548da6201'
>> [ 0.157494] zswap: loaded using pool lzo/zbud
>> [ 0.160050] page_owner is disabled
>> [ 0.160226] pstore: Using crash dump compression: deflate
>> [ 0.972073] Freeing initrd memory: 76160K
>> [ 0.974020] Key type encrypted registered
>> [ 0.974056] Secure boot mode disabled
>> [ 0.974060] ima: No TPM chip found, activating TPM-bypass!
>> [ 0.974067] Loading compiled-in module X.509 certificates
>> [ 0.974567] Loaded X.509 cert 'Build time autogenerated kernel key: 7b04a1cdeda81c05f7a701657946db5548da6201'
>> [ 0.974571] ima: Allocated hash algorithm: sha256
>> [ 0.974598] Secure boot mode disabled
>> [ 0.974615] Trusted boot mode disabled
>> [ 0.974617] ima: No architecture policies found
>> [ 0.974629] evm: Initialising EVM extended attributes:
>> [ 0.974631] evm: security.selinux
>> [ 0.974633] evm: security.SMACK64 (disabled)
>> [ 0.974635] evm: security.SMACK64EXEC (disabled)
>> [ 0.974637] evm: security.SMACK64TRANSMUTE (disabled)
>> [ 0.974639] evm: security.SMACK64MMAP (disabled)
>> [ 0.974641] evm: security.apparmor (disabled)
>> [ 0.974642] evm: security.ima
>> [ 0.974644] evm: security.capability
>> [ 0.974646] evm: HMAC attrs: 0x1
>> [ 0.974676] alg: No test for 842 (842-nx)
>> [ 0.982519] Freeing unused kernel image (initmem) memory: 5440K
>> [ 1.086157] Run /init as init process
>> [ 1.092664] systemd[1]: systemd 239 (239-58.el8) running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy)
>> [ 1.092708] systemd[1]: Detected virtualization powervm.
>> [ 1.092714] systemd[1]: Detected architecture ppc64-le.
>> [ 1.092718] systemd[1]: Running in initial RAM disk.
>>
>> Welcome to Red Hat Enterprise Linux 8.6 (Ootpa) dracut-049-201.git20220131.el8 (Initramfs)!
>>
>> [ 1.246394] systemd[1]: Set hostname to <ltcden3-lp1.aus.stglabs.ibm.com>.
>> [ 1.321102] systemd[1]: Listening on Journal Socket.
>> [ OK ] Listening on Journal Socket.
>> [ 1.322421] systemd[1]: Started Hardware RNG Entropy Gatherer Daemon.
>> [ OK ] Started Hardware RNG Entropy Gatherer Daemon.
>> [ 1.323252] systemd[1]: Starting Create list of required static device nodes for the current kernel...
>> Starting Create list of required st…ce nodes for the current kernel...
>> [ 1.323333] systemd[1]: Reached target Local File Systems.
>> [ OK ] Reached target Local File Systems.
>> [ 1.324085] systemd[1]: Started Memstrack Anylazing Service.
>> [ OK ] Started Memstrack Anylazing Service.
>> [ OK ] Reached target Slices.
>> [ OK ] Listening on udev Kernel Socket.
>> [ OK ] Listening on Journal Socket (/dev/log).
>> Starting Journal Service...
>> Starting Create Volatile Files and Directories...
>> [ OK ] Reached target Swap.
>> [ OK ] Reached target Timers.
>> Starting Setup Virtual Console...
>> Starting Load Kernel Modules...
>> [ OK ] Listening on udev Control Socket.
>> [ OK ] Reached target Sockets.
>> [ OK ] Started Create list of required sta…vice nodes for the current kernel.
>> [ OK ] Started Create Volatile Files and Directories.
>> Starting Create Static Device Nodes in /dev...
>> [FAILED] Failed to start Load Kernel Modules.
>> See 'systemctl status systemd-modules-load.service' for details.
>> Starting Apply Kernel Variables...
>> [ OK ] Started Create Static Device Nodes in /dev.
>> [ OK ] Started Apply Kernel Variables.
>> [ OK ] Started Journal Service.
>> [ OK ] Started Setup Virtual Console.
>> Starting dracut cmdline hook...
>> [ OK ] Started dracut cmdline hook.
>> Starting dracut pre-udev hook...
>> [ 1.477216] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
>> [ 1.477252] device-mapper: uevent: version 1.0.3
>> [ 1.477339] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
>> [ OK ] Started dracut pre-udev hook.
>> Starting udev Kernel Device Manager...
>> [ OK ] Started udev Kernel Device Manager.
>> Starting udev Coldplug all Devices...
>> Mounting Kernel Configuration File System...
>> [ OK ] Mounted Kernel Configuration File System.
>> [ 1.651355] synth uevent: /devices/vio: failed to send uevent
>> [ 1.651365] vio vio: uevent: failed to send synthetic uevent: -19
>> [ 1.651402] synth uevent: /devices/vio/4000: failed to send uevent
>> [ 1.651406] vio 4000: uevent: failed to send synthetic uevent: -19
>> [ 1.651415] synth uevent: /devices/vio/4001: failed to send uevent
>> [ 1.651418] vio 4001: uevent: failed to send synthetic uevent: -19
>> [ 1.651428] synth uevent: /devices/vio/4002: failed to send uevent
>> [ 1.651431] vio 4002: uevent: failed to send synthetic uevent: -19
>> [ 1.651441] synth uevent: /devices/vio/4004: failed to send uevent
>> [ 1.651444] vio 4004: uevent: failed to send synthetic uevent: -19
>> [ OK ] Started udev Coldplug all Devices.
>> [ OK ] Reached target System Initialization.
>> Starting Show Plymouth Boot Screen...
>> Starting dracut initqueue hook...
>> [ OK ] Started Show Plymouth Boot Screen.
>> [ OK ] Started Forward Password Requests to Plymouth Directory Watch.
>> [ OK ] Reached target Paths.
>> [ OK ] Reached target Basic System.
>> [ 1.709851] ibmveth 30000002 net0: renamed from eth0
>> [ 1.712196] nvme nvme0: pci function 0019:01:00.0
>> [ 1.714161] ibmvscsi 30000065: SRP_VERSION: 16.a
>> [ 1.714223] ibmvscsi 30000065: Maximum ID: 64 Maximum LUN: 32 Maximum Channel: 3
>> [ 1.714227] scsi host0: IBM POWER Virtual SCSI Adapter 1.5.9
>> [ 1.714365] ibmvscsi 30000065: partner initialization complete
>> [ 1.714391] ibmvscsi 30000065: host srp version: 16.a, host partition ltcden3-vios1 (100), OS 3, max io 524288
>> [ 1.714421] ibmvscsi 30000065: Client reserve enabled
>> [ 1.714426] ibmvscsi 30000065: sent SRP login
>> [ 1.714448] ibmvscsi 30000065: SRP_LOGIN succeeded
>> [ 1.721611] nvme nvme0: Shutdown timeout set to 8 seconds
>> [ 1.737117] scsi 0:0:1:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
>> [ 1.738038] scsi 0:0:2:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
>> [ 1.738364] scsi 0:0:3:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
>> [ 1.750754] nvme nvme0: 32/0/0 default/read/poll queues
>> [ 1.754482] nvme0n1: p1 p2 p3
>> [ 1.772868] scsi 0:0:1:0: Attached scsi generic sg0 type 0
>> [ 1.772898] scsi 0:0:2:0: Attached scsi generic sg1 type 0
>> [ 1.772920] scsi 0:0:3:0: Attached scsi generic sg2 type 0
>> [ 1.794722] sd 0:0:2:0: [sda] 629145600 512-byte logical blocks: (322 GB/300 GiB)
>> [ 1.794757] sd 0:0:2:0: [sda] Write Protect is off
>> [ 1.794758] sd 0:0:1:0: [sdb] 209715200 512-byte logical blocks: (107 GB/100 GiB)
>> [ 1.794790] sd 0:0:2:0: [sda] Cache data unavailable
>> [ 1.794792] sd 0:0:1:0: [sdb] Write Protect is off
>> [ 1.794796] sd 0:0:2:0: [sda] Assuming drive cache: write through
>> [ 1.794826] sd 0:0:1:0: [sdb] Cache data unavailable
>> [ 1.794829] sd 0:0:1:0: [sdb] Assuming drive cache: write through
>> [ 1.794943] sd 0:0:3:0: [sdc] 91750400 4096-byte logical blocks: (376 GB/350 GiB)
>> [ 1.794979] sd 0:0:3:0: [sdc] Write Protect is off
>> [ 1.795008] sd 0:0:3:0: [sdc] Cache data unavailable
>> [ 1.795011] sd 0:0:3:0: [sdc] Assuming drive cache: write through
>> [ 1.796625] sdb: sdb1 sdb2 sdb3
>> [ 1.796717] sdc: sdc1
>> [ 1.796720] sda: sda1 sda2
>> [ 1.796752] sd 0:0:1:0: [sdb] Attached SCSI disk
>> [ 1.796820] sd 0:0:3:0: [sdc] Attached SCSI disk
>> [ 1.796841] sd 0:0:2:0: [sda] Attached SCSI disk
>> [ OK ] Found device /dev/mapper/rhel_ltcden3--lp1-root.
>> [ OK ] Reached target Initrd Root Device.
>> [ OK ] Started dracut initqueue hook.
>> Starting File System Check on /dev/mapper/rhel_ltcden3--lp1-root...
>> [ OK ] Reached target Remote File Systems (Pre).
>> [ OK ] Reached target Remote File Systems.
>> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
>> Mounting /sysroot...
>> [ 3.060638] SGI XFS with ACLs, security attributes, quota, no debug enabled
>> [ 3.062369] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
>> [ 3.109076] XFS (dm-0): Ending clean mount
>> [ OK ] Mounted /sysroot.
>> [ OK ] Reached target Initrd Root File System.
>> Starting Reload Configuration from the Real Root...
>> [ OK ] Started Reload Configuration from the Real Root.
>> [ OK ] Reached target Initrd File Systems.
>> [ OK ] Reached target Initrd Default Target.
>> Starting dracut pre-pivot and cleanup hook...
>> [ OK ] Started dracut pre-pivot and cleanup hook.
>> Starting Cleaning Up and Shutting Down Daemons...
>> [ OK ] Stopped dracut pre-pivot and cleanup hook.
>> [ OK ] Stopped target Remote File Systems.
>> [ OK ] Stopped target Initrd Default Target.
>> [ OK ] Stopped target Timers.
>> [ OK ] Stopped target Initrd Root Device.
>> [ OK ] Stopped target Remote File Systems (Pre).
>> [ OK ] Stopped dracut initqueue hook.
>> Starting Setup Virtual Console...
>> [ OK ] Stopped target Basic System.
>> [ OK ] Stopped target System Initialization.
>> [ OK ] Stopped Create Volatile Files and Directories.
>> [ OK ] Stopped Apply Kernel Variables.
>> [ OK ] Stopped udev Coldplug all Devices.
>> Stopping udev Kernel Device Manager...
>> [ OK ] Stopped target Swap.
>> [ OK ] Stopped target Paths.
>> [ OK ] Stopped target Sockets.
>> [ OK ] Stopped target Slices.
>> Starting Plymouth switch root service...
>> [ OK ] Stopped target Local File Systems.
>> [ OK ] Started Cleaning Up and Shutting Down Daemons.
>> [ OK ] Started Plymouth switch root service.
>> [ OK ] Started Setup Virtual Console.
>> [ OK ] Stopped udev Kernel Device Manager.
>> [ OK ] Stopped Create Static Device Nodes in /dev.
>> [ OK ] Stopped Create list of required sta…vice nodes for the current kernel.
>> Stopping Hardware RNG Entropy Gatherer Daemon...
>> [ OK ] Stopped dracut pre-udev hook.
>> [ OK ] Stopped dracut cmdline hook.
>> [ OK ] Closed udev Control Socket.
>> [ OK ] Closed udev Kernel Socket.
>> Starting Cleanup udevd DB...
>> [ OK ] Stopped Hardware RNG Entropy Gatherer Daemon.
>> [ OK ] Started Cleanup udevd DB.
>> [ OK ] Reached target Switch Root.
>> Starting Switch Root...
>> [ 3.449370] printk: systemd: 22 output lines suppressed due to ratelimiting
>> [ 3.593463] SELinux: Runtime disable is deprecated, use selinux=0 on the kernel cmdline.
>> [ 3.593471] SELinux: https://github.com/SELinuxProject/selinux-kernel/wiki/DEPRECATE-runtime-disable
>> [ 19.036134] SELinux: Disabled at runtime.
>> [ 19.196154] audit: type=1404 audit(1676701702.570:2): enforcing=0 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=0 old-enabled=1 lsm=selinux res=1
>> [ 19.201608] systemd[1]: systemd 239 (239-58.el8) running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy)
>> [ 19.201637] systemd[1]: Detected virtualization powervm.
>> [ 19.201642] systemd[1]: Detected architecture ppc64-le.
>>
>> Welcome to Red Hat Enterprise Linux 8.6 (Ootpa)!
>>
>> [ 19.202637] systemd[1]: Set hostname to <ltcden3-lp1.aus.stglabs.ibm.com>.
>> [ 21.777702] systemd[1]: systemd-journald.service: Succeeded.
>> [ 21.778191] systemd[1]: initrd-switch-root.service: Succeeded.
>> [ 21.778387] systemd[1]: Stopped Switch Root.
>> [ OK ] Stopped Switch Root.
>> [ 21.778748] systemd[1]: systemd-journald.service: Service has no hold-off time (RestartSec=0), scheduling restart.
>> [ 21.778795] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
>> [ 21.778847] systemd[1]: Stopped Journal Service.
>> [ OK ] Stopped Journal Service.
>> Starting Journal Service...
>> [ OK ] Stopped Plymouth switch root service.
>> [ OK ] Stopped target Switch Root.
>> [ OK ] Listening on udev Kernel Socket.
>> [ OK ] Listening on initctl Compatibility Named Pipe.
>> [ OK ] Listening on Process Core Dump Socket.
>> Mounting Huge Pages File System...
>> Starting Load Kernel Modules...
>> Starting Read and set NIS domainname from /etc/sysconfig/network...
>> Activating swap /dev/mapper/rhel_ltcden3--lp1-swap...
>> [ OK ] Created slice system-serial\x2dgetty.slice.
>> [ OK ] Created slice system-getty.slice.
>> Starting Create list of required st…ce nodes for the current kernel...
>> [ OK ] Created slice User and Session Slice.
>> [ OK ] Reached target Slices.
>> [ OK ] Listening on RPCbind Server Activation Socket.
>> [ OK ] Reached target RPC Port Mapper.
>> Mounting POSIX Message Queue File System...
>> [ OK ] Stopped File System Check on Root Device.
>> Starting Remount Root and Kernel File Systems...
>> [ OK ] Started Forward Password Requests to Wall Directory Watch.
>> [ OK ] Reached target Local Encrypted Volumes.
>> [ 21.912238] Adding 4194240k swap on /dev/mapper/rhel_ltcden3--lp1-swap. Priority:-2 extents:1 across:4194240k FS
>> [ OK ] Listening on Device-mapper event daemon FIFOs.
>> Starting Monitoring of LVM2 mirrors…ng dmeventd or progress polling...
>> Starting Setup Virtual Console...
>> [ OK ] Stopped target Initrd Root File System.
>> Mounting Kernel Debug File System...
>> [ OK ] Listening on udev Control Socket.
>> Starting udev Coldplug all Devices...
>> [ OK ] Created slice system-sshd\x2dkeygen.slice.
>> [ OK ] Stopped target Initrd File Systems.
>> [ OK ] Listening on LVM2 poll daemon socket.
>> [ OK ] Activated swap /dev/mapper/rhel_ltcden3--lp1-swap.
>> [ OK ] Mounted Huge Pages File System.
>> [ OK ] Started Read and set NIS domainname from /etc/sysconfig/network.
>> [ OK ] Started Create list of required sta…vice nodes for the current kernel.
>> [ OK ] Started Journal Service.
>> [ OK ] Mounted POSIX Message Queue File System.
>> [ OK ] Mounted Kernel Debug File System.
>> [ OK ] Reached target Swap.
>> [ 22.217261] xfs filesystem being remounted at / supports timestamps until 2038 (0x7fffffff)
>> [ OK ] Started Remount Root and Kernel File Systems.
>> [ OK ] Started Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
>> Starting Create Static Device Nodes in /dev...
>> Starting Load/Save Random Seed...
>> Starting Flush Journal to Persistent Storage...
>> [FAILED] Failed to start Load Kernel Modules.
>> See 'systemctl status systemd-modules-load.service' for details.
>> Starting Apply Kernel Variables...
>> [ 22.341308] synth uevent: /devices/vio: failed to send uevent
>> [ 22.341317] vio vio: uevent: failed to send synthetic uevent: -19
>> [ 22.341597] synth uevent: /devices/vio/4000: failed to send uevent
>> [ 22.341600] vio 4000: uevent: failed to send synthetic uevent: -19
>> [ 22.341610] synth uevent: /devices/vio/4001: failed to send uevent
>> [ 22.341613] vio 4001: uevent: failed to send synthetic uevent: -19
>> [ 22.341622] synth uevent: /devices/vio/4002: failed to send uevent
>> [ 22.341625] vio 4002: uevent: failed to send synthetic uevent: -19
>> [ 22.341633] synth uevent: /devices/vio/4004: failed to send uevent
>> [ 22.341636] vio 4004: uevent: failed to send synthetic uevent: -19
>> [ OK ] Started udev Coldplug all Devices.
>> Starting udev Wait for Complete Device Initialization...
>> [ OK ] Started Load/Save Random Seed.
>> [ OK ] Started Flush Journal to Persistent Storage.
>> [ OK ] Started Setup Virtual Console.
>> [ OK ] Started Apply Kernel Variables.
>> [ OK ] Started Create Static Device Nodes in /dev.
>> Starting udev Kernel Device Manager...
>> [ OK ] Started udev Kernel Device Manager.
>> [ 24.100485] pseries_rng: Registering IBM pSeries RNG driver
>> [ OK ] Created slice system-lvm2\x2dpvscan.slice.
>> Starting LVM event activation on device 8:19...
>> [ OK ] Started LVM event activation on device 8:19.
>> [ OK ] Started udev Wait for Complete Device Initialization.
>> [ OK ] Reached target Local File Systems (Pre).
>> Mounting /home...
>> Mounting /home2...
>> Mounting /boot...
>> [ 25.049055] XFS (nvme0n1p1): Mounting V5 Filesystem 31458cd5-8eb4-48b4-8f5a-112217ef59df
>> [ 25.049822] XFS (dm-1): Mounting V5 Filesystem 0ac3d742-375d-4cd7-bdd2-72b0559b1957
>> [ 25.050953] XFS (sdb2): Mounting V5 Filesystem c72725b8-35e3-42b4-b5cb-f8435cada964
>> [ 25.055813] XFS (nvme0n1p1): Ending clean mount
>> [ 25.056844] xfs filesystem being mounted at /home supports timestamps until 2038 (0x7fffffff)
>> [ OK ] Mounted /home.
>> [ 25.389921] XFS (dm-1): Ending clean mount
>> [ 25.513566] xfs filesystem being mounted at /home2 supports timestamps until 2038 (0x7fffffff)
>> [ OK ] Mounted /home2.
>> [ 26.797307] XFS (sdb2): Ending clean mount
>> [ 26.857340] xfs filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
>> [ OK ] Mounted /boot.
>> [ OK ] Reached target Local File Systems.
>> Starting Tell Plymouth To Write Out Runtime Data...
>> Starting Restore /run/initramfs on shutdown...
>> Starting Import network configuration from initramfs...
>> [ OK ] Started Restore /run/initramfs on shutdown.
>> [ OK ] Started Import network configuration from initramfs.
>> Starting Create Volatile Files and Directories...
>> [ OK ] Started Tell Plymouth To Write Out Runtime Data.
>> [ OK ] Started Create Volatile Files and Directories.
>> Mounting RPC Pipe File System...
>> Starting Security Auditing Service...
>> Starting RPC Bind...
>> [ OK ] Started RPC Bind.
>> [ 27.888702] RPC: Registered named UNIX socket transport module.
>> [ 27.888714] RPC: Registered udp transport module.
>> [ 27.888717] RPC: Registered tcp transport module.
>> [ 27.888719] RPC: Registered tcp NFSv4.1 backchannel transport module.
>> [ OK ] Mounted RPC Pipe File System.
>> [ OK ] Reached target rpc_pipefs.target.
>> [ OK ] Started Security Auditing Service.
>> Starting Update UTMP about System Boot/Shutdown...
>> [ OK ] Started Update UTMP about System Boot/Shutdown.
>> [ OK ] Reached target System Initialization.
>> [ OK ] Listening on Open-iSCSI iscsid Socket.
>> [ OK ] Listening on CUPS Scheduler.
>> [ OK ] Started Run system activity accounting tool every 10 minutes.
>> [ OK ] Started CUPS Scheduler.
>> [ OK ] Reached target Paths.
>> [ OK ] Listening on SSSD Kerberos Cache Manager responder socket.
>> [ OK ] Listening on D-Bus System Message Bus Socket.
>> [ OK ] Started Generate summary of yesterday's process accounting.
>> [ OK ] Started daily update of the root trust anchor for DNSSEC.
>> [ OK ] Started Daily Cleanup of Temporary Directories.
>> [ OK ] Started dnf makecache --timer.
>> [ OK ] Reached target Timers.
>> [ OK ] Listening on Open-iSCSI iscsiuio Socket.
>> [ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
>> [ OK ] Reached target Sockets.
>> [ OK ] Reached target Basic System.
>> Starting NTP client/server...
>> Starting Hardware RNG Entropy Gatherer Wake threshold service...
>> [ OK ] Started libstoragemgmt plug-in server daemon.
>> [ OK ] Started irqbalance daemon.
>> Starting Resets System Activity Logs...
>> Starting ppc64-diag rtas_errd (platform error handling) Service...
>> Starting Self Monitoring and Reporting Technology (SMART) Daemon...
>> [ OK ] Reached target sshd-keygen.target.
>> Starting ABRT Automated Bug Reporting Tool...
>> Starting System Security Services Daemon...
>> Starting Authorization Manager...
>> [ OK ] Started D-Bus System Message Bus.
>> Starting Avahi mDNS/DNS-SD Stack...
>> [ OK ] Started Hardware RNG Entropy Gatherer Wake threshold service.
>> [ OK ] Started Hardware RNG Entropy Gatherer Daemon.
>> [ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
>> [ OK ] Started Resets System Activity Logs.
>> [ OK ] Started ppc64-diag rtas_errd (platform error handling) Service.
>> [ OK ] Started Avahi mDNS/DNS-SD Stack.
>> [ OK ] Started NTP client/server.
>> [ OK ] Started System Security Services Daemon.
>> [ OK ] Reached target User and Group Name Lookups.
>> Starting Login Service...
>> [ OK ] Started Login Service.
>> [ OK ] Started Authorization Manager.
>> Starting firewalld - dynamic firewall daemon...
>> Starting Modem Manager...
>> [ OK ] Started Modem Manager.
>> [ OK ] Started firewalld - dynamic firewall daemon.
>> [ OK ] Reached target Network (Pre).
>> Starting Network Manager...
>> [ OK ] Started Network Manager.
>> Starting hybrid virtual network scan and config...
>> Starting Network Manager Wait Online...
>> [ OK ] Reached target Network.
>> Starting Enable periodic update of entitlement certificates....
>> Starting CUPS Scheduler...
>> Starting GSSAPI Proxy Daemon...
>> Starting OpenSSH server daemon...
>> Starting Logout off all iSCSI sessions on shutdown...
>> [ OK ] Started Logout off all iSCSI sessions on shutdown.
>> [ OK ] Started Enable periodic update of entitlement certificates..
>> Starting Hostname Service...
>> [ OK ] Started ABRT Automated Bug Reporting Tool.
>> [ OK ] Started ABRT kernel log watcher.
>> [ OK ] Started ABRT Xorg log watcher.
>> [ OK ] Started Creates ABRT problems from coredumpctl messages.
>> [ OK ] Started Hostname Service.
>> [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
>> [FAILED] Failed to start hybrid virtual network scan and config.
>> See 'systemctl status hcn-init.service' for details.
>> [ OK ] Started OpenSSH server daemon.
>> [ OK ] Started GSSAPI Proxy Daemon.
>> [ OK ] Reached target NFS client services.
>> Starting Network Manager Script Dispatcher Service...
>> [ OK ] Started CUPS Scheduler.
>> [ OK ] Started Network Manager Script Dispatcher Service.
>> [ OK ] Started Network Manager Wait Online.
>> [ OK ] Reached target Network is Online.
>> Starting Notify NFS peers of a restart...
>> [ OK ] Reached target Remote File Systems (Pre).
>> [ OK ] Reached target Remote File Systems.
>> Starting Harvest vmcores for ABRT...
>> Starting Permit User Sessions...
>> Starting System Logging Service...
>> [ OK ] Started Notify NFS peers of a restart.
>> [ OK ] Started Permit User Sessions.
>> [ OK ] Started Job spooling tools.
>> Starting Terminate Plymouth Boot Screen...
>> [ OK ] Started Command Scheduler.
>> Starting Hold until boot process finishes up...
>> [ OK ] Started System Logging Service.
>> [ 44.801795] ------------[ cut here ]------------
>> [ 44.801810] WARNING: CPU: 24 PID: 1906 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
>> [ 44.801895] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set rfkill nf_tables nfnetlink sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi nvme ibmveth scsi_transport_srp nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
>> [ 44.801926] CPU: 24 PID: 1906 Comm: in:imjournal Not tainted 6.2.0-rc8ssh #35
>> [ 44.801930] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
>> [ 44.801933] NIP: c00800000062fa80 LR: c00800000062fa4c CTR: c000000000ea4d40
>> [ 44.801936] REGS: c00000001984b690 TRAP: 0700 Not tainted (6.2.0-rc8ssh)
>> [ 44.801939] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24224842 XER: 00000000
>> [ 44.801947] CFAR: c00800000062fa54 IRQMASK: 0
>> [ 44.801947] GPR00: c0000000091cbec8 c00000001984b930 c0080000006d8300 0000000000000000
>> [ 44.801947] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000051aa4d90
>> [ 44.801947] GPR08: 0000000000000000 c000000051aa4e40 0000000000000000 fffffffffffffffd
>> [ 44.801947] GPR12: 0000000000000040 c000004afece5880 0000000000000000 0000000004000000
>> [ 44.801947] GPR16: c00000001984bb38 c00000001984ba38 c00000001984ba68 c00000002c323c00
>> [ 44.801947] GPR20: c0000000091cbe00 0000000000008000 c0000000516e5800 00000000002ec44d
>> [ 44.801947] GPR24: 000000000030af4d 000000000000000d c000000008d71680 00000000002ec44d
>> [ 44.801947] GPR28: c00000002c322400 c0000000091cbe00 c000000054c05618 000000000030af4d
>> [ 44.801983] NIP [c00800000062fa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
>> [ 44.802037] LR [c00800000062fa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
>> [ 44.802090] Call Trace:
>> [ 44.802091] [c00000001984b930] [c000000054c05618] 0xc000000054c05618 (unreliable)
>> [ 44.802096] [c00000001984b950] [c008000000630094] xfs_iunlink+0x1bc/0x280 [xfs]
>> [ 44.802149] [c00000001984b9d0] [c008000000634754] xfs_rename+0x69c/0xd10 [xfs]
>> [ 44.802202] [c00000001984bb10] [c00800000062e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
>> [ 44.802255] [c00000001984bba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
>> [ 44.802261] [c00000001984bc90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
>> [ 44.802265] [c00000001984bde0] [c000000000580520] sys_rename+0x60/0x80
>> [ 44.802269] [c00000001984be10] [c000000000033630] system_call_exception+0x150/0x3b0
>> [ 44.802274] [c00000001984be50] [c00000000000c554] system_call_common+0xf4/0x258
>> [ 44.802280] --- interrupt: c00 at 0x7fffa6482e20
>> [ 44.802282] NIP: 00007fffa6482e20 LR: 00007fffa6055e24 CTR: 0000000000000000
>> [ 44.802285] REGS: c00000001984be80 TRAP: 0c00 Not tainted (6.2.0-rc8ssh)
>> [ 44.802288] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
>> [ 44.802297] IRQMASK: 0
>> [ 44.802297] GPR00: 0000000000000026 00007fffa536d220 00007fffa6607300 00007fffa536d288
>> [ 44.802297] GPR04: 000000014f7a6b70 0000000000000000 0700000000000000 0000000000000002
>> [ 44.802297] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> [ 44.802297] GPR12: 0000000000000000 00007fffa53766e0 000000014f795930 0000000000000000
>> [ 44.802297] GPR16: 0000000126b67648 00007fffa6057ce0 0000000000000003 000000000000002b
>> [ 44.802297] GPR20: 0000000000000212 00007fffa536e3a0 00007fffa536e398 00007fff98008690
>> [ 44.802297] GPR24: 0000000000000000 00007fffa536e388 00007fffa536e378 00007fffa536e3b0
>> [ 44.802297] GPR28: 00007fffa6070000 00007fffa60705e0 00007fff98000c10 00007fffa536d288
>> [ 44.802331] NIP [00007fffa6482e20] 0x7fffa6482e20
>> [ 44.802334] LR [00007fffa6055e24] 0x7fffa6055e24
>> [ 44.802336] --- interrupt: c00
>> [ 44.802338] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
>> [ 44.802352] ---[ end trace 0000000000000000 ]---
>> [ 44.802356] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x9cc/0xd10 [xfs]
>> [ 44.802412] CPU: 24 PID: 1906 Comm: in:imjournal Tainted: G W 6.2.0-rc8ssh #35
>> [ 44.802415] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
>> [ 44.802418] Call Trace:
>> [ 44.802420] [c00000001984b8f0] [c000000000e87328] dump_stack_lvl+0x6c/0x9c (unreliable)
>> [ 44.802425] [c00000001984b920] [c008000000616a84] xfs_error_report+0x5c/0x80 [xfs]
>> [ 44.802478] [c00000001984b980] [c0080000006467b0] xfs_trans_cancel+0x178/0x1b0 [xfs]
>> [ 44.802533] [c00000001984b9d0] [c008000000634a84] xfs_rename+0x9cc/0xd10 [xfs]
>> [ 44.802586] [c00000001984bb10] [c00800000062e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
>> [ 44.802641] [c00000001984bba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
>> [ 44.802644] [c00000001984bc90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
>> [ 44.802648] [c00000001984bde0] [c000000000580520] sys_rename+0x60/0x80
>> [ 44.802652] [c00000001984be10] [c000000000033630] system_call_exception+0x150/0x3b0
>> [ 44.802657] [c00000001984be50] [c00000000000c554] system_call_common+0xf4/0x258
>> [ 44.802661] --- interrupt: c00 at 0x7fffa6482e20
>> [ 44.802664] NIP: 00007fffa6482e20 LR: 00007fffa6055e24 CTR: 0000000000000000
>> [ 44.802667] REGS: c00000001984be80 TRAP: 0c00 Tainted: G W (6.2.0-rc8ssh)
>> [ 44.802670] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
>> [ 44.802678] IRQMASK: 0
>> [ 44.802678] GPR00: 0000000000000026 00007fffa536d220 00007fffa6607300 00007fffa536d288
>> [ 44.802678] GPR04: 000000014f7a6b70 0000000000000000 0700000000000000 0000000000000002
>> [ 44.802678] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> [ 44.802678] GPR12: 0000000000000000 00007fffa53766e0 000000014f795930 0000000000000000
>> [ 44.802678] GPR16: 0000000126b67648 00007fffa6057ce0 0000000000000003 000000000000002b
>> [ 44.802678] GPR20: 0000000000000212 00007fffa536e3a0 00007fffa536e398 00007fff98008690
>> [ 44.802678] GPR24: 0000000000000000 00007fffa536e388 00007fffa536e378 00007fffa536e3b0
>> [ 44.802678] GPR28: 00007fffa6070000 00007fffa60705e0 00007fff98000c10 00007fffa536d288
>> [ 44.802712] NIP [00007fffa6482e20] 0x7fffa6482e20
>> [ 44.802715] LR [00007fffa6055e24] 0x7fffa6055e24
>> [ 44.802717] --- interrupt: c00
>> [ 44.804354] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
>> [ 44.804413] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
>>
>>
>>
>> >> [ 333.390615] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
>> >> [ 333.390645] CPU: 56 PID: 12450 Comm: rm Not tainted 6.2.0-rc4ssh+ #4
>> >> [ 333.390649] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
>> >> [ 333.390652] NIP: c0080000004bfa80 LR: c0080000004bfa4c CTR: c000000000ea28d0
>> >> [ 333.390655] REGS: c0000000442bb8c0 TRAP: 0700 Not tainted (6.2.0-rc4ssh+)
>> >> [ 333.390658] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24002842 XER: 00000000
>> >> [ 333.390666] CFAR: c0080000004bfa54 IRQMASK: 0
>> >> [ 333.390666] GPR00: c00000003b69c0c8 c0000000442bbb60 c008000000568300 0000000000000000
>> >> [ 333.390666] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000004b27d78
>> >> [ 333.390666] GPR08: 0000000000000000 c000000004b27e28 0000000000000000 fffffffffffffffd
>> >> [ 333.390666] GPR12: 0000000000000040 c000004afecc5880 0000000106620918 0000000000000001
>> >> [ 333.390666] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
>> >> [ 333.390666] GPR20: 0000000106620e30 c0000000880ba938 0000000000200000 00000000002ec44d
>> >> [ 333.390666] GPR24: 000000000008170d 000000000000000d c0000000519f4800 00000000002ec44d
>> >> [ 333.390666] GPR28: c0000000880ba800 c00000003b69c000 c0000000833edd20 000000000008170d
>> >> [ 333.390702] NIP [c0080000004bfa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
>> >> [ 333.390756] LR [c0080000004bfa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
>> >> [ 333.390810] Call Trace:
>> >> [ 333.390811] [c0000000442bbb60] [c0000000833edd20] 0xc0000000833edd20 (unreliable)
>> >> [ 333.390816] [c0000000442bbb80] [c0080000004c0094] xfs_iunlink+0x1bc/0x280 [xfs]
>> >> [ 333.390869] [c0000000442bbc00] [c0080000004c3f84] xfs_remove+0x1dc/0x310 [xfs]
>> >> [ 333.390922] [c0000000442bbc70] [c0080000004be180] xfs_vn_unlink+0x68/0xf0 [xfs]
>> >> [ 333.390975] [c0000000442bbcd0] [c000000000576b24] vfs_unlink+0x1b4/0x3d0
>> >
>> > ...that trips when rm tries to remove a file, which means that the call
>> > stack is
>> >
>> > xfs_remove -> xfs_iunlink -> xfs_iunlink_insert_inode ->
>> > xfs_iunlink_update_backref -> xfs_iunlink_lookup <kaboom>
>> >
>> > It looks as though "rm foo" unlinked foo from the directory and was
>> > trying to insert it at the head of one of the unlinked lists in the AGI
>> > buffer. The AGI claims that the list points to an ondisk inode, so the
>> > iunlink code tries to find the incore inode to update the incore list,
>> > fails to find an incore inode, and this is the result...
>>
>> This seems to happen for rename as well. i.e xfs_rename.
>> Does rename path calls rm first, and then create?
>
> Effectively, yes. A "mv a b" will unlink b, and that calls the same
> internal unlink code as an unlink syscall.
>
>> >>
>> >>
>> >> we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
>> >> as the bad commit.
>> >> Short description of commit:
>> >> commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad)
>> >> Author: Dave Chinner <dchinner@redhat.com>
>> >> Date: Thu Jul 14 11:42:39 2022 +1000
>> >>
>> >> xfs: refactor xlog_recover_process_iunlinks()
>> >
>> > ...which was in the middle of the series that reworked thev mount time
>> > iunlink clearing. Oddly, I don't spot any obvious errors in /that/
>> > patch that didn't already exist. But this does make me wonder, does
>> > xfs_repair -n have anything to say about unlinked or orphaned inodes?
>> >
>> > The runtime code expects that every ondisk inode in an iunlink chain has
>> > an incore inode that is linked (via i_{next,prev}_unlinked) to the other
>> > incore inodes in that same chain. If this requirement is not met, then
>> > the WARNings you see will trip, and the fs shuts down.
>> >
>> > My hypothesis here is that one of the AGs has an unprocessed unlinked
>> > list. At mount time, the ondisk log was clean, so mount time log
>> > recovery didn't invoke xlog_recover_process_iunlinks, and the list was
>> > not cleared. The mount code does not construct the incore unlinked list
>> > from an existing ondisk iunlink list, hence the WARNing. Prior to 5.17,
>> > we only manipulated the ondisk unlink list, and the code never noticed
>> > or cared if there were mystery inodes in the list that never went away.
>> >
>> > (Obviously, if something blew up earlier in dmesg, that would be
>> > relevant here.)
>> >
>> > It's possible that we could end up in this situation (clean log,
>> > unlinked inodes) if a previous log recovery was only partially
>> > successful at clearing the unlinked list, since all that code ignores
>> > errors. If that happens, we ... succeed at mounting and clean the log.
>> >
>> > If you're willing to patch your kernels, it would be interesting
>> > to printk if the xfs_read_agi or the xlog_recover_iunlink_bucket calls
>> > in xlog_recover_iunlink_ag returns an error code. It might be too late
>>
>> We can try. Please provide the Patch.
>>
>> > to capture that, hence my suggestion of seeing if xfs_repair -n will
>> > tell us anything else.
>> >
>>
>> Could you please clarify? We should run xfs_repair -n from 5.17-rc2 kernel?
>
> Whatever xfs_repair is installed on the system should suffice to report
> an unlinked inode list and any other errors on the filesystem.
>
Hi Darrick,
Please find the information collected from the system. We added some
debug logs and looks like it is exactly what is happening which you
pointed out.
We added a debug kernel patch to get more info from the system which
you had requested [1]
1. We first breaked into emergency shell where root fs is first getting
mounted on /sysroot as "ro" filesystem. Here are the logs.
[ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
Mounting /sysroot...
[ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
[ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
[ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
[ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
[ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
[ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
[ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
[ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
[ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
[ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
[ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
[ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
[ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
[ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
[ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
[ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
[ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
[ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
<previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
the huge value.
[ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
[ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
[ 17.801292] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:15
[ 17.801298] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:16
[ 17.801303] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:17
[ 17.801309] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:18
[ 17.801315] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:19
[ 17.801320] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:20
[ 17.801325] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:21
[ 17.801331] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:22
[ 17.811059] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:23
[ 17.811276] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:24
[ 17.811282] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:25
[ 17.811288] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:26
[ 17.811293] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:27
[ 17.811299] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:28
[ 17.811304] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:29
[ 17.811310] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:30
[ 17.811315] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:31
[ 17.811320] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:32
[ 17.811326] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:33
[ 17.811331] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:34
[ 17.811337] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:35
[ 17.811342] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:36
[ 17.811347] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:37
[ 17.811353] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:38
[ 17.811358] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:39
[ 17.811364] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:40
[ 17.811369] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:41
[ 17.811375] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:42
[ 17.811380] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:43
[ 17.811386] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:44
[ 17.811391] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:45
[ 17.811397] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:46
[ 17.811402] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:47
[ 17.811408] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:48
[ 17.811413] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:49
[ 17.811419] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:50
[ 17.811424] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:51
[ 17.811430] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:52
[ 17.811435] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:53
[ 17.811441] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:54
[ 17.811446] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:55
[ 17.811452] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:56
[ 17.811457] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:57
[ 17.811462] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:58
[ 17.811468] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:59
[ 17.811474] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:60
[ 17.811480] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:61
[ 17.811485] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:62
[ 17.811491] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:63
[ 17.811496] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:0
[ 17.811502] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:1
[ 17.811507] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:2
[ 17.811513] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:3
[ 17.811518] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:4
[ 17.811524] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:5
[ 17.811529] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:6
[ 17.811535] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:7
[ 17.811540] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:8
[ 17.811546] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:9
[ 17.811551] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:10
[ 17.811557] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:11
[ 17.811562] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:12
[ 17.811568] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:13
[ 17.811573] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:14
[ 17.811578] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:15
[ 17.811584] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:16
[ 17.811589] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:17
[ 17.811595] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:18
[ 17.811600] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:19
[ 17.811605] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:20
[ 17.811611] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:21
[ 17.811616] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:22
[ 17.811621] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:23
[ 17.811627] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:24
[ 17.811632] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:25
[ 17.811638] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:26
[ 17.811643] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:27
[ 17.811649] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:28
[ 17.811654] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:29
[ 17.811660] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:30
[ 17.811665] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:31
[ 17.811671] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:32
[ 17.811676] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:33
[ 17.811682] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:34
[ 17.811687] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:35
[ 17.811693] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:36
[ 17.811698] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:37
[ 17.811704] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:38
[ 17.811709] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:39
[ 17.811715] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:40
[ 17.811720] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:41
[ 17.811726] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:42
[ 17.811731] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:43
[ 17.811737] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:44
[ 17.811742] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:45
[ 17.811748] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:46
[ 17.811753] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:47
[ 17.811759] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:48
[ 17.811764] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:49
[ 17.811770] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:50
[ 17.811775] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:51
[ 17.811780] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:52
[ 17.811786] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:53
[ 17.811791] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:54
[ 17.811797] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:55
[ 17.811802] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:56
[ 17.811807] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:57
[ 17.811812] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:58
[ 17.811818] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:59
[ 17.811824] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:60
[ 17.811829] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:61
[ 17.811835] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:62
[ 17.811840] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:1, bucket:63
[ 17.811846] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:0
[ 17.811851] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:1
[ 17.811857] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:2
[ 17.811862] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:3
[ 17.811868] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:4
[ 17.811873] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:5
[ 17.811879] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:6
[ 17.811884] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:7
[ 17.811890] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:8
[ 17.811895] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:9
[ 17.811900] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:10
[ 17.811906] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:11
[ 17.811912] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:12
[ 17.811917] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:13
[ 17.811922] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:14
[ 17.811928] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:15
[ 17.811933] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:16
[ 17.811939] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:17
[ 17.811944] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:18
[ 17.811950] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:19
[ 17.811955] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:20
[ 17.811960] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:21
[ 17.811966] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:22
[ 17.811971] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:23
[ 17.811977] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:24
[ 17.811982] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:25
[ 17.811988] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:26
[ 17.811993] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:27
[ 17.811999] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:28
[ 17.812004] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:29
[ 17.812010] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:30
[ 17.812015] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:31
[ 17.812021] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:32
[ 17.812026] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:33
[ 17.812031] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:34
[ 17.812037] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:35
[ 17.812042] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:36
[ 17.812048] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:37
[ 17.812053] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:38
[ 17.812058] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:39
[ 17.812064] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:40
[ 17.812070] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:41
[ 17.812075] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:42
[ 17.812080] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:43
[ 17.812086] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:44
[ 17.812091] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:45
[ 17.812097] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:46
[ 17.812102] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:47
[ 17.812107] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:48
[ 17.812113] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:49
[ 17.812118] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:50
[ 17.812123] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:51
[ 17.812129] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:52
[ 17.812134] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:53
[ 17.812139] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:54
[ 17.812145] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:55
[ 17.812150] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:56
[ 17.812156] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:57
[ 17.812161] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:58
[ 17.812166] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:59
[ 17.812172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:60
[ 17.812177] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:61
[ 17.813165] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:62
[ 17.813170] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:2, bucket:63
[ 17.813176] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:0
[ 17.813181] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:1
[ 17.813186] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:2
[ 17.813192] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:3
[ 17.813197] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:4
[ 17.813202] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:5
[ 17.819070] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:6
[ 17.819076] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:7
[ 17.819082] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:8
[ 17.819087] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:9
[ 17.819093] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:10
[ 17.819099] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:11
[ 17.819104] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:12
[ 17.819110] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:13
[ 17.819115] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:14
[ 17.819121] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:15
[ 17.824214] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:16
[ 17.824220] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:17
[ 17.824226] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:18
[ 17.824231] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:19
[ 17.824236] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:20
[ 17.824242] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:21
[ 17.824247] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:22
[ 17.824253] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:23
[ 17.824258] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:24
[ 17.824264] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:25
[ 17.824269] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:26
[ 17.829372] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:27
[ 17.829378] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:28
[ 17.829384] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:29
[ 17.829390] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:30
[ 17.829395] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:31
[ 17.829401] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:32
[ 17.829406] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:33
[ 17.829412] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:34
[ 17.829418] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:35
[ 17.829423] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:36
[ 17.834523] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:37
[ 17.834529] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:38
[ 17.834534] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:39
[ 17.834540] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:40
[ 17.834545] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:41
[ 17.834550] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:42
[ 17.834556] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:43
[ 17.834561] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:44
[ 17.834567] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:45
[ 17.834572] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:46
[ 17.834577] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:47
[ 17.839752] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:48
[ 17.839758] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:49
[ 17.839764] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:50
[ 17.839769] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:51
[ 17.839775] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:52
[ 17.839781] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:53
[ 17.839786] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:54
[ 17.839792] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:55
[ 17.839797] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:56
[ 17.839803] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:57
[ 17.844888] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:58
[ 17.844894] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:59
[ 17.844900] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:60
[ 17.844905] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:61
[ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
[ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
[ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
[ OK ] Mounted /sysroot.
[ OK ] Reached target Initrd Root File System.
2. Then these are the logs from xfs_repair -n /dev/dm-0
Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
printed in above xlog_recover_iunlink_ag() function.
switch_root:/# xfs_repair -n /dev/dm-0
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 2
- agno = 1
- agno = 3
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
would have reset inode 3064909 nlinks from 4294967291 to 2
No modify flag set, skipping filesystem flush and exiting.
3. Then we exit from the shell for the system to continue booting.
Here it will continue.. Just pasting the logs where the warning gets
generated and some extra logs are getting printed for the same inode
with our patch.
it continues
================
[ 587.999113] ------------[ cut here ]------------
[ 587.999121] WARNING: CPU: 48 PID: 2026 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
[ 587.999185] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc xts pseries_rng vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
[ 587.999215] CPU: 48 PID: 2026 Comm: in:imjournal Not tainted 6.2.0-rc8ssh+ #38
[ 587.999219] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
[ 587.999222] NIP: c00800000065fa80 LR: c00800000065fa4c CTR: c000000000ea4d40
[ 587.999226] REGS: c00000001aa83650 TRAP: 0700 Not tainted (6.2.0-rc8ssh+)
[ 587.999228] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24224842 XER: 00000000
[ 587.999236] CFAR: c00800000065fa54 IRQMASK: 0
[ 587.999236] GPR00: c00000004570b2c8 c00000001aa838f0 c008000000708300 0000000000000000
[ 587.999236] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c00000000413faf0
[ 587.999236] GPR08: 0000000000000000 c00000000413fba0 0000000000000000 fffffffffffffffd
[ 587.999236] GPR12: 0000000000000040 c000004afeccd880 0000000000000000 0000000004000000
[ 587.999236] GPR16: c00000001aa83b38 c00000001aa83a38 c00000001aa83a68 c000000035264c00
[ 587.999236] GPR20: c00000004570b200 0000000000008000 c00000000886c400 00000000002ec44d
[ 587.999236] GPR24: 000000000014040d 000000000000000d c000000051875400 00000000002ec44d
[ 587.999236] GPR28: c000000035262c00 c00000004570b200 c00000008f2d8b90 000000000014040d
[ 587.999272] NIP [c00800000065fa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
[ 587.999327] LR [c00800000065fa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
[ 587.999379] Call Trace:
[ 587.999381] [c00000001aa838f0] [c00000008f2d8b90] 0xc00000008f2d8b90 (unreliable)
[ 587.999385] [c00000001aa83910] [c008000000660094] xfs_iunlink+0x1bc/0x2c0 [xfs]
[ 587.999438] [c00000001aa839d0] [c008000000664804] xfs_rename+0x69c/0xd10 [xfs]
[ 587.999491] [c00000001aa83b10] [c00800000065e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
[ 587.999544] [c00000001aa83ba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
[ 587.999549] [c00000001aa83c90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
[ 587.999553] [c00000001aa83de0] [c000000000580520] sys_rename+0x60/0x80
[ 587.999557] [c00000001aa83e10] [c000000000033630] system_call_exception+0x150/0x3b0
[ 587.999562] [c00000001aa83e50] [c00000000000c554] system_call_common+0xf4/0x258
[ 587.999567] --- interrupt: c00 at 0x7fff96082e20
[ 587.999569] NIP: 00007fff96082e20 LR: 00007fff95c45e24 CTR: 0000000000000000
[ 587.999572] REGS: c00000001aa83e80 TRAP: 0c00 Not tainted (6.2.0-rc8ssh+)
[ 587.999575] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
[ 587.999584] IRQMASK: 0
[ 587.999584] GPR00: 0000000000000026 00007fff94f5d220 00007fff96207300 00007fff94f5d288
[ 587.999584] GPR04: 0000000172b76b70 0000000000000000 0600000000000000 0000000000000002
[ 587.999584] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 587.999584] GPR12: 0000000000000000 00007fff94f666e0 0000000172b65930 0000000000000000
[ 587.999584] GPR16: 0000000132fe7648 00007fff95c47ce0 0000000000000000 000000000000004c
[ 587.999584] GPR20: 0000000000000082 00007fff94f5e3a0 00007fff94f5e398 00007fff880029b0
[ 587.999584] GPR24: 0000000000000000 00007fff94f5e388 00007fff94f5e378 00007fff94f5e3b0
[ 587.999584] GPR28: 00007fff95c60000 00007fff95c605e0 00007fff88000c10 00007fff94f5d288
[ 587.999618] NIP [00007fff96082e20] 0x7fff96082e20
[ 587.999620] LR [00007fff95c45e24] 0x7fff95c45e24
[ 587.999622] --- interrupt: c00
[ 587.999624] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
[ 587.999637] ---[ end trace 0000000000000000 ]---
[ 587.999640] xfs_iunlink_update_backref: next_agino: 3064909 cannot be found
[ 587.999643] xfs_iunlink_insert_inode: Cannot find backref for agino:1311757, ip->i_ino:1311757, next_agino: 3064909 agno:0
[ 587.999646] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x9cc/0xd10 [xfs]
^^^ There are the extra info printing the next_agino to be the same
agino 3064909 for xfs_iunlink_lookup has failed.
[ 587.999701] CPU: 48 PID: 2026 Comm: in:imjournal Tainted: G W 6.2.0-rc8ssh+ #38
[ 587.999705] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
[ 587.999708] Call Trace:
[ 587.999709] [c00000001aa838f0] [c000000000e87328] dump_stack_lvl+0x6c/0x9c (unreliable)
[ 587.999715] [c00000001aa83920] [c008000000646a84] xfs_error_report+0x5c/0x80 [xfs]
[ 587.999767] [c00000001aa83980] [c008000000676860] xfs_trans_cancel+0x178/0x1b0 [xfs]
[ 587.999823] [c00000001aa839d0] [c008000000664b34] xfs_rename+0x9cc/0xd10 [xfs]
[ 587.999876] [c00000001aa83b10] [c00800000065e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
[ 587.999929] [c00000001aa83ba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
[ 587.999933] [c00000001aa83c90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
[ 587.999937] [c00000001aa83de0] [c000000000580520] sys_rename+0x60/0x80
[ 587.999941] [c00000001aa83e10] [c000000000033630] system_call_exception+0x150/0x3b0
[ 587.999945] [c00000001aa83e50] [c00000000000c554] system_call_common+0xf4/0x258
[ 587.999950] --- interrupt: c00 at 0x7fff96082e20
[ 587.999952] NIP: 00007fff96082e20 LR: 00007fff95c45e24 CTR: 0000000000000000
[ 587.999955] REGS: c00000001aa83e80 TRAP: 0c00 Tainted: G W (6.2.0-rc8ssh+)
[ 587.999958] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
[ 587.999967] IRQMASK: 0
[ 587.999967] GPR00: 0000000000000026 00007fff94f5d220 00007fff96207300 00007fff94f5d288
[ 587.999967] GPR04: 0000000172b76b70 0000000000000000 0600000000000000 0000000000000002
[ 587.999967] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 587.999967] GPR12: 0000000000000000 00007fff94f666e0 0000000172b65930 0000000000000000
[ 587.999967] GPR16: 0000000132fe7648 00007fff95c47ce0 0000000000000000 000000000000004c
[ 587.999967] GPR20: 0000000000000082 00007fff94f5e3a0 00007fff94f5e398 00007fff880029b0
[ 587.999967] GPR24: 0000000000000000 00007fff94f5e388 00007fff94f5e378 00007fff94f5e3b0
[ 587.999967] GPR28: 00007fff95c60000 00007fff95c605e0 00007fff88000c10 00007fff94f5d288
[ 588.000000] NIP [00007fff96082e20] 0x7fff96082e20
[ 588.000002] LR [00007fff95c45e24] 0x7fff95c45e24
[ 588.000004] --- interrupt: c00
[ 588.012398] Core dump to |/usr/lib/systemd/systemd-coredump pipe failed
[ 588.020328] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
[ 588.020388] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
4. Here is the patch diff which we used to collect the info.
<patch>
=============
root-> git diff
diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
index 5808abab786c..86b8cab7f759 100644
--- a/fs/xfs/xfs_inode.c
+++ b/fs/xfs/xfs_inode.c
@@ -1859,8 +1859,10 @@ xfs_iunlink_update_backref(
return 0;
ip = xfs_iunlink_lookup(pag, next_agino);
- if (!ip)
+ if (!ip) {
+ pr_err("%s: next_agino: %u cannot be found\n", __func__, next_agino);
return -EFSCORRUPTED;
+ }
ip->i_prev_unlinked = prev_agino;
return 0;
}
@@ -1935,8 +1937,11 @@ xfs_iunlink_insert_inode(
* inode.
*/
error = xfs_iunlink_update_backref(pag, agino, next_agino);
- if (error)
+ if (error) {
+ pr_crit("%s: Cannot find backref for agino:%u, ip->i_ino:%llu, next_agino: %u agno:%u\n",
+ __func__, agino, ip->i_ino, next_agino, pag->pag_agno);
return error;
+ }
if (next_agino != NULLAGINO) {
/*
diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
index fc61cc024023..035fc1eba871 100644
--- a/fs/xfs/xfs_log.c
+++ b/fs/xfs/xfs_log.c
@@ -825,6 +825,10 @@ xfs_log_mount_finish(
*/
mp->m_super->s_flags |= SB_ACTIVE;
xfs_log_work_queue(mp);
+ if (xlog_recovery_needed(log))
+ pr_crit("%s: Recovery needed is set\n", __func__);
+ else
+ pr_crit("%s: Recovery needed not set\n", __func__);
if (xlog_recovery_needed(log))
error = xlog_recover_finish(log);
mp->m_super->s_flags &= ~SB_ACTIVE;
diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
index 322eb2ee6c55..6caa8147b443 100644
--- a/fs/xfs/xfs_log_recover.c
+++ b/fs/xfs/xfs_log_recover.c
@@ -2696,8 +2696,13 @@ xlog_recover_iunlink_bucket(
ASSERT(VFS_I(ip)->i_nlink == 0);
ASSERT(VFS_I(ip)->i_mode != 0);
xfs_iflags_clear(ip, XFS_IRECOVERY);
- agino = ip->i_next_unlinked;
+ if (bucket == 13) {
+ pr_crit("%s: bucket: %d, agino: %u, ino: %llu, iget ret: %d, previno:%llu, prev_agino:%u\n",
+ __func__, bucket, agino, ip->i_ino, error, prev_ip ? prev_ip->i_ino : -1, prev_ip ? XFS_INO_TO_AGINO(mp, prev_ip->i_ino) : -1);
+ }
+
+ agino = ip->i_next_unlinked;
if (prev_ip) {
ip->i_prev_unlinked = prev_agino;
xfs_irele(prev_ip);
@@ -2789,8 +2794,11 @@ xlog_recover_iunlink_ag(
* bucket and remaining inodes on it unreferenced and
* unfreeable.
*/
+ pr_crit("%s: Failed in xlog_recover_iunlink_bucket %d\n", __func__, error);
xfs_inodegc_flush(pag->pag_mount);
xlog_recover_clear_agi_bucket(pag, bucket);
+ } else {
+ pr_crit("%s: ran xlog_recover_iunlink_bucket for agi:%u, bucket:%d\n", __func__, pag->pag_agno, bucket);
}
}
> That evidence will guide us towards a kernel patch.
I can spend some more time to debug and understand on how to fix this.
But thought of sharing this info meanwhile and see if there are any
pointers on how to fix this in kernel.
Let me know if any other info is needed. We haven't yet run xfs_repair
on the device w/o -n option.
-ritesh
^ permalink raw reply related [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-03-09 14:26 ` Ritesh Harjani
@ 2023-03-09 17:27 ` Darrick J. Wong
2023-03-16 4:46 ` Ritesh Harjani
2023-03-10 0:29 ` Dave Chinner
1 sibling, 1 reply; 28+ messages in thread
From: Darrick J. Wong @ 2023-03-09 17:27 UTC (permalink / raw)
To: Ritesh Harjani
Cc: shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
TLDR: skip to line 990.
On Thu, Mar 09, 2023 at 07:56:06PM +0530, Ritesh Harjani wrote:
> "Darrick J. Wong" <djwong@kernel.org> writes:
>
> > On Sat, Feb 18, 2023 at 12:47:48PM +0530, shrikanth hegde wrote:
> >>
> >>
> >> On 2/17/23 10:23 PM, Darrick J. Wong wrote:
> >> > On Fri, Feb 17, 2023 at 04:45:12PM +0530, shrikanth hegde wrote:
> >> >> We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in
> >> >> one of our systems. System fails to come up. System was booting well
> >> >> with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel.
> >> >>
> >> >> Panic Log is below.
> >> >> [ 333.390539] ------------[ cut here ]------------
> >> >> [ 333.390552] WARNING: CPU: 56 PID: 12450 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
> >> >
> >> > Hmm, ok, so this is the same if (WARN_ON_ONCE(!ip || !ip->i_ino)) line
> >> > in xfs_iunlink_lookup that I've been bonking my head on the past
> >> > several days. 333 seconds uptime, so I guess this is a pretty recent
> >> > mount. You didn't post a full dmesg, so I can only assume there weren't
> >> > any *other* obvious complaints from XFS when the fs was mounted...
> >> >
> >>
> >> Darrick, Dave. Thank you for taking a look at this. sorry i didnt paste the full log.
> >> Please find the full dmesg below. it was kexec from 5.17-rc2 to 6.2-rc8
> >>
> >>
> >> Starting Reboot via kexec...
> >> [ 71.134231] printk: systemd-shutdow: 37 output lines suppressed due to ratelimiting
> >> [ 71.158255] systemd-shutdown[1]: Syncing filesystems and block devices.
> >> [ 71.160419] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
> >> [ 71.214007] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
> >> [ 71.233182] systemd-shutdown[1]: Unmounting file systems.
> >> [ 71.233845] [2287]: Remounting '/home' read-only in with options 'attr2,inode64,logbufs=8,logbsize=32k,noquota'.
> >> [ 71.234873] [2288]: Unmounting '/home'.
> >> [ 71.237859] XFS (nvme0n1p1): Unmounting Filesystem
> >> [ 71.524111] [2289]: Remounting '/' read-only in with options 'attr2,inode64,logbufs=8,logbsize=32k,noquota'.
> >> [ 71.810094] systemd-shutdown[1]: All filesystems unmounted.
> >> [ 71.810103] systemd-shutdown[1]: Deactivating swaps.
> >> [ 71.810121] systemd-shutdown[1]: All swaps deactivated. pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/li[ 71.810126] systemd-shutdown[1]: Detaching loop devices.'
> >> [ 71.810227] systemd-shutdown[1]: All loop devices detached.
> >> [ 71.810232] systemd-shutdown[1]: Detaching DM devices.
> >> [ 71.932097] printk: shutdown: 8 output lines suppressed due to ratelimiting
> >> [ 71.954484] dracut Warning: Killing all remaining processes
> >> dracut Warning: Killing all remaining processes
> >> [ 72.001360] XFS (dm-0): Unmounting Filesystem
> >> [ 72.393816] dracut Warning: Unmounted /oldroot.
> >> [ 72.409893] dracut: Disassembling device-mapper devices
> >> [ 72.527853] Removing IBM Power 842 compression device
> >> [ 78.084038] kexec_core: Starting new kernel
> >> [ 78.104094] kexec: waiting for cpu 26 (physical 26) to enter 1 state
> >> [ 78.104102] kexec: waiting for cpu 87 (physical 87) to enter 1 state
> >> [ 78.104109] kexec: waiting for cpu 1 (physical 1) to enter 2 state
> >> [ 78.104248] kexec: waiting for cpu 2 (physical 2) to enter 2 state
> >> [ 78.104275] kexec: waiting for cpu 3 (physical 3) to enter 2 state
> >> [ 78.104289] kexec: waiting for cpu 4 (physical 4) to enter 2 state
> >> [ 78.104303] kexec: waiting for cpu 5 (physical 5) to enter 2 state
> >> [ 78.104315] kexec: waiting for cpu 8 (physical 8) to enter 2 state
> >> [ 78.104352] kexec: waiting for cpu 48 (physical 48) to enter 2 state
> >> [ 78.104357] kexec: waiting for cpu 49 (physical 49) to enter 2 state
> >> [ 78.278072] kexec: Starting switchover sequence.
> >> I'm in purgatory
> >> [ 0.000000] radix-mmu: Page sizes from device-tree:
> >> [ 0.000000] radix-mmu: Page size shift = 12 AP=0x0
> >> [ 0.000000] radix-mmu: Page size shift = 16 AP=0x5
> >> [ 0.000000] radix-mmu: Page size shift = 21 AP=0x1
> >> [ 0.000000] radix-mmu: Page size shift = 30 AP=0x2
> >> [ 0.000000] Activating Kernel Userspace Access Prevention
> >> [ 0.000000] Activating Kernel Userspace Execution Prevention
> >> [ 0.000000] radix-mmu: Mapped 0x0000000000000000-0x0000000002600000 with 2.00 MiB pages (exec)
> >> [ 0.000000] radix-mmu: Mapped 0x0000000002600000-0x0000004b00000000 with 2.00 MiB pages
> >> [ 0.000000] lpar: Using radix MMU under hypervisor
> >> [ 0.000000] Linux version 6.2.0-rc8ssh (root@ltcden3-lp1.aus.stglabs.ibm.com) (gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10), GNU ld version 2.30-113.el8) #35 SMP Sat Feb 18 00:41:56 EST 2023
> >> [ 0.000000] Found initrd at 0xc0000000061d0000:0xc00000000ac38d3b
> >> [ 0.000000] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> >> [ 0.000000] printk: bootconsole [udbg0] enabled
> >> [ 0.000000] Partition configured for 96 cpus.
> >> [ 0.000000] CPU maps initialized for 8 threads per core
> >> [ 0.000000] numa: Partition configured for 32 NUMA nodes.
> >> [ 0.000000] -----------------------------------------------------
> >> [ 0.000000] phys_mem_size = 0x4b00000000
> >> [ 0.000000] dcache_bsize = 0x80
> >> [ 0.000000] icache_bsize = 0x80
> >> [ 0.000000] cpu_features = 0x000c00eb8f5f9187
> >> [ 0.000000] possible = 0x000ffbfbcf5fb187
> >> [ 0.000000] always = 0x0000000380008181
> >> [ 0.000000] cpu_user_features = 0xdc0065c2 0xaef60000
> >> [ 0.000000] mmu_features = 0xbc007641
> >> [ 0.000000] firmware_features = 0x000005bfc55bfc57
> >> [ 0.000000] vmalloc start = 0xc008000000000000
> >> [ 0.000000] IO start = 0xc00a000000000000
> >> [ 0.000000] vmemmap start = 0xc00c000000000000
> >> [ 0.000000] -----------------------------------------------------
> >> [ 0.000000] numa: NODE_DATA [mem 0x4afe663780-0x4afe66aeff]
> >> [ 0.000000] rfi-flush: fallback displacement flush available
> >> [ 0.000000] count-cache-flush: hardware flush enabled.
> >> [ 0.000000] link-stack-flush: software flush enabled.
> >> [ 0.000000] stf-barrier: eieio barrier available
> >> [ 0.000000] PPC64 nvram contains 15360 bytes
> >> [ 0.000000] barrier-nospec: using ORI speculation barrier
> >> [ 0.000000] Zone ranges:
> >> [ 0.000000] Normal [mem 0x0000000000000000-0x0000004affffffff]
> >> [ 0.000000] Device empty
> >> [ 0.000000] Movable zone start for each node
> >> [ 0.000000] Early memory node ranges
> >> [ 0.000000] node 2: [mem 0x0000000000000000-0x0000004affffffff]
> >> [ 0.000000] Initializing node 0 as memoryless
> >> [ 0.000000] Initmem setup node 0 as memoryless
> >> [ 0.000000] Initializing node 1 as memoryless
> >> [ 0.000000] Initmem setup node 1 as memoryless
> >> [ 0.000000] Initmem setup node 2 [mem 0x0000000000000000-0x0000004affffffff]
> >> [ 0.000000] Initializing node 3 as memoryless
> >> [ 0.000000] Initmem setup node 3 as memoryless
> >> [ 0.000000] Initializing node 4 as memoryless
> >> [ 0.000000] Initmem setup node 4 as memoryless
> >> [ 0.000000] Initializing node 5 as memoryless
> >> [ 0.000000] Initmem setup node 5 as memoryless
> >> [ 0.000000] Initializing node 6 as memoryless
> >> [ 0.000000] Initmem setup node 6 as memoryless
> >> [ 0.000000] Initializing node 7 as memoryless
> >> [ 0.000000] Initmem setup node 7 as memoryless
> >> [ 0.000000] Initializing node 8 as memoryless
> >> [ 0.000000] Initmem setup node 8 as memoryless
> >> [ 0.000000] Initializing node 9 as memoryless
> >> [ 0.000000] Initmem setup node 9 as memoryless
> >> [ 0.000000] Initializing node 10 as memoryless
> >> [ 0.000000] Initmem setup node 10 as memoryless
> >> [ 0.000000] Initializing node 11 as memoryless
> >> [ 0.000000] Initmem setup node 11 as memoryless
> >> [ 0.000000] Initializing node 12 as memoryless
> >> [ 0.000000] Initmem setup node 12 as memoryless
> >> [ 0.000000] Initializing node 13 as memoryless
> >> [ 0.000000] Initmem setup node 13 as memoryless
> >> [ 0.000000] Initializing node 14 as memoryless
> >> [ 0.000000] Initmem setup node 14 as memoryless
> >> [ 0.000000] Initializing node 15 as memoryless
> >> [ 0.000000] Initmem setup node 15 as memoryless
> >> [ 0.000000] Initializing node 16 as memoryless
> >> [ 0.000000] Initmem setup node 16 as memoryless
> >> [ 0.000000] Initializing node 17 as memoryless
> >> [ 0.000000] Initmem setup node 17 as memoryless
> >> [ 0.000000] Initializing node 18 as memoryless
> >> [ 0.000000] Initmem setup node 18 as memoryless
> >> [ 0.000000] Initializing node 19 as memoryless
> >> [ 0.000000] Initmem setup node 19 as memoryless
> >> [ 0.000000] Initializing node 20 as memoryless
> >> [ 0.000000] Initmem setup node 20 as memoryless
> >> [ 0.000000] Initializing node 21 as memoryless
> >> [ 0.000000] Initmem setup node 21 as memoryless
> >> [ 0.000000] Initializing node 22 as memoryless
> >> [ 0.000000] Initmem setup node 22 as memoryless
> >> [ 0.000000] Initializing node 23 as memoryless
> >> [ 0.000000] Initmem setup node 23 as memoryless
> >> [ 0.000000] Initializing node 24 as memoryless
> >> [ 0.000000] Initmem setup node 24 as memoryless
> >> [ 0.000000] Initializing node 25 as memoryless
> >> [ 0.000000] Initmem setup node 25 as memoryless
> >> [ 0.000000] Initializing node 26 as memoryless
> >> [ 0.000000] Initmem setup node 26 as memoryless
> >> [ 0.000000] Initializing node 27 as memoryless
> >> [ 0.000000] Initmem setup node 27 as memoryless
> >> [ 0.000000] Initializing node 28 as memoryless
> >> [ 0.000000] Initmem setup node 28 as memoryless
> >> [ 0.000000] Initializing node 29 as memoryless
> >> [ 0.000000] Initmem setup node 29 as memoryless
> >> [ 0.000000] Initializing node 30 as memoryless
> >> [ 0.000000] Initmem setup node 30 as memoryless
> >> [ 0.000000] Initializing node 31 as memoryless
> >> [ 0.000000] Initmem setup node 31 as memoryless
> >> [ 0.000000] percpu: Embedded 10 pages/cpu s601512 r0 d53848 u655360
> >> [ 0.000000] Fallback order for Node 0: 0 2
> >> [ 0.000000] Fallback order for Node 1: 1 2
> >> [ 0.000000] Fallback order for Node 2: 2
> >> [ 0.000000] Fallback order for Node 3: 3 2
> >> [ 0.000000] Fallback order for Node 4: 4 2
> >> [ 0.000000] Fallback order for Node 5: 5 2
> >> [ 0.000000] Fallback order for Node 6: 6 2
> >> [ 0.000000] Fallback order for Node 7: 7 2
> >> [ 0.000000] Fallback order for Node 8: 8 2
> >> [ 0.000000] Fallback order for Node 9: 9 2
> >> [ 0.000000] Fallback order for Node 10: 10 2
> >> [ 0.000000] Fallback order for Node 11: 11 2
> >> [ 0.000000] Fallback order for Node 12: 12 2
> >> [ 0.000000] Fallback order for Node 13: 13 2
> >> [ 0.000000] Fallback order for Node 14: 14 2
> >> [ 0.000000] Fallback order for Node 15: 15 2
> >> [ 0.000000] Fallback order for Node 16: 16 2
> >> [ 0.000000] Fallback order for Node 17: 17 2
> >> [ 0.000000] Fallback order for Node 18: 18 2
> >> [ 0.000000] Fallback order for Node 19: 19 2
> >> [ 0.000000] Fallback order for Node 20: 20 2
> >> [ 0.000000] Fallback order for Node 21: 21 2
> >> [ 0.000000] Fallback order for Node 22: 22 2
> >> [ 0.000000] Fallback order for Node 23: 23 2
> >> [ 0.000000] Fallback order for Node 24: 24 2
> >> [ 0.000000] Fallback order for Node 25: 25 2
> >> [ 0.000000] Fallback order for Node 26: 26 2
> >> [ 0.000000] Fallback order for Node 27: 27 2
> >> [ 0.000000] Fallback order for Node 28: 28 2
> >> [ 0.000000] Fallback order for Node 29: 29 2
> >> [ 0.000000] Fallback order for Node 30: 30 2
> >> [ 0.000000] Fallback order for Node 31: 31 2
> >> [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 4910400
> >> [ 0.000000] Policy zone: Normal
> >> [ 0.000000] Kernel command line: root=/dev/mapper/rhel_ltcden3--lp1-root
> >> [ 0.000000] random: crng init done
> >> [ 0.000000] Dentry cache hash table entries: 16777216 (order: 11, 134217728 bytes, linear)
> >> [ 0.000000] Inode-cache hash table entries: 8388608 (order: 10, 67108864 bytes, linear)
> >> [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
> >> [ 0.000000] Memory: 313817216K/314572800K available (15168K kernel code, 5632K rwdata, 17600K rodata, 5440K init, 2721K bss, 755584K reserved, 0K cma-reserved)
> >> [ 0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=96, Nodes=32
> >> [ 0.000000] ftrace: allocating 38156 entries in 14 pages
> >> [ 0.000000] ftrace: allocated 14 pages with 3 groups
> >> [ 0.000000] trace event string verifier disabled
> >> [ 0.000000] rcu: Hierarchical RCU implementation.
> >> [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=2048 to nr_cpu_ids=96.
> >> [ 0.000000] Rude variant of Tasks RCU enabled.
> >> [ 0.000000] Tracing variant of Tasks RCU enabled.
> >> [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
> >> [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=96
> >> [ 0.000000] NR_IRQS: 512, nr_irqs: 512, preallocated irqs: 16
> >> [ 0.000000] xive: Using IRQ range [400000-40005f]
> >> [ 0.000000] xive: Interrupt handling initialized with spapr backend
> >> [ 0.000000] xive: Using priority 7 for all interrupts
> >> [ 0.000000] xive: Using 64kB queues
> >> [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
> >> [ 0.000001] time_init: 56 bit decrementer (max: 7fffffffffffff)
> >> [ 0.000021] clocksource: timebase: mask: 0xffffffffffffffff max_cycles: 0x761537d007, max_idle_ns: 440795202126 ns
> >> [ 0.000055] clocksource: timebase mult[1f40000] shift[24] registered
> >> [ 0.000233] Console: colour dummy device 80x25
> >> [ 0.000252] printk: console [hvc0] enabled
> >> [ 0.000252] printk: console [hvc0] enabled
> >> [ 0.000269] printk: bootconsole [udbg0] disabled
> >> [ 0.000269] printk: bootconsole [udbg0] disabled
> >> [ 0.000360] pid_max: default: 98304 minimum: 768
> >> [ 0.000481] LSM: initializing lsm=capability,yama,integrity,selinux,bpf
> >> [ 0.000550] Yama: becoming mindful.
> >> [ 0.000565] SELinux: Initializing.
> >> [ 0.000568] SELinux: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE is non-zero. This is deprecated and will be rejected in a future kernel release.
> >> [ 0.000573] SELinux: https://github.com/SELinuxProject/selinux-kernel/wiki/DEPRECATE-checkreqprot
> >> [ 0.000747] LSM support for eBPF active
> >> [ 0.000929] Mount-cache hash table entries: 262144 (order: 5, 2097152 bytes, linear)
> >> [ 0.001056] Mountpoint-cache hash table entries: 262144 (order: 5, 2097152 bytes, linear)
> >> [ 0.003430] cblist_init_generic: Setting adjustable number of callback queues.
> >> [ 0.003454] cblist_init_generic: Setting shift to 7 and lim to 1.
> >> [ 0.003486] cblist_init_generic: Setting shift to 7 and lim to 1.
> >> [ 0.003507] POWER10 performance monitor hardware support registered
> >> [ 0.003537] rcu: Hierarchical SRCU implementation.
> >> [ 0.003540] rcu: Max phase no-delay instances is 1000.
> >> [ 0.004445] smp: Bringing up secondary CPUs ...
> >> [ 0.022208] smp: Brought up 1 node, 96 CPUs
> >> [ 0.022218] numa: Node 2 CPUs: 0-95
> >> [ 0.022222] Big cores detected but using small core scheduling
> >> [ 0.033289] devtmpfs: initialized
> >> [ 0.042965] PCI host bridge /pci@800000020000019 ranges:
> >> [ 0.042984] MEM 0x0000040080000000..0x00000400feffffff -> 0x0000000080000000
> >> [ 0.042988] MEM 0x0000044000000000..0x0000047fffffffff -> 0x0006204000000000
> >> [ 0.043060] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
> >> [ 0.043066] futex hash table entries: 32768 (order: 6, 4194304 bytes, linear)
> >> [ 0.043643] NET: Registered PF_NETLINK/PF_ROUTE protocol family
> >> [ 0.043801] audit: initializing netlink subsys (disabled)
> >> [ 0.043903] audit: type=2000 audit(1676701683.040:1): state=initialized audit_enabled=0 res=1
> >> [ 0.043954] thermal_sys: Registered thermal governor 'fair_share'
> >> [ 0.043955] thermal_sys: Registered thermal governor 'step_wise'
> >> [ 0.044007] cpuidle: using governor menu
> >> [ 0.044306] pstore: Registered nvram as persistent store backend
> >> [ 0.044682] EEH: pSeries platform initialized
> >> [ 0.055324] PCI: Probing PCI hardware
> >> [ 0.055372] PCI host bridge to bus 0019:01
> >> [ 0.055376] pci_bus 0019:01: root bus resource [mem 0x40080000000-0x400feffffff] (bus address [0x80000000-0xfeffffff])
> >> [ 0.055381] pci_bus 0019:01: root bus resource [mem 0x44000000000-0x47fffffffff 64bit] (bus address [0x6204000000000-0x6207fffffffff])
> >> [ 0.055386] pci_bus 0019:01: root bus resource [bus 01-ff]
> >> [ 0.056001] pci 0019:01:00.0: No hypervisor support for SR-IOV on this device, IOV BARs disabled.
> >> [ 0.064978] IOMMU table initialized, virtual merging enabled
> >> [ 0.065086] pci 0019:01:00.0: Adding to iommu group 0
> >> [ 0.066308] EEH: Capable adapter found: recovery enabled.
> >> [ 0.066550] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
> >> [ 0.066812] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
> >> [ 0.066817] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
> >> [ 0.066821] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
> >> [ 0.066824] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
> >> [ 0.085068] cryptd: max_cpu_qlen set to 1000
> >> [ 0.085368] iommu: Default domain type: Translated
> >> [ 0.085371] iommu: DMA domain TLB invalidation policy: strict mode
> >> [ 0.085491] SCSI subsystem initialized
> >> [ 0.085517] usbcore: registered new interface driver usbfs
> >> [ 0.085523] usbcore: registered new interface driver hub
> >> [ 0.085542] usbcore: registered new device driver usb
> >> [ 0.085563] pps_core: LinuxPPS API ver. 1 registered
> >> [ 0.085565] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
> >> [ 0.085569] PTP clock support registered
> >> [ 0.085628] EDAC MC: Ver: 3.0.0
> >> [ 0.085885] NetLabel: Initializing
> >> [ 0.085887] NetLabel: domain hash size = 128
> >> [ 0.085889] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
> >> [ 0.085903] NetLabel: unlabeled traffic allowed by default
> >> [ 0.085956] vgaarb: loaded
> >> [ 0.086157] clocksource: Switched to clocksource timebase
> >> [ 0.086451] VFS: Disk quotas dquot_6.6.0
> >> [ 0.086480] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)
> >> [ 0.088080] NET: Registered PF_INET protocol family
> >> [ 0.088237] IP idents hash table entries: 262144 (order: 5, 2097152 bytes, linear)
> >> [ 0.091345] tcp_listen_portaddr_hash hash table entries: 65536 (order: 4, 1048576 bytes, linear)
> >> [ 0.091454] Table-perturb hash table entries: 65536 (order: 2, 262144 bytes, linear)
> >> [ 0.091480] TCP established hash table entries: 524288 (order: 6, 4194304 bytes, linear)
> >> [ 0.092201] TCP bind hash table entries: 65536 (order: 5, 2097152 bytes, linear)
> >> [ 0.092386] TCP: Hash tables configured (established 524288 bind 65536)
> >> [ 0.092708] MPTCP token hash table entries: 65536 (order: 4, 1572864 bytes, linear)
> >> [ 0.092826] UDP hash table entries: 65536 (order: 5, 2097152 bytes, linear)
> >> [ 0.093046] UDP-Lite hash table entries: 65536 (order: 5, 2097152 bytes, linear)
> >> [ 0.093402] NET: Registered PF_UNIX/PF_LOCAL protocol family
> >> [ 0.093413] NET: Registered PF_XDP protocol family
> >> [ 0.093509] PCI: CLS 128 bytes, default 128
> >> [ 0.093638] Unpacking initramfs...
> >> [ 0.094862] vio_register_device_node: node lid missing 'reg'
> >> [ 0.103665] vas: GZIP feature is available
> >> [ 0.104512] hv-24x7: read 548 catalog entries, created 387 event attrs (0 failures), 387 descs
> >> [ 0.108478] Initialise system trusted keyrings
> >> [ 0.108493] Key type blacklist registered
> >> [ 0.108560] workingset: timestamp_bits=38 max_order=23 bucket_order=0
> >> [ 0.108587] zbud: loaded
> >> [ 0.108988] integrity: Platform Keyring initialized
> >> [ 0.119068] NET: Registered PF_ALG protocol family
> >> [ 0.119083] Key type asymmetric registered
> >> [ 0.119086] Asymmetric key parser 'x509' registered
> >> [ 0.119120] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
> >> [ 0.119182] io scheduler mq-deadline registered
> >> [ 0.119185] io scheduler kyber registered
> >> [ 0.119198] io scheduler bfq registered
> >> [ 0.120970] atomic64_test: passed
> >> [ 0.121210] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
> >> [ 0.121214] PowerPC PowerNV PCI Hotplug Driver version: 0.1
> >> [ 0.121532] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> >> [ 0.121728] Non-volatile memory driver v1.3
> >> [ 0.122174] rdac: device handler registered
> >> [ 0.122215] hp_sw: device handler registered
> >> [ 0.122218] emc: device handler registered
> >> [ 0.122260] alua: device handler registered
> >> [ 0.122450] usbcore: registered new interface driver usbserial_generic
> >> [ 0.122457] usbserial: USB Serial support registered for generic
> >> [ 0.122529] mousedev: PS/2 mouse device common for all mice
> >> [ 0.122644] rtc-generic rtc-generic: registered as rtc0
> >> [ 0.122676] rtc-generic rtc-generic: setting system clock to 2023-02-18T06:28:03 UTC (1676701683)
> >> [ 0.122755] xcede: xcede_record_size = 10
> >> [ 0.122758] xcede: Record 0 : hint = 1, latency = 0x1800 tb ticks, Wake-on-irq = 1
> >> [ 0.122765] xcede: Record 1 : hint = 2, latency = 0x3c00 tb ticks, Wake-on-irq = 0
> >> [ 0.122769] cpuidle: Skipping the 2 Extended CEDE idle states
> >> [ 0.122771] cpuidle: Fixed up CEDE exit latency to 12 us
> >> [ 0.123865] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sync_size new:65536 old:0
> >> [ 0.123871] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sync_sg new:510 old:0
> >> [ 0.123875] nx_compress_pseries ibm,compression-v1: nx842_OF_upd: max_sg_len new:4080 old:0
> >> [ 0.124018] hid: raw HID events driver (C) Jiri Kosina
> >> [ 0.124042] usbcore: registered new interface driver usbhid
> >> [ 0.124048] usbhid: USB HID core driver
> >> [ 0.124069] drop_monitor: Initializing network drop monitor service
> >> [ 0.134168] Initializing XFRM netlink socket
> >> [ 0.134234] NET: Registered PF_INET6 protocol family
> >> [ 0.134747] Segment Routing with IPv6
> >> [ 0.134756] In-situ OAM (IOAM) with IPv6
> >> [ 0.134776] NET: Registered PF_PACKET protocol family
> >> [ 0.134817] mpls_gso: MPLS GSO support
> >> [ 0.134836] secvar-sysfs: secvar: failed to retrieve secvar operations.
> >> [ 0.139134] registered taskstats version 1
> >> [ 0.140964] Loading compiled-in X.509 certificates
> >> [ 0.156881] Loaded X.509 cert 'Build time autogenerated kernel key: 7b04a1cdeda81c05f7a701657946db5548da6201'
> >> [ 0.157494] zswap: loaded using pool lzo/zbud
> >> [ 0.160050] page_owner is disabled
> >> [ 0.160226] pstore: Using crash dump compression: deflate
> >> [ 0.972073] Freeing initrd memory: 76160K
> >> [ 0.974020] Key type encrypted registered
> >> [ 0.974056] Secure boot mode disabled
> >> [ 0.974060] ima: No TPM chip found, activating TPM-bypass!
> >> [ 0.974067] Loading compiled-in module X.509 certificates
> >> [ 0.974567] Loaded X.509 cert 'Build time autogenerated kernel key: 7b04a1cdeda81c05f7a701657946db5548da6201'
> >> [ 0.974571] ima: Allocated hash algorithm: sha256
> >> [ 0.974598] Secure boot mode disabled
> >> [ 0.974615] Trusted boot mode disabled
> >> [ 0.974617] ima: No architecture policies found
> >> [ 0.974629] evm: Initialising EVM extended attributes:
> >> [ 0.974631] evm: security.selinux
> >> [ 0.974633] evm: security.SMACK64 (disabled)
> >> [ 0.974635] evm: security.SMACK64EXEC (disabled)
> >> [ 0.974637] evm: security.SMACK64TRANSMUTE (disabled)
> >> [ 0.974639] evm: security.SMACK64MMAP (disabled)
> >> [ 0.974641] evm: security.apparmor (disabled)
> >> [ 0.974642] evm: security.ima
> >> [ 0.974644] evm: security.capability
> >> [ 0.974646] evm: HMAC attrs: 0x1
> >> [ 0.974676] alg: No test for 842 (842-nx)
> >> [ 0.982519] Freeing unused kernel image (initmem) memory: 5440K
> >> [ 1.086157] Run /init as init process
> >> [ 1.092664] systemd[1]: systemd 239 (239-58.el8) running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy)
> >> [ 1.092708] systemd[1]: Detected virtualization powervm.
> >> [ 1.092714] systemd[1]: Detected architecture ppc64-le.
> >> [ 1.092718] systemd[1]: Running in initial RAM disk.
> >>
> >> Welcome to Red Hat Enterprise Linux 8.6 (Ootpa) dracut-049-201.git20220131.el8 (Initramfs)!
> >>
> >> [ 1.246394] systemd[1]: Set hostname to <ltcden3-lp1.aus.stglabs.ibm.com>.
> >> [ 1.321102] systemd[1]: Listening on Journal Socket.
> >> [ OK ] Listening on Journal Socket.
> >> [ 1.322421] systemd[1]: Started Hardware RNG Entropy Gatherer Daemon.
> >> [ OK ] Started Hardware RNG Entropy Gatherer Daemon.
> >> [ 1.323252] systemd[1]: Starting Create list of required static device nodes for the current kernel...
> >> Starting Create list of required st…ce nodes for the current kernel...
> >> [ 1.323333] systemd[1]: Reached target Local File Systems.
> >> [ OK ] Reached target Local File Systems.
> >> [ 1.324085] systemd[1]: Started Memstrack Anylazing Service.
> >> [ OK ] Started Memstrack Anylazing Service.
> >> [ OK ] Reached target Slices.
> >> [ OK ] Listening on udev Kernel Socket.
> >> [ OK ] Listening on Journal Socket (/dev/log).
> >> Starting Journal Service...
> >> Starting Create Volatile Files and Directories...
> >> [ OK ] Reached target Swap.
> >> [ OK ] Reached target Timers.
> >> Starting Setup Virtual Console...
> >> Starting Load Kernel Modules...
> >> [ OK ] Listening on udev Control Socket.
> >> [ OK ] Reached target Sockets.
> >> [ OK ] Started Create list of required sta…vice nodes for the current kernel.
> >> [ OK ] Started Create Volatile Files and Directories.
> >> Starting Create Static Device Nodes in /dev...
> >> [FAILED] Failed to start Load Kernel Modules.
> >> See 'systemctl status systemd-modules-load.service' for details.
> >> Starting Apply Kernel Variables...
> >> [ OK ] Started Create Static Device Nodes in /dev.
> >> [ OK ] Started Apply Kernel Variables.
> >> [ OK ] Started Journal Service.
> >> [ OK ] Started Setup Virtual Console.
> >> Starting dracut cmdline hook...
> >> [ OK ] Started dracut cmdline hook.
> >> Starting dracut pre-udev hook...
> >> [ 1.477216] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
> >> [ 1.477252] device-mapper: uevent: version 1.0.3
> >> [ 1.477339] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
> >> [ OK ] Started dracut pre-udev hook.
> >> Starting udev Kernel Device Manager...
> >> [ OK ] Started udev Kernel Device Manager.
> >> Starting udev Coldplug all Devices...
> >> Mounting Kernel Configuration File System...
> >> [ OK ] Mounted Kernel Configuration File System.
> >> [ 1.651355] synth uevent: /devices/vio: failed to send uevent
> >> [ 1.651365] vio vio: uevent: failed to send synthetic uevent: -19
> >> [ 1.651402] synth uevent: /devices/vio/4000: failed to send uevent
> >> [ 1.651406] vio 4000: uevent: failed to send synthetic uevent: -19
> >> [ 1.651415] synth uevent: /devices/vio/4001: failed to send uevent
> >> [ 1.651418] vio 4001: uevent: failed to send synthetic uevent: -19
> >> [ 1.651428] synth uevent: /devices/vio/4002: failed to send uevent
> >> [ 1.651431] vio 4002: uevent: failed to send synthetic uevent: -19
> >> [ 1.651441] synth uevent: /devices/vio/4004: failed to send uevent
> >> [ 1.651444] vio 4004: uevent: failed to send synthetic uevent: -19
> >> [ OK ] Started udev Coldplug all Devices.
> >> [ OK ] Reached target System Initialization.
> >> Starting Show Plymouth Boot Screen...
> >> Starting dracut initqueue hook...
> >> [ OK ] Started Show Plymouth Boot Screen.
> >> [ OK ] Started Forward Password Requests to Plymouth Directory Watch.
> >> [ OK ] Reached target Paths.
> >> [ OK ] Reached target Basic System.
> >> [ 1.709851] ibmveth 30000002 net0: renamed from eth0
> >> [ 1.712196] nvme nvme0: pci function 0019:01:00.0
> >> [ 1.714161] ibmvscsi 30000065: SRP_VERSION: 16.a
> >> [ 1.714223] ibmvscsi 30000065: Maximum ID: 64 Maximum LUN: 32 Maximum Channel: 3
> >> [ 1.714227] scsi host0: IBM POWER Virtual SCSI Adapter 1.5.9
> >> [ 1.714365] ibmvscsi 30000065: partner initialization complete
> >> [ 1.714391] ibmvscsi 30000065: host srp version: 16.a, host partition ltcden3-vios1 (100), OS 3, max io 524288
> >> [ 1.714421] ibmvscsi 30000065: Client reserve enabled
> >> [ 1.714426] ibmvscsi 30000065: sent SRP login
> >> [ 1.714448] ibmvscsi 30000065: SRP_LOGIN succeeded
> >> [ 1.721611] nvme nvme0: Shutdown timeout set to 8 seconds
> >> [ 1.737117] scsi 0:0:1:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
> >> [ 1.738038] scsi 0:0:2:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
> >> [ 1.738364] scsi 0:0:3:0: Direct-Access AIX VDASD 0001 PQ: 0 ANSI: 3
> >> [ 1.750754] nvme nvme0: 32/0/0 default/read/poll queues
> >> [ 1.754482] nvme0n1: p1 p2 p3
> >> [ 1.772868] scsi 0:0:1:0: Attached scsi generic sg0 type 0
> >> [ 1.772898] scsi 0:0:2:0: Attached scsi generic sg1 type 0
> >> [ 1.772920] scsi 0:0:3:0: Attached scsi generic sg2 type 0
> >> [ 1.794722] sd 0:0:2:0: [sda] 629145600 512-byte logical blocks: (322 GB/300 GiB)
> >> [ 1.794757] sd 0:0:2:0: [sda] Write Protect is off
> >> [ 1.794758] sd 0:0:1:0: [sdb] 209715200 512-byte logical blocks: (107 GB/100 GiB)
> >> [ 1.794790] sd 0:0:2:0: [sda] Cache data unavailable
> >> [ 1.794792] sd 0:0:1:0: [sdb] Write Protect is off
> >> [ 1.794796] sd 0:0:2:0: [sda] Assuming drive cache: write through
> >> [ 1.794826] sd 0:0:1:0: [sdb] Cache data unavailable
> >> [ 1.794829] sd 0:0:1:0: [sdb] Assuming drive cache: write through
> >> [ 1.794943] sd 0:0:3:0: [sdc] 91750400 4096-byte logical blocks: (376 GB/350 GiB)
> >> [ 1.794979] sd 0:0:3:0: [sdc] Write Protect is off
> >> [ 1.795008] sd 0:0:3:0: [sdc] Cache data unavailable
> >> [ 1.795011] sd 0:0:3:0: [sdc] Assuming drive cache: write through
> >> [ 1.796625] sdb: sdb1 sdb2 sdb3
> >> [ 1.796717] sdc: sdc1
> >> [ 1.796720] sda: sda1 sda2
> >> [ 1.796752] sd 0:0:1:0: [sdb] Attached SCSI disk
> >> [ 1.796820] sd 0:0:3:0: [sdc] Attached SCSI disk
> >> [ 1.796841] sd 0:0:2:0: [sda] Attached SCSI disk
> >> [ OK ] Found device /dev/mapper/rhel_ltcden3--lp1-root.
> >> [ OK ] Reached target Initrd Root Device.
> >> [ OK ] Started dracut initqueue hook.
> >> Starting File System Check on /dev/mapper/rhel_ltcden3--lp1-root...
> >> [ OK ] Reached target Remote File Systems (Pre).
> >> [ OK ] Reached target Remote File Systems.
> >> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
> >> Mounting /sysroot...
> >> [ 3.060638] SGI XFS with ACLs, security attributes, quota, no debug enabled
> >> [ 3.062369] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
> >> [ 3.109076] XFS (dm-0): Ending clean mount
> >> [ OK ] Mounted /sysroot.
> >> [ OK ] Reached target Initrd Root File System.
> >> Starting Reload Configuration from the Real Root...
> >> [ OK ] Started Reload Configuration from the Real Root.
> >> [ OK ] Reached target Initrd File Systems.
> >> [ OK ] Reached target Initrd Default Target.
> >> Starting dracut pre-pivot and cleanup hook...
> >> [ OK ] Started dracut pre-pivot and cleanup hook.
> >> Starting Cleaning Up and Shutting Down Daemons...
> >> [ OK ] Stopped dracut pre-pivot and cleanup hook.
> >> [ OK ] Stopped target Remote File Systems.
> >> [ OK ] Stopped target Initrd Default Target.
> >> [ OK ] Stopped target Timers.
> >> [ OK ] Stopped target Initrd Root Device.
> >> [ OK ] Stopped target Remote File Systems (Pre).
> >> [ OK ] Stopped dracut initqueue hook.
> >> Starting Setup Virtual Console...
> >> [ OK ] Stopped target Basic System.
> >> [ OK ] Stopped target System Initialization.
> >> [ OK ] Stopped Create Volatile Files and Directories.
> >> [ OK ] Stopped Apply Kernel Variables.
> >> [ OK ] Stopped udev Coldplug all Devices.
> >> Stopping udev Kernel Device Manager...
> >> [ OK ] Stopped target Swap.
> >> [ OK ] Stopped target Paths.
> >> [ OK ] Stopped target Sockets.
> >> [ OK ] Stopped target Slices.
> >> Starting Plymouth switch root service...
> >> [ OK ] Stopped target Local File Systems.
> >> [ OK ] Started Cleaning Up and Shutting Down Daemons.
> >> [ OK ] Started Plymouth switch root service.
> >> [ OK ] Started Setup Virtual Console.
> >> [ OK ] Stopped udev Kernel Device Manager.
> >> [ OK ] Stopped Create Static Device Nodes in /dev.
> >> [ OK ] Stopped Create list of required sta…vice nodes for the current kernel.
> >> Stopping Hardware RNG Entropy Gatherer Daemon...
> >> [ OK ] Stopped dracut pre-udev hook.
> >> [ OK ] Stopped dracut cmdline hook.
> >> [ OK ] Closed udev Control Socket.
> >> [ OK ] Closed udev Kernel Socket.
> >> Starting Cleanup udevd DB...
> >> [ OK ] Stopped Hardware RNG Entropy Gatherer Daemon.
> >> [ OK ] Started Cleanup udevd DB.
> >> [ OK ] Reached target Switch Root.
> >> Starting Switch Root...
> >> [ 3.449370] printk: systemd: 22 output lines suppressed due to ratelimiting
> >> [ 3.593463] SELinux: Runtime disable is deprecated, use selinux=0 on the kernel cmdline.
> >> [ 3.593471] SELinux: https://github.com/SELinuxProject/selinux-kernel/wiki/DEPRECATE-runtime-disable
> >> [ 19.036134] SELinux: Disabled at runtime.
> >> [ 19.196154] audit: type=1404 audit(1676701702.570:2): enforcing=0 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=0 old-enabled=1 lsm=selinux res=1
> >> [ 19.201608] systemd[1]: systemd 239 (239-58.el8) running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy)
> >> [ 19.201637] systemd[1]: Detected virtualization powervm.
> >> [ 19.201642] systemd[1]: Detected architecture ppc64-le.
> >>
> >> Welcome to Red Hat Enterprise Linux 8.6 (Ootpa)!
> >>
> >> [ 19.202637] systemd[1]: Set hostname to <ltcden3-lp1.aus.stglabs.ibm.com>.
> >> [ 21.777702] systemd[1]: systemd-journald.service: Succeeded.
> >> [ 21.778191] systemd[1]: initrd-switch-root.service: Succeeded.
> >> [ 21.778387] systemd[1]: Stopped Switch Root.
> >> [ OK ] Stopped Switch Root.
> >> [ 21.778748] systemd[1]: systemd-journald.service: Service has no hold-off time (RestartSec=0), scheduling restart.
> >> [ 21.778795] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
> >> [ 21.778847] systemd[1]: Stopped Journal Service.
> >> [ OK ] Stopped Journal Service.
> >> Starting Journal Service...
> >> [ OK ] Stopped Plymouth switch root service.
> >> [ OK ] Stopped target Switch Root.
> >> [ OK ] Listening on udev Kernel Socket.
> >> [ OK ] Listening on initctl Compatibility Named Pipe.
> >> [ OK ] Listening on Process Core Dump Socket.
> >> Mounting Huge Pages File System...
> >> Starting Load Kernel Modules...
> >> Starting Read and set NIS domainname from /etc/sysconfig/network...
> >> Activating swap /dev/mapper/rhel_ltcden3--lp1-swap...
> >> [ OK ] Created slice system-serial\x2dgetty.slice.
> >> [ OK ] Created slice system-getty.slice.
> >> Starting Create list of required st…ce nodes for the current kernel...
> >> [ OK ] Created slice User and Session Slice.
> >> [ OK ] Reached target Slices.
> >> [ OK ] Listening on RPCbind Server Activation Socket.
> >> [ OK ] Reached target RPC Port Mapper.
> >> Mounting POSIX Message Queue File System...
> >> [ OK ] Stopped File System Check on Root Device.
> >> Starting Remount Root and Kernel File Systems...
> >> [ OK ] Started Forward Password Requests to Wall Directory Watch.
> >> [ OK ] Reached target Local Encrypted Volumes.
> >> [ 21.912238] Adding 4194240k swap on /dev/mapper/rhel_ltcden3--lp1-swap. Priority:-2 extents:1 across:4194240k FS
> >> [ OK ] Listening on Device-mapper event daemon FIFOs.
> >> Starting Monitoring of LVM2 mirrors…ng dmeventd or progress polling...
> >> Starting Setup Virtual Console...
> >> [ OK ] Stopped target Initrd Root File System.
> >> Mounting Kernel Debug File System...
> >> [ OK ] Listening on udev Control Socket.
> >> Starting udev Coldplug all Devices...
> >> [ OK ] Created slice system-sshd\x2dkeygen.slice.
> >> [ OK ] Stopped target Initrd File Systems.
> >> [ OK ] Listening on LVM2 poll daemon socket.
> >> [ OK ] Activated swap /dev/mapper/rhel_ltcden3--lp1-swap.
> >> [ OK ] Mounted Huge Pages File System.
> >> [ OK ] Started Read and set NIS domainname from /etc/sysconfig/network.
> >> [ OK ] Started Create list of required sta…vice nodes for the current kernel.
> >> [ OK ] Started Journal Service.
> >> [ OK ] Mounted POSIX Message Queue File System.
> >> [ OK ] Mounted Kernel Debug File System.
> >> [ OK ] Reached target Swap.
> >> [ 22.217261] xfs filesystem being remounted at / supports timestamps until 2038 (0x7fffffff)
> >> [ OK ] Started Remount Root and Kernel File Systems.
> >> [ OK ] Started Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
> >> Starting Create Static Device Nodes in /dev...
> >> Starting Load/Save Random Seed...
> >> Starting Flush Journal to Persistent Storage...
> >> [FAILED] Failed to start Load Kernel Modules.
> >> See 'systemctl status systemd-modules-load.service' for details.
> >> Starting Apply Kernel Variables...
> >> [ 22.341308] synth uevent: /devices/vio: failed to send uevent
> >> [ 22.341317] vio vio: uevent: failed to send synthetic uevent: -19
> >> [ 22.341597] synth uevent: /devices/vio/4000: failed to send uevent
> >> [ 22.341600] vio 4000: uevent: failed to send synthetic uevent: -19
> >> [ 22.341610] synth uevent: /devices/vio/4001: failed to send uevent
> >> [ 22.341613] vio 4001: uevent: failed to send synthetic uevent: -19
> >> [ 22.341622] synth uevent: /devices/vio/4002: failed to send uevent
> >> [ 22.341625] vio 4002: uevent: failed to send synthetic uevent: -19
> >> [ 22.341633] synth uevent: /devices/vio/4004: failed to send uevent
> >> [ 22.341636] vio 4004: uevent: failed to send synthetic uevent: -19
> >> [ OK ] Started udev Coldplug all Devices.
> >> Starting udev Wait for Complete Device Initialization...
> >> [ OK ] Started Load/Save Random Seed.
> >> [ OK ] Started Flush Journal to Persistent Storage.
> >> [ OK ] Started Setup Virtual Console.
> >> [ OK ] Started Apply Kernel Variables.
> >> [ OK ] Started Create Static Device Nodes in /dev.
> >> Starting udev Kernel Device Manager...
> >> [ OK ] Started udev Kernel Device Manager.
> >> [ 24.100485] pseries_rng: Registering IBM pSeries RNG driver
> >> [ OK ] Created slice system-lvm2\x2dpvscan.slice.
> >> Starting LVM event activation on device 8:19...
> >> [ OK ] Started LVM event activation on device 8:19.
> >> [ OK ] Started udev Wait for Complete Device Initialization.
> >> [ OK ] Reached target Local File Systems (Pre).
> >> Mounting /home...
> >> Mounting /home2...
> >> Mounting /boot...
> >> [ 25.049055] XFS (nvme0n1p1): Mounting V5 Filesystem 31458cd5-8eb4-48b4-8f5a-112217ef59df
> >> [ 25.049822] XFS (dm-1): Mounting V5 Filesystem 0ac3d742-375d-4cd7-bdd2-72b0559b1957
> >> [ 25.050953] XFS (sdb2): Mounting V5 Filesystem c72725b8-35e3-42b4-b5cb-f8435cada964
> >> [ 25.055813] XFS (nvme0n1p1): Ending clean mount
> >> [ 25.056844] xfs filesystem being mounted at /home supports timestamps until 2038 (0x7fffffff)
> >> [ OK ] Mounted /home.
> >> [ 25.389921] XFS (dm-1): Ending clean mount
> >> [ 25.513566] xfs filesystem being mounted at /home2 supports timestamps until 2038 (0x7fffffff)
> >> [ OK ] Mounted /home2.
> >> [ 26.797307] XFS (sdb2): Ending clean mount
> >> [ 26.857340] xfs filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
> >> [ OK ] Mounted /boot.
> >> [ OK ] Reached target Local File Systems.
> >> Starting Tell Plymouth To Write Out Runtime Data...
> >> Starting Restore /run/initramfs on shutdown...
> >> Starting Import network configuration from initramfs...
> >> [ OK ] Started Restore /run/initramfs on shutdown.
> >> [ OK ] Started Import network configuration from initramfs.
> >> Starting Create Volatile Files and Directories...
> >> [ OK ] Started Tell Plymouth To Write Out Runtime Data.
> >> [ OK ] Started Create Volatile Files and Directories.
> >> Mounting RPC Pipe File System...
> >> Starting Security Auditing Service...
> >> Starting RPC Bind...
> >> [ OK ] Started RPC Bind.
> >> [ 27.888702] RPC: Registered named UNIX socket transport module.
> >> [ 27.888714] RPC: Registered udp transport module.
> >> [ 27.888717] RPC: Registered tcp transport module.
> >> [ 27.888719] RPC: Registered tcp NFSv4.1 backchannel transport module.
> >> [ OK ] Mounted RPC Pipe File System.
> >> [ OK ] Reached target rpc_pipefs.target.
> >> [ OK ] Started Security Auditing Service.
> >> Starting Update UTMP about System Boot/Shutdown...
> >> [ OK ] Started Update UTMP about System Boot/Shutdown.
> >> [ OK ] Reached target System Initialization.
> >> [ OK ] Listening on Open-iSCSI iscsid Socket.
> >> [ OK ] Listening on CUPS Scheduler.
> >> [ OK ] Started Run system activity accounting tool every 10 minutes.
> >> [ OK ] Started CUPS Scheduler.
> >> [ OK ] Reached target Paths.
> >> [ OK ] Listening on SSSD Kerberos Cache Manager responder socket.
> >> [ OK ] Listening on D-Bus System Message Bus Socket.
> >> [ OK ] Started Generate summary of yesterday's process accounting.
> >> [ OK ] Started daily update of the root trust anchor for DNSSEC.
> >> [ OK ] Started Daily Cleanup of Temporary Directories.
> >> [ OK ] Started dnf makecache --timer.
> >> [ OK ] Reached target Timers.
> >> [ OK ] Listening on Open-iSCSI iscsiuio Socket.
> >> [ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
> >> [ OK ] Reached target Sockets.
> >> [ OK ] Reached target Basic System.
> >> Starting NTP client/server...
> >> Starting Hardware RNG Entropy Gatherer Wake threshold service...
> >> [ OK ] Started libstoragemgmt plug-in server daemon.
> >> [ OK ] Started irqbalance daemon.
> >> Starting Resets System Activity Logs...
> >> Starting ppc64-diag rtas_errd (platform error handling) Service...
> >> Starting Self Monitoring and Reporting Technology (SMART) Daemon...
> >> [ OK ] Reached target sshd-keygen.target.
> >> Starting ABRT Automated Bug Reporting Tool...
> >> Starting System Security Services Daemon...
> >> Starting Authorization Manager...
> >> [ OK ] Started D-Bus System Message Bus.
> >> Starting Avahi mDNS/DNS-SD Stack...
> >> [ OK ] Started Hardware RNG Entropy Gatherer Wake threshold service.
> >> [ OK ] Started Hardware RNG Entropy Gatherer Daemon.
> >> [ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
> >> [ OK ] Started Resets System Activity Logs.
> >> [ OK ] Started ppc64-diag rtas_errd (platform error handling) Service.
> >> [ OK ] Started Avahi mDNS/DNS-SD Stack.
> >> [ OK ] Started NTP client/server.
> >> [ OK ] Started System Security Services Daemon.
> >> [ OK ] Reached target User and Group Name Lookups.
> >> Starting Login Service...
> >> [ OK ] Started Login Service.
> >> [ OK ] Started Authorization Manager.
> >> Starting firewalld - dynamic firewall daemon...
> >> Starting Modem Manager...
> >> [ OK ] Started Modem Manager.
> >> [ OK ] Started firewalld - dynamic firewall daemon.
> >> [ OK ] Reached target Network (Pre).
> >> Starting Network Manager...
> >> [ OK ] Started Network Manager.
> >> Starting hybrid virtual network scan and config...
> >> Starting Network Manager Wait Online...
> >> [ OK ] Reached target Network.
> >> Starting Enable periodic update of entitlement certificates....
> >> Starting CUPS Scheduler...
> >> Starting GSSAPI Proxy Daemon...
> >> Starting OpenSSH server daemon...
> >> Starting Logout off all iSCSI sessions on shutdown...
> >> [ OK ] Started Logout off all iSCSI sessions on shutdown.
> >> [ OK ] Started Enable periodic update of entitlement certificates..
> >> Starting Hostname Service...
> >> [ OK ] Started ABRT Automated Bug Reporting Tool.
> >> [ OK ] Started ABRT kernel log watcher.
> >> [ OK ] Started ABRT Xorg log watcher.
> >> [ OK ] Started Creates ABRT problems from coredumpctl messages.
> >> [ OK ] Started Hostname Service.
> >> [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
> >> [FAILED] Failed to start hybrid virtual network scan and config.
> >> See 'systemctl status hcn-init.service' for details.
> >> [ OK ] Started OpenSSH server daemon.
> >> [ OK ] Started GSSAPI Proxy Daemon.
> >> [ OK ] Reached target NFS client services.
> >> Starting Network Manager Script Dispatcher Service...
> >> [ OK ] Started CUPS Scheduler.
> >> [ OK ] Started Network Manager Script Dispatcher Service.
> >> [ OK ] Started Network Manager Wait Online.
> >> [ OK ] Reached target Network is Online.
> >> Starting Notify NFS peers of a restart...
> >> [ OK ] Reached target Remote File Systems (Pre).
> >> [ OK ] Reached target Remote File Systems.
> >> Starting Harvest vmcores for ABRT...
> >> Starting Permit User Sessions...
> >> Starting System Logging Service...
> >> [ OK ] Started Notify NFS peers of a restart.
> >> [ OK ] Started Permit User Sessions.
> >> [ OK ] Started Job spooling tools.
> >> Starting Terminate Plymouth Boot Screen...
> >> [ OK ] Started Command Scheduler.
> >> Starting Hold until boot process finishes up...
> >> [ OK ] Started System Logging Service.
> >> [ 44.801795] ------------[ cut here ]------------
> >> [ 44.801810] WARNING: CPU: 24 PID: 1906 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
> >> [ 44.801895] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set rfkill nf_tables nfnetlink sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi nvme ibmveth scsi_transport_srp nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
> >> [ 44.801926] CPU: 24 PID: 1906 Comm: in:imjournal Not tainted 6.2.0-rc8ssh #35
> >> [ 44.801930] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> >> [ 44.801933] NIP: c00800000062fa80 LR: c00800000062fa4c CTR: c000000000ea4d40
> >> [ 44.801936] REGS: c00000001984b690 TRAP: 0700 Not tainted (6.2.0-rc8ssh)
> >> [ 44.801939] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24224842 XER: 00000000
> >> [ 44.801947] CFAR: c00800000062fa54 IRQMASK: 0
> >> [ 44.801947] GPR00: c0000000091cbec8 c00000001984b930 c0080000006d8300 0000000000000000
> >> [ 44.801947] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000051aa4d90
> >> [ 44.801947] GPR08: 0000000000000000 c000000051aa4e40 0000000000000000 fffffffffffffffd
> >> [ 44.801947] GPR12: 0000000000000040 c000004afece5880 0000000000000000 0000000004000000
> >> [ 44.801947] GPR16: c00000001984bb38 c00000001984ba38 c00000001984ba68 c00000002c323c00
> >> [ 44.801947] GPR20: c0000000091cbe00 0000000000008000 c0000000516e5800 00000000002ec44d
> >> [ 44.801947] GPR24: 000000000030af4d 000000000000000d c000000008d71680 00000000002ec44d
> >> [ 44.801947] GPR28: c00000002c322400 c0000000091cbe00 c000000054c05618 000000000030af4d
> >> [ 44.801983] NIP [c00800000062fa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
> >> [ 44.802037] LR [c00800000062fa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
> >> [ 44.802090] Call Trace:
> >> [ 44.802091] [c00000001984b930] [c000000054c05618] 0xc000000054c05618 (unreliable)
> >> [ 44.802096] [c00000001984b950] [c008000000630094] xfs_iunlink+0x1bc/0x280 [xfs]
> >> [ 44.802149] [c00000001984b9d0] [c008000000634754] xfs_rename+0x69c/0xd10 [xfs]
> >> [ 44.802202] [c00000001984bb10] [c00800000062e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
> >> [ 44.802255] [c00000001984bba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
> >> [ 44.802261] [c00000001984bc90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
> >> [ 44.802265] [c00000001984bde0] [c000000000580520] sys_rename+0x60/0x80
> >> [ 44.802269] [c00000001984be10] [c000000000033630] system_call_exception+0x150/0x3b0
> >> [ 44.802274] [c00000001984be50] [c00000000000c554] system_call_common+0xf4/0x258
> >> [ 44.802280] --- interrupt: c00 at 0x7fffa6482e20
> >> [ 44.802282] NIP: 00007fffa6482e20 LR: 00007fffa6055e24 CTR: 0000000000000000
> >> [ 44.802285] REGS: c00000001984be80 TRAP: 0c00 Not tainted (6.2.0-rc8ssh)
> >> [ 44.802288] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
> >> [ 44.802297] IRQMASK: 0
> >> [ 44.802297] GPR00: 0000000000000026 00007fffa536d220 00007fffa6607300 00007fffa536d288
> >> [ 44.802297] GPR04: 000000014f7a6b70 0000000000000000 0700000000000000 0000000000000002
> >> [ 44.802297] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> >> [ 44.802297] GPR12: 0000000000000000 00007fffa53766e0 000000014f795930 0000000000000000
> >> [ 44.802297] GPR16: 0000000126b67648 00007fffa6057ce0 0000000000000003 000000000000002b
> >> [ 44.802297] GPR20: 0000000000000212 00007fffa536e3a0 00007fffa536e398 00007fff98008690
> >> [ 44.802297] GPR24: 0000000000000000 00007fffa536e388 00007fffa536e378 00007fffa536e3b0
> >> [ 44.802297] GPR28: 00007fffa6070000 00007fffa60705e0 00007fff98000c10 00007fffa536d288
> >> [ 44.802331] NIP [00007fffa6482e20] 0x7fffa6482e20
> >> [ 44.802334] LR [00007fffa6055e24] 0x7fffa6055e24
> >> [ 44.802336] --- interrupt: c00
> >> [ 44.802338] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
> >> [ 44.802352] ---[ end trace 0000000000000000 ]---
> >> [ 44.802356] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x9cc/0xd10 [xfs]
> >> [ 44.802412] CPU: 24 PID: 1906 Comm: in:imjournal Tainted: G W 6.2.0-rc8ssh #35
> >> [ 44.802415] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> >> [ 44.802418] Call Trace:
> >> [ 44.802420] [c00000001984b8f0] [c000000000e87328] dump_stack_lvl+0x6c/0x9c (unreliable)
> >> [ 44.802425] [c00000001984b920] [c008000000616a84] xfs_error_report+0x5c/0x80 [xfs]
> >> [ 44.802478] [c00000001984b980] [c0080000006467b0] xfs_trans_cancel+0x178/0x1b0 [xfs]
> >> [ 44.802533] [c00000001984b9d0] [c008000000634a84] xfs_rename+0x9cc/0xd10 [xfs]
> >> [ 44.802586] [c00000001984bb10] [c00800000062e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
> >> [ 44.802641] [c00000001984bba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
> >> [ 44.802644] [c00000001984bc90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
> >> [ 44.802648] [c00000001984bde0] [c000000000580520] sys_rename+0x60/0x80
> >> [ 44.802652] [c00000001984be10] [c000000000033630] system_call_exception+0x150/0x3b0
> >> [ 44.802657] [c00000001984be50] [c00000000000c554] system_call_common+0xf4/0x258
> >> [ 44.802661] --- interrupt: c00 at 0x7fffa6482e20
> >> [ 44.802664] NIP: 00007fffa6482e20 LR: 00007fffa6055e24 CTR: 0000000000000000
> >> [ 44.802667] REGS: c00000001984be80 TRAP: 0c00 Tainted: G W (6.2.0-rc8ssh)
> >> [ 44.802670] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
> >> [ 44.802678] IRQMASK: 0
> >> [ 44.802678] GPR00: 0000000000000026 00007fffa536d220 00007fffa6607300 00007fffa536d288
> >> [ 44.802678] GPR04: 000000014f7a6b70 0000000000000000 0700000000000000 0000000000000002
> >> [ 44.802678] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> >> [ 44.802678] GPR12: 0000000000000000 00007fffa53766e0 000000014f795930 0000000000000000
> >> [ 44.802678] GPR16: 0000000126b67648 00007fffa6057ce0 0000000000000003 000000000000002b
> >> [ 44.802678] GPR20: 0000000000000212 00007fffa536e3a0 00007fffa536e398 00007fff98008690
> >> [ 44.802678] GPR24: 0000000000000000 00007fffa536e388 00007fffa536e378 00007fffa536e3b0
> >> [ 44.802678] GPR28: 00007fffa6070000 00007fffa60705e0 00007fff98000c10 00007fffa536d288
> >> [ 44.802712] NIP [00007fffa6482e20] 0x7fffa6482e20
> >> [ 44.802715] LR [00007fffa6055e24] 0x7fffa6055e24
> >> [ 44.802717] --- interrupt: c00
> >> [ 44.804354] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
> >> [ 44.804413] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
> >>
> >>
> >>
> >> >> [ 333.390615] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc pseries_rng xts vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
> >> >> [ 333.390645] CPU: 56 PID: 12450 Comm: rm Not tainted 6.2.0-rc4ssh+ #4
> >> >> [ 333.390649] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> >> >> [ 333.390652] NIP: c0080000004bfa80 LR: c0080000004bfa4c CTR: c000000000ea28d0
> >> >> [ 333.390655] REGS: c0000000442bb8c0 TRAP: 0700 Not tainted (6.2.0-rc4ssh+)
> >> >> [ 333.390658] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24002842 XER: 00000000
> >> >> [ 333.390666] CFAR: c0080000004bfa54 IRQMASK: 0
> >> >> [ 333.390666] GPR00: c00000003b69c0c8 c0000000442bbb60 c008000000568300 0000000000000000
> >> >> [ 333.390666] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c000000004b27d78
> >> >> [ 333.390666] GPR08: 0000000000000000 c000000004b27e28 0000000000000000 fffffffffffffffd
> >> >> [ 333.390666] GPR12: 0000000000000040 c000004afecc5880 0000000106620918 0000000000000001
> >> >> [ 333.390666] GPR16: 000000010bd36e10 0000000106620dc8 0000000106620e58 0000000106620e90
> >> >> [ 333.390666] GPR20: 0000000106620e30 c0000000880ba938 0000000000200000 00000000002ec44d
> >> >> [ 333.390666] GPR24: 000000000008170d 000000000000000d c0000000519f4800 00000000002ec44d
> >> >> [ 333.390666] GPR28: c0000000880ba800 c00000003b69c000 c0000000833edd20 000000000008170d
> >> >> [ 333.390702] NIP [c0080000004bfa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
> >> >> [ 333.390756] LR [c0080000004bfa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
> >> >> [ 333.390810] Call Trace:
> >> >> [ 333.390811] [c0000000442bbb60] [c0000000833edd20] 0xc0000000833edd20 (unreliable)
> >> >> [ 333.390816] [c0000000442bbb80] [c0080000004c0094] xfs_iunlink+0x1bc/0x280 [xfs]
> >> >> [ 333.390869] [c0000000442bbc00] [c0080000004c3f84] xfs_remove+0x1dc/0x310 [xfs]
> >> >> [ 333.390922] [c0000000442bbc70] [c0080000004be180] xfs_vn_unlink+0x68/0xf0 [xfs]
> >> >> [ 333.390975] [c0000000442bbcd0] [c000000000576b24] vfs_unlink+0x1b4/0x3d0
> >> >
> >> > ...that trips when rm tries to remove a file, which means that the call
> >> > stack is
> >> >
> >> > xfs_remove -> xfs_iunlink -> xfs_iunlink_insert_inode ->
> >> > xfs_iunlink_update_backref -> xfs_iunlink_lookup <kaboom>
> >> >
> >> > It looks as though "rm foo" unlinked foo from the directory and was
> >> > trying to insert it at the head of one of the unlinked lists in the AGI
> >> > buffer. The AGI claims that the list points to an ondisk inode, so the
> >> > iunlink code tries to find the incore inode to update the incore list,
> >> > fails to find an incore inode, and this is the result...
> >>
> >> This seems to happen for rename as well. i.e xfs_rename.
> >> Does rename path calls rm first, and then create?
> >
> > Effectively, yes. A "mv a b" will unlink b, and that calls the same
> > internal unlink code as an unlink syscall.
> >
> >> >>
> >> >>
> >> >> we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821
> >> >> as the bad commit.
> >> >> Short description of commit:
> >> >> commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad)
> >> >> Author: Dave Chinner <dchinner@redhat.com>
> >> >> Date: Thu Jul 14 11:42:39 2022 +1000
> >> >>
> >> >> xfs: refactor xlog_recover_process_iunlinks()
> >> >
> >> > ...which was in the middle of the series that reworked thev mount time
> >> > iunlink clearing. Oddly, I don't spot any obvious errors in /that/
> >> > patch that didn't already exist. But this does make me wonder, does
> >> > xfs_repair -n have anything to say about unlinked or orphaned inodes?
> >> >
> >> > The runtime code expects that every ondisk inode in an iunlink chain has
> >> > an incore inode that is linked (via i_{next,prev}_unlinked) to the other
> >> > incore inodes in that same chain. If this requirement is not met, then
> >> > the WARNings you see will trip, and the fs shuts down.
> >> >
> >> > My hypothesis here is that one of the AGs has an unprocessed unlinked
> >> > list. At mount time, the ondisk log was clean, so mount time log
> >> > recovery didn't invoke xlog_recover_process_iunlinks, and the list was
> >> > not cleared. The mount code does not construct the incore unlinked list
> >> > from an existing ondisk iunlink list, hence the WARNing. Prior to 5.17,
> >> > we only manipulated the ondisk unlink list, and the code never noticed
> >> > or cared if there were mystery inodes in the list that never went away.
> >> >
> >> > (Obviously, if something blew up earlier in dmesg, that would be
> >> > relevant here.)
> >> >
> >> > It's possible that we could end up in this situation (clean log,
> >> > unlinked inodes) if a previous log recovery was only partially
> >> > successful at clearing the unlinked list, since all that code ignores
> >> > errors. If that happens, we ... succeed at mounting and clean the log.
> >> >
> >> > If you're willing to patch your kernels, it would be interesting
> >> > to printk if the xfs_read_agi or the xlog_recover_iunlink_bucket calls
> >> > in xlog_recover_iunlink_ag returns an error code. It might be too late
> >>
> >> We can try. Please provide the Patch.
> >>
> >> > to capture that, hence my suggestion of seeing if xfs_repair -n will
> >> > tell us anything else.
> >> >
> >>
> >> Could you please clarify? We should run xfs_repair -n from 5.17-rc2 kernel?
> >
> > Whatever xfs_repair is installed on the system should suffice to report
> > an unlinked inode list and any other errors on the filesystem.
> >
>
> Hi Darrick,
>
> Please find the information collected from the system. We added some
> debug logs and looks like it is exactly what is happening which you
> pointed out.
>
> We added a debug kernel patch to get more info from the system which
> you had requested [1]
>
> 1. We first breaked into emergency shell where root fs is first getting
> mounted on /sysroot as "ro" filesystem. Here are the logs.
>
> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
> Mounting /sysroot...
> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
>
> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
> the huge value.
Ok, so log recovery finds 3064909 and clears it...
> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
<snip the rest of these...>
> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
> [ OK ] Mounted /sysroot.
> [ OK ] Reached target Initrd Root File System.
>
>
> 2. Then these are the logs from xfs_repair -n /dev/dm-0
> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
> printed in above xlog_recover_iunlink_ag() function.
>
> switch_root:/# xfs_repair -n /dev/dm-0
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
> - zero log...
> - scan filesystem freespace and inode maps...
> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
...yet here we find that 3064909 is still on the unlinked list?
Just to confirm -- you ran xfs_repair -n after the successful recovery
above, right?
> - found root inode chunk
> Phase 3 - for each AG...
> - scan (but don't clear) agi unlinked lists...
> - process known inodes and perform inode discovery...
> - agno = 0
> - agno = 1
> - agno = 2
> - agno = 3
> - process newly discovered inodes...
> Phase 4 - check for duplicate blocks...
> - setting up duplicate extent list...
> - check for inodes claiming duplicate blocks...
> - agno = 0
> - agno = 2
> - agno = 1
> - agno = 3
> No modify flag set, skipping phase 5
> Phase 6 - check inode connectivity...
> - traversing filesystem ...
> - traversal finished ...
> - moving disconnected inodes to lost+found ...
> Phase 7 - verify link counts...
> would have reset inode 3064909 nlinks from 4294967291 to 2
Oh now that's interesting. Inode on unlinked list with grossly nonzero
(but probably underflowed) link count. That might explain why iunlink
recovery ignores the inode. Is inode 3064909 reachable via the
directory tree?
Would you mind sending me a metadump to play with? metadump -ago would
be best, if filenames/xattrnames aren't sensitive customer data.
> No modify flag set, skipping filesystem flush and exiting.
>
>
> 3. Then we exit from the shell for the system to continue booting.
> Here it will continue.. Just pasting the logs where the warning gets
> generated and some extra logs are getting printed for the same inode
> with our patch.
>
>
> it continues
> ================
> [ 587.999113] ------------[ cut here ]------------
> [ 587.999121] WARNING: CPU: 48 PID: 2026 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
> [ 587.999185] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc xts pseries_rng vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
> [ 587.999215] CPU: 48 PID: 2026 Comm: in:imjournal Not tainted 6.2.0-rc8ssh+ #38
> [ 587.999219] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> [ 587.999222] NIP: c00800000065fa80 LR: c00800000065fa4c CTR: c000000000ea4d40
> [ 587.999226] REGS: c00000001aa83650 TRAP: 0700 Not tainted (6.2.0-rc8ssh+)
> [ 587.999228] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24224842 XER: 00000000
> [ 587.999236] CFAR: c00800000065fa54 IRQMASK: 0
> [ 587.999236] GPR00: c00000004570b2c8 c00000001aa838f0 c008000000708300 0000000000000000
> [ 587.999236] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c00000000413faf0
> [ 587.999236] GPR08: 0000000000000000 c00000000413fba0 0000000000000000 fffffffffffffffd
> [ 587.999236] GPR12: 0000000000000040 c000004afeccd880 0000000000000000 0000000004000000
> [ 587.999236] GPR16: c00000001aa83b38 c00000001aa83a38 c00000001aa83a68 c000000035264c00
> [ 587.999236] GPR20: c00000004570b200 0000000000008000 c00000000886c400 00000000002ec44d
> [ 587.999236] GPR24: 000000000014040d 000000000000000d c000000051875400 00000000002ec44d
> [ 587.999236] GPR28: c000000035262c00 c00000004570b200 c00000008f2d8b90 000000000014040d
> [ 587.999272] NIP [c00800000065fa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
> [ 587.999327] LR [c00800000065fa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
> [ 587.999379] Call Trace:
> [ 587.999381] [c00000001aa838f0] [c00000008f2d8b90] 0xc00000008f2d8b90 (unreliable)
> [ 587.999385] [c00000001aa83910] [c008000000660094] xfs_iunlink+0x1bc/0x2c0 [xfs]
> [ 587.999438] [c00000001aa839d0] [c008000000664804] xfs_rename+0x69c/0xd10 [xfs]
> [ 587.999491] [c00000001aa83b10] [c00800000065e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
> [ 587.999544] [c00000001aa83ba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
> [ 587.999549] [c00000001aa83c90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
> [ 587.999553] [c00000001aa83de0] [c000000000580520] sys_rename+0x60/0x80
> [ 587.999557] [c00000001aa83e10] [c000000000033630] system_call_exception+0x150/0x3b0
> [ 587.999562] [c00000001aa83e50] [c00000000000c554] system_call_common+0xf4/0x258
> [ 587.999567] --- interrupt: c00 at 0x7fff96082e20
> [ 587.999569] NIP: 00007fff96082e20 LR: 00007fff95c45e24 CTR: 0000000000000000
> [ 587.999572] REGS: c00000001aa83e80 TRAP: 0c00 Not tainted (6.2.0-rc8ssh+)
> [ 587.999575] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
> [ 587.999584] IRQMASK: 0
> [ 587.999584] GPR00: 0000000000000026 00007fff94f5d220 00007fff96207300 00007fff94f5d288
> [ 587.999584] GPR04: 0000000172b76b70 0000000000000000 0600000000000000 0000000000000002
> [ 587.999584] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> [ 587.999584] GPR12: 0000000000000000 00007fff94f666e0 0000000172b65930 0000000000000000
> [ 587.999584] GPR16: 0000000132fe7648 00007fff95c47ce0 0000000000000000 000000000000004c
> [ 587.999584] GPR20: 0000000000000082 00007fff94f5e3a0 00007fff94f5e398 00007fff880029b0
> [ 587.999584] GPR24: 0000000000000000 00007fff94f5e388 00007fff94f5e378 00007fff94f5e3b0
> [ 587.999584] GPR28: 00007fff95c60000 00007fff95c605e0 00007fff88000c10 00007fff94f5d288
> [ 587.999618] NIP [00007fff96082e20] 0x7fff96082e20
> [ 587.999620] LR [00007fff95c45e24] 0x7fff95c45e24
> [ 587.999622] --- interrupt: c00
> [ 587.999624] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
> [ 587.999637] ---[ end trace 0000000000000000 ]---
> [ 587.999640] xfs_iunlink_update_backref: next_agino: 3064909 cannot be found
> [ 587.999643] xfs_iunlink_insert_inode: Cannot find backref for agino:1311757, ip->i_ino:1311757, next_agino: 3064909 agno:0
> [ 587.999646] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x9cc/0xd10 [xfs]
>
> ^^^ There are the extra info printing the next_agino to be the same
> agino 3064909 for xfs_iunlink_lookup has failed.
Yep, then runtime code encounters agi[0].unlinked[13] == 3064909, but
doesn't find an xfs_inode in the cache for it, and shuts down the
filesystem.
--D
>
> [ 587.999701] CPU: 48 PID: 2026 Comm: in:imjournal Tainted: G W 6.2.0-rc8ssh+ #38
> [ 587.999705] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> [ 587.999708] Call Trace:
> [ 587.999709] [c00000001aa838f0] [c000000000e87328] dump_stack_lvl+0x6c/0x9c (unreliable)
> [ 587.999715] [c00000001aa83920] [c008000000646a84] xfs_error_report+0x5c/0x80 [xfs]
> [ 587.999767] [c00000001aa83980] [c008000000676860] xfs_trans_cancel+0x178/0x1b0 [xfs]
> [ 587.999823] [c00000001aa839d0] [c008000000664b34] xfs_rename+0x9cc/0xd10 [xfs]
> [ 587.999876] [c00000001aa83b10] [c00800000065e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
> [ 587.999929] [c00000001aa83ba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
> [ 587.999933] [c00000001aa83c90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
> [ 587.999937] [c00000001aa83de0] [c000000000580520] sys_rename+0x60/0x80
> [ 587.999941] [c00000001aa83e10] [c000000000033630] system_call_exception+0x150/0x3b0
> [ 587.999945] [c00000001aa83e50] [c00000000000c554] system_call_common+0xf4/0x258
> [ 587.999950] --- interrupt: c00 at 0x7fff96082e20
> [ 587.999952] NIP: 00007fff96082e20 LR: 00007fff95c45e24 CTR: 0000000000000000
> [ 587.999955] REGS: c00000001aa83e80 TRAP: 0c00 Tainted: G W (6.2.0-rc8ssh+)
> [ 587.999958] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
> [ 587.999967] IRQMASK: 0
> [ 587.999967] GPR00: 0000000000000026 00007fff94f5d220 00007fff96207300 00007fff94f5d288
> [ 587.999967] GPR04: 0000000172b76b70 0000000000000000 0600000000000000 0000000000000002
> [ 587.999967] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> [ 587.999967] GPR12: 0000000000000000 00007fff94f666e0 0000000172b65930 0000000000000000
> [ 587.999967] GPR16: 0000000132fe7648 00007fff95c47ce0 0000000000000000 000000000000004c
> [ 587.999967] GPR20: 0000000000000082 00007fff94f5e3a0 00007fff94f5e398 00007fff880029b0
> [ 587.999967] GPR24: 0000000000000000 00007fff94f5e388 00007fff94f5e378 00007fff94f5e3b0
> [ 587.999967] GPR28: 00007fff95c60000 00007fff95c605e0 00007fff88000c10 00007fff94f5d288
> [ 588.000000] NIP [00007fff96082e20] 0x7fff96082e20
> [ 588.000002] LR [00007fff95c45e24] 0x7fff95c45e24
> [ 588.000004] --- interrupt: c00
> [ 588.012398] Core dump to |/usr/lib/systemd/systemd-coredump pipe failed
> [ 588.020328] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
> [ 588.020388] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
>
>
> 4. Here is the patch diff which we used to collect the info.
>
> <patch>
> =============
>
> root-> git diff
> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> index 5808abab786c..86b8cab7f759 100644
> --- a/fs/xfs/xfs_inode.c
> +++ b/fs/xfs/xfs_inode.c
> @@ -1859,8 +1859,10 @@ xfs_iunlink_update_backref(
> return 0;
>
> ip = xfs_iunlink_lookup(pag, next_agino);
> - if (!ip)
> + if (!ip) {
> + pr_err("%s: next_agino: %u cannot be found\n", __func__, next_agino);
> return -EFSCORRUPTED;
> + }
> ip->i_prev_unlinked = prev_agino;
> return 0;
> }
> @@ -1935,8 +1937,11 @@ xfs_iunlink_insert_inode(
> * inode.
> */
> error = xfs_iunlink_update_backref(pag, agino, next_agino);
> - if (error)
> + if (error) {
> + pr_crit("%s: Cannot find backref for agino:%u, ip->i_ino:%llu, next_agino: %u agno:%u\n",
> + __func__, agino, ip->i_ino, next_agino, pag->pag_agno);
> return error;
> + }
>
> if (next_agino != NULLAGINO) {
> /*
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index fc61cc024023..035fc1eba871 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -825,6 +825,10 @@ xfs_log_mount_finish(
> */
> mp->m_super->s_flags |= SB_ACTIVE;
> xfs_log_work_queue(mp);
> + if (xlog_recovery_needed(log))
> + pr_crit("%s: Recovery needed is set\n", __func__);
> + else
> + pr_crit("%s: Recovery needed not set\n", __func__);
> if (xlog_recovery_needed(log))
> error = xlog_recover_finish(log);
> mp->m_super->s_flags &= ~SB_ACTIVE;
> diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
> index 322eb2ee6c55..6caa8147b443 100644
> --- a/fs/xfs/xfs_log_recover.c
> +++ b/fs/xfs/xfs_log_recover.c
> @@ -2696,8 +2696,13 @@ xlog_recover_iunlink_bucket(
> ASSERT(VFS_I(ip)->i_nlink == 0);
> ASSERT(VFS_I(ip)->i_mode != 0);
> xfs_iflags_clear(ip, XFS_IRECOVERY);
> - agino = ip->i_next_unlinked;
>
> + if (bucket == 13) {
> + pr_crit("%s: bucket: %d, agino: %u, ino: %llu, iget ret: %d, previno:%llu, prev_agino:%u\n",
> + __func__, bucket, agino, ip->i_ino, error, prev_ip ? prev_ip->i_ino : -1, prev_ip ? XFS_INO_TO_AGINO(mp, prev_ip->i_ino) : -1);
> + }
> +
> + agino = ip->i_next_unlinked;
> if (prev_ip) {
> ip->i_prev_unlinked = prev_agino;
> xfs_irele(prev_ip);
> @@ -2789,8 +2794,11 @@ xlog_recover_iunlink_ag(
> * bucket and remaining inodes on it unreferenced and
> * unfreeable.
> */
> + pr_crit("%s: Failed in xlog_recover_iunlink_bucket %d\n", __func__, error);
> xfs_inodegc_flush(pag->pag_mount);
> xlog_recover_clear_agi_bucket(pag, bucket);
> + } else {
> + pr_crit("%s: ran xlog_recover_iunlink_bucket for agi:%u, bucket:%d\n", __func__, pag->pag_agno, bucket);
> }
> }
>
>
> > That evidence will guide us towards a kernel patch.
>
> I can spend some more time to debug and understand on how to fix this.
> But thought of sharing this info meanwhile and see if there are any
> pointers on how to fix this in kernel.
>
> Let me know if any other info is needed. We haven't yet run xfs_repair
> on the device w/o -n option.
>
> -ritesh
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-03-09 14:26 ` Ritesh Harjani
2023-03-09 17:27 ` Darrick J. Wong
@ 2023-03-10 0:29 ` Dave Chinner
2023-03-16 4:48 ` Ritesh Harjani
1 sibling, 1 reply; 28+ messages in thread
From: Dave Chinner @ 2023-03-10 0:29 UTC (permalink / raw)
To: Ritesh Harjani
Cc: Darrick J. Wong, shrikanth hegde, dchinner, linux-xfs,
Srikar Dronamraju, ojaswin
On Thu, Mar 09, 2023 at 07:56:06PM +0530, Ritesh Harjani wrote:
> Hi Darrick,
>
> Please find the information collected from the system. We added some
> debug logs and looks like it is exactly what is happening which you
> pointed out.
>
> We added a debug kernel patch to get more info from the system which
> you had requested [1]
>
> 1. We first breaked into emergency shell where root fs is first getting
> mounted on /sysroot as "ro" filesystem. Here are the logs.
>
> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
> Mounting /sysroot...
> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
>
> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
> the huge value.
That's NULLFSINO and NULLAGINO respectively. That's the indication
that this is the last inode on the chain and that the recovery loop
should terminate at this inode.
Nothing looks wrong to me there.
> 2. Then these are the logs from xfs_repair -n /dev/dm-0
> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
> printed in above xlog_recover_iunlink_ag() function.
>
> switch_root:/# xfs_repair -n /dev/dm-0
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
> - zero log...
> - scan filesystem freespace and inode maps...
> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
> - found root inode chunk
> Phase 3 - for each AG...
> - scan (but don't clear) agi unlinked lists...
> - process known inodes and perform inode discovery...
> - agno = 0
> - agno = 1
> - agno = 2
> - agno = 3
> - process newly discovered inodes...
> Phase 4 - check for duplicate blocks...
> - setting up duplicate extent list...
> - check for inodes claiming duplicate blocks...
> - agno = 0
> - agno = 2
> - agno = 1
> - agno = 3
> No modify flag set, skipping phase 5
> Phase 6 - check inode connectivity...
> - traversing filesystem ...
> - traversal finished ...
> - moving disconnected inodes to lost+found ...
> Phase 7 - verify link counts...
> would have reset inode 3064909 nlinks from 4294967291 to 2
And there's the problem. The link count, as an signed int, is -5.
It got reset to 2 probably because it was moved to lost+found due to
having a non-zero link count. Not sure how it got to -5 and I
suspect we'll never really know. However, I think that's irrelevant
because if we fix the problem with unlink recovery failing to
register an unlink recovery error from inodegc we'll intentionally
leak the inode and it won't ever be a problem again.
> No modify flag set, skipping filesystem flush and exiting.
>
>
> 3. Then we exit from the shell for the system to continue booting.
> Here it will continue.. Just pasting the logs where the warning gets
> generated and some extra logs are getting printed for the same inode
> with our patch.
>
>
> it continues
> ================
> [ 587.999113] ------------[ cut here ]------------
> [ 587.999121] WARNING: CPU: 48 PID: 2026 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
Yeah, that happens because we failed to recover the unlinked inode,
we don't feed errors that occur in inodegc back to the unlink
recovery code, so it didn't clear the AGI bucket when we failed to
remove the inode from the unlinked list in inodegc. Hence it goes to
add the new inode to the start of unlinked list, and doesn't find the
broken, unrecovered inode that the bucket points to in cache.
IOWs, we fix the problem with feeding back errors from inodegc to
iunlink recovery, and this specific issue will go away.
> I can spend some more time to debug and understand on how to fix this.
> But thought of sharing this info meanwhile and see if there are any
> pointers on how to fix this in kernel.
I suspect that we need to do something like gather an error in
xfs_inodegc_flush() like we do for gathering the error in
xfs_btree_split() from the offloaded xfs_btree_split_worker()...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-03-09 17:27 ` Darrick J. Wong
@ 2023-03-16 4:46 ` Ritesh Harjani
2023-03-16 5:20 ` Darrick J. Wong
0 siblings, 1 reply; 28+ messages in thread
From: Ritesh Harjani @ 2023-03-16 4:46 UTC (permalink / raw)
To: Darrick J. Wong
Cc: shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
"Darrick J. Wong" <djwong@kernel.org> writes:
Hi Darrick,
Thanks for your analysis and quick help on this.
>>
>> Hi Darrick,
>>
>> Please find the information collected from the system. We added some
>> debug logs and looks like it is exactly what is happening which you
>> pointed out.
>>
>> We added a debug kernel patch to get more info from the system which
>> you had requested [1]
>>
>> 1. We first breaked into emergency shell where root fs is first getting
>> mounted on /sysroot as "ro" filesystem. Here are the logs.
>>
>> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
>> Mounting /sysroot...
>> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
>> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
>> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
>> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
>> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
>> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
>> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
>> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
>> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
>> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
>> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
>> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
>> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
>> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
>> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
>> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
>> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
>> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
>>
>> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
>> the huge value.
>
> Ok, so log recovery finds 3064909 and clears it...
>
>> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
>> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
>
> <snip the rest of these...>
>
>> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
>> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
>> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
>> [ OK ] Mounted /sysroot.
>> [ OK ] Reached target Initrd Root File System.
>>
>>
>> 2. Then these are the logs from xfs_repair -n /dev/dm-0
>> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
>> printed in above xlog_recover_iunlink_ag() function.
>>
>> switch_root:/# xfs_repair -n /dev/dm-0
>> Phase 1 - find and verify superblock...
>> Phase 2 - using internal log
>> - zero log...
>> - scan filesystem freespace and inode maps...
>> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
>
> ...yet here we find that 3064909 is still on the unlinked list?
>
> Just to confirm -- you ran xfs_repair -n after the successful recovery
> above, right?
>
Yes, that's right.
>> - found root inode chunk
>> Phase 3 - for each AG...
>> - scan (but don't clear) agi unlinked lists...
>> - process known inodes and perform inode discovery...
>> - agno = 0
>> - agno = 1
>> - agno = 2
>> - agno = 3
>> - process newly discovered inodes...
>> Phase 4 - check for duplicate blocks...
>> - setting up duplicate extent list...
>> - check for inodes claiming duplicate blocks...
>> - agno = 0
>> - agno = 2
>> - agno = 1
>> - agno = 3
>> No modify flag set, skipping phase 5
>> Phase 6 - check inode connectivity...
>> - traversing filesystem ...
>> - traversal finished ...
>> - moving disconnected inodes to lost+found ...
>> Phase 7 - verify link counts...
>> would have reset inode 3064909 nlinks from 4294967291 to 2
>
> Oh now that's interesting. Inode on unlinked list with grossly nonzero
> (but probably underflowed) link count. That might explain why iunlink
> recovery ignores the inode. Is inode 3064909 reachable via the
> directory tree?
>
> Would you mind sending me a metadump to play with? metadump -ago would
> be best, if filenames/xattrnames aren't sensitive customer data.
Sorry about the delay.
I am checking for any permissions part internally.
Meanwhile - I can help out if you would like me to try anything.
>> No modify flag set, skipping filesystem flush and exiting.
>>
>>
>> 3. Then we exit from the shell for the system to continue booting.
>> Here it will continue.. Just pasting the logs where the warning gets
>> generated and some extra logs are getting printed for the same inode
>> with our patch.
>>
>>
>> it continues
>> ================
>> [ 587.999113] ------------[ cut here ]------------
>> [ 587.999121] WARNING: CPU: 48 PID: 2026 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
>> [ 587.999185] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc xts pseries_rng vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
>> [ 587.999215] CPU: 48 PID: 2026 Comm: in:imjournal Not tainted 6.2.0-rc8ssh+ #38
>> [ 587.999219] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
>> [ 587.999222] NIP: c00800000065fa80 LR: c00800000065fa4c CTR: c000000000ea4d40
>> [ 587.999226] REGS: c00000001aa83650 TRAP: 0700 Not tainted (6.2.0-rc8ssh+)
>> [ 587.999228] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24224842 XER: 00000000
>> [ 587.999236] CFAR: c00800000065fa54 IRQMASK: 0
>> [ 587.999236] GPR00: c00000004570b2c8 c00000001aa838f0 c008000000708300 0000000000000000
>> [ 587.999236] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c00000000413faf0
>> [ 587.999236] GPR08: 0000000000000000 c00000000413fba0 0000000000000000 fffffffffffffffd
>> [ 587.999236] GPR12: 0000000000000040 c000004afeccd880 0000000000000000 0000000004000000
>> [ 587.999236] GPR16: c00000001aa83b38 c00000001aa83a38 c00000001aa83a68 c000000035264c00
>> [ 587.999236] GPR20: c00000004570b200 0000000000008000 c00000000886c400 00000000002ec44d
>> [ 587.999236] GPR24: 000000000014040d 000000000000000d c000000051875400 00000000002ec44d
>> [ 587.999236] GPR28: c000000035262c00 c00000004570b200 c00000008f2d8b90 000000000014040d
>> [ 587.999272] NIP [c00800000065fa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
>> [ 587.999327] LR [c00800000065fa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
>> [ 587.999379] Call Trace:
>> [ 587.999381] [c00000001aa838f0] [c00000008f2d8b90] 0xc00000008f2d8b90 (unreliable)
>> [ 587.999385] [c00000001aa83910] [c008000000660094] xfs_iunlink+0x1bc/0x2c0 [xfs]
>> [ 587.999438] [c00000001aa839d0] [c008000000664804] xfs_rename+0x69c/0xd10 [xfs]
>> [ 587.999491] [c00000001aa83b10] [c00800000065e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
>> [ 587.999544] [c00000001aa83ba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
>> [ 587.999549] [c00000001aa83c90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
>> [ 587.999553] [c00000001aa83de0] [c000000000580520] sys_rename+0x60/0x80
>> [ 587.999557] [c00000001aa83e10] [c000000000033630] system_call_exception+0x150/0x3b0
>> [ 587.999562] [c00000001aa83e50] [c00000000000c554] system_call_common+0xf4/0x258
>> [ 587.999567] --- interrupt: c00 at 0x7fff96082e20
>> [ 587.999569] NIP: 00007fff96082e20 LR: 00007fff95c45e24 CTR: 0000000000000000
>> [ 587.999572] REGS: c00000001aa83e80 TRAP: 0c00 Not tainted (6.2.0-rc8ssh+)
>> [ 587.999575] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
>> [ 587.999584] IRQMASK: 0
>> [ 587.999584] GPR00: 0000000000000026 00007fff94f5d220 00007fff96207300 00007fff94f5d288
>> [ 587.999584] GPR04: 0000000172b76b70 0000000000000000 0600000000000000 0000000000000002
>> [ 587.999584] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> [ 587.999584] GPR12: 0000000000000000 00007fff94f666e0 0000000172b65930 0000000000000000
>> [ 587.999584] GPR16: 0000000132fe7648 00007fff95c47ce0 0000000000000000 000000000000004c
>> [ 587.999584] GPR20: 0000000000000082 00007fff94f5e3a0 00007fff94f5e398 00007fff880029b0
>> [ 587.999584] GPR24: 0000000000000000 00007fff94f5e388 00007fff94f5e378 00007fff94f5e3b0
>> [ 587.999584] GPR28: 00007fff95c60000 00007fff95c605e0 00007fff88000c10 00007fff94f5d288
>> [ 587.999618] NIP [00007fff96082e20] 0x7fff96082e20
>> [ 587.999620] LR [00007fff95c45e24] 0x7fff95c45e24
>> [ 587.999622] --- interrupt: c00
>> [ 587.999624] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
>> [ 587.999637] ---[ end trace 0000000000000000 ]---
>> [ 587.999640] xfs_iunlink_update_backref: next_agino: 3064909 cannot be found
>> [ 587.999643] xfs_iunlink_insert_inode: Cannot find backref for agino:1311757, ip->i_ino:1311757, next_agino: 3064909 agno:0
>> [ 587.999646] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x9cc/0xd10 [xfs]
>>
>> ^^^ There are the extra info printing the next_agino to be the same
>> agino 3064909 for xfs_iunlink_lookup has failed.
>
> Yep, then runtime code encounters agi[0].unlinked[13] == 3064909, but
> doesn't find an xfs_inode in the cache for it, and shuts down the
> filesystem.
>
Sure, thanks for the info.
> --D
>
>>
>> [ 587.999701] CPU: 48 PID: 2026 Comm: in:imjournal Tainted: G W 6.2.0-rc8ssh+ #38
>> [ 587.999705] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
>> [ 587.999708] Call Trace:
>> [ 587.999709] [c00000001aa838f0] [c000000000e87328] dump_stack_lvl+0x6c/0x9c (unreliable)
>> [ 587.999715] [c00000001aa83920] [c008000000646a84] xfs_error_report+0x5c/0x80 [xfs]
>> [ 587.999767] [c00000001aa83980] [c008000000676860] xfs_trans_cancel+0x178/0x1b0 [xfs]
>> [ 587.999823] [c00000001aa839d0] [c008000000664b34] xfs_rename+0x9cc/0xd10 [xfs]
>> [ 587.999876] [c00000001aa83b10] [c00800000065e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
>> [ 587.999929] [c00000001aa83ba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
>> [ 587.999933] [c00000001aa83c90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
>> [ 587.999937] [c00000001aa83de0] [c000000000580520] sys_rename+0x60/0x80
>> [ 587.999941] [c00000001aa83e10] [c000000000033630] system_call_exception+0x150/0x3b0
>> [ 587.999945] [c00000001aa83e50] [c00000000000c554] system_call_common+0xf4/0x258
>> [ 587.999950] --- interrupt: c00 at 0x7fff96082e20
>> [ 587.999952] NIP: 00007fff96082e20 LR: 00007fff95c45e24 CTR: 0000000000000000
>> [ 587.999955] REGS: c00000001aa83e80 TRAP: 0c00 Tainted: G W (6.2.0-rc8ssh+)
>> [ 587.999958] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
>> [ 587.999967] IRQMASK: 0
>> [ 587.999967] GPR00: 0000000000000026 00007fff94f5d220 00007fff96207300 00007fff94f5d288
>> [ 587.999967] GPR04: 0000000172b76b70 0000000000000000 0600000000000000 0000000000000002
>> [ 587.999967] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> [ 587.999967] GPR12: 0000000000000000 00007fff94f666e0 0000000172b65930 0000000000000000
>> [ 587.999967] GPR16: 0000000132fe7648 00007fff95c47ce0 0000000000000000 000000000000004c
>> [ 587.999967] GPR20: 0000000000000082 00007fff94f5e3a0 00007fff94f5e398 00007fff880029b0
>> [ 587.999967] GPR24: 0000000000000000 00007fff94f5e388 00007fff94f5e378 00007fff94f5e3b0
>> [ 587.999967] GPR28: 00007fff95c60000 00007fff95c605e0 00007fff88000c10 00007fff94f5d288
>> [ 588.000000] NIP [00007fff96082e20] 0x7fff96082e20
>> [ 588.000002] LR [00007fff95c45e24] 0x7fff95c45e24
>> [ 588.000004] --- interrupt: c00
>> [ 588.012398] Core dump to |/usr/lib/systemd/systemd-coredump pipe failed
>> [ 588.020328] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
>> [ 588.020388] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
>>
>>
>> 4. Here is the patch diff which we used to collect the info.
>>
>> <patch>
>> =============
>>
>> root-> git diff
>> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
>> index 5808abab786c..86b8cab7f759 100644
>> --- a/fs/xfs/xfs_inode.c
>> +++ b/fs/xfs/xfs_inode.c
>> @@ -1859,8 +1859,10 @@ xfs_iunlink_update_backref(
>> return 0;
>>
>> ip = xfs_iunlink_lookup(pag, next_agino);
>> - if (!ip)
>> + if (!ip) {
>> + pr_err("%s: next_agino: %u cannot be found\n", __func__, next_agino);
>> return -EFSCORRUPTED;
>> + }
>> ip->i_prev_unlinked = prev_agino;
>> return 0;
>> }
>> @@ -1935,8 +1937,11 @@ xfs_iunlink_insert_inode(
>> * inode.
>> */
>> error = xfs_iunlink_update_backref(pag, agino, next_agino);
>> - if (error)
>> + if (error) {
>> + pr_crit("%s: Cannot find backref for agino:%u, ip->i_ino:%llu, next_agino: %u agno:%u\n",
>> + __func__, agino, ip->i_ino, next_agino, pag->pag_agno);
>> return error;
>> + }
>>
>> if (next_agino != NULLAGINO) {
>> /*
>> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
>> index fc61cc024023..035fc1eba871 100644
>> --- a/fs/xfs/xfs_log.c
>> +++ b/fs/xfs/xfs_log.c
>> @@ -825,6 +825,10 @@ xfs_log_mount_finish(
>> */
>> mp->m_super->s_flags |= SB_ACTIVE;
>> xfs_log_work_queue(mp);
>> + if (xlog_recovery_needed(log))
>> + pr_crit("%s: Recovery needed is set\n", __func__);
>> + else
>> + pr_crit("%s: Recovery needed not set\n", __func__);
>> if (xlog_recovery_needed(log))
>> error = xlog_recover_finish(log);
>> mp->m_super->s_flags &= ~SB_ACTIVE;
>> diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
>> index 322eb2ee6c55..6caa8147b443 100644
>> --- a/fs/xfs/xfs_log_recover.c
>> +++ b/fs/xfs/xfs_log_recover.c
>> @@ -2696,8 +2696,13 @@ xlog_recover_iunlink_bucket(
>> ASSERT(VFS_I(ip)->i_nlink == 0);
>> ASSERT(VFS_I(ip)->i_mode != 0);
>> xfs_iflags_clear(ip, XFS_IRECOVERY);
>> - agino = ip->i_next_unlinked;
>>
>> + if (bucket == 13) {
>> + pr_crit("%s: bucket: %d, agino: %u, ino: %llu, iget ret: %d, previno:%llu, prev_agino:%u\n",
>> + __func__, bucket, agino, ip->i_ino, error, prev_ip ? prev_ip->i_ino : -1, prev_ip ? XFS_INO_TO_AGINO(mp, prev_ip->i_ino) : -1);
>> + }
>> +
>> + agino = ip->i_next_unlinked;
>> if (prev_ip) {
>> ip->i_prev_unlinked = prev_agino;
>> xfs_irele(prev_ip);
>> @@ -2789,8 +2794,11 @@ xlog_recover_iunlink_ag(
>> * bucket and remaining inodes on it unreferenced and
>> * unfreeable.
>> */
>> + pr_crit("%s: Failed in xlog_recover_iunlink_bucket %d\n", __func__, error);
>> xfs_inodegc_flush(pag->pag_mount);
>> xlog_recover_clear_agi_bucket(pag, bucket);
>> + } else {
>> + pr_crit("%s: ran xlog_recover_iunlink_bucket for agi:%u, bucket:%d\n", __func__, pag->pag_agno, bucket);
>> }
>> }
>>
>>
>> > That evidence will guide us towards a kernel patch.
>>
>> I can spend some more time to debug and understand on how to fix this.
>> But thought of sharing this info meanwhile and see if there are any
>> pointers on how to fix this in kernel.
>>
>> Let me know if any other info is needed. We haven't yet run xfs_repair
>> on the device w/o -n option.
>>
>> -ritesh
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-03-10 0:29 ` Dave Chinner
@ 2023-03-16 4:48 ` Ritesh Harjani
0 siblings, 0 replies; 28+ messages in thread
From: Ritesh Harjani @ 2023-03-16 4:48 UTC (permalink / raw)
To: Dave Chinner
Cc: Darrick J. Wong, shrikanth hegde, dchinner, linux-xfs,
Srikar Dronamraju, ojaswin
Dave Chinner <david@fromorbit.com> writes:
> On Thu, Mar 09, 2023 at 07:56:06PM +0530, Ritesh Harjani wrote:
>> Hi Darrick,
>>
>> Please find the information collected from the system. We added some
>> debug logs and looks like it is exactly what is happening which you
>> pointed out.
>>
>> We added a debug kernel patch to get more info from the system which
>> you had requested [1]
>>
>> 1. We first breaked into emergency shell where root fs is first getting
>> mounted on /sysroot as "ro" filesystem. Here are the logs.
>>
>> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
>> Mounting /sysroot...
>> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
>> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
>> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
>> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
>> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
>> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
>> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
>> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
>> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
>> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
>> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
>> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
>> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
>> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
>> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
>> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
>> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
>> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
>>
>> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
>> the huge value.
>
> That's NULLFSINO and NULLAGINO respectively. That's the indication
> that this is the last inode on the chain and that the recovery loop
> should terminate at this inode.
>
> Nothing looks wrong to me there.
Yes, that's right.
>
>
>> 2. Then these are the logs from xfs_repair -n /dev/dm-0
>> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
>> printed in above xlog_recover_iunlink_ag() function.
>>
>> switch_root:/# xfs_repair -n /dev/dm-0
>> Phase 1 - find and verify superblock...
>> Phase 2 - using internal log
>> - zero log...
>> - scan filesystem freespace and inode maps...
>> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
>> - found root inode chunk
>> Phase 3 - for each AG...
>> - scan (but don't clear) agi unlinked lists...
>> - process known inodes and perform inode discovery...
>> - agno = 0
>> - agno = 1
>> - agno = 2
>> - agno = 3
>> - process newly discovered inodes...
>> Phase 4 - check for duplicate blocks...
>> - setting up duplicate extent list...
>> - check for inodes claiming duplicate blocks...
>> - agno = 0
>> - agno = 2
>> - agno = 1
>> - agno = 3
>> No modify flag set, skipping phase 5
>> Phase 6 - check inode connectivity...
>> - traversing filesystem ...
>> - traversal finished ...
>> - moving disconnected inodes to lost+found ...
>> Phase 7 - verify link counts...
>> would have reset inode 3064909 nlinks from 4294967291 to 2
>
> And there's the problem. The link count, as an signed int, is -5.
> It got reset to 2 probably because it was moved to lost+found due to
> having a non-zero link count. Not sure how it got to -5 and I
> suspect we'll never really know. However, I think that's irrelevant
> because if we fix the problem with unlink recovery failing to
> register an unlink recovery error from inodegc we'll intentionally
> leak the inode and it won't ever be a problem again.
>
>
>> No modify flag set, skipping filesystem flush and exiting.
>>
>>
>> 3. Then we exit from the shell for the system to continue booting.
>> Here it will continue.. Just pasting the logs where the warning gets
>> generated and some extra logs are getting printed for the same inode
>> with our patch.
>>
>>
>> it continues
>> ================
>> [ 587.999113] ------------[ cut here ]------------
>> [ 587.999121] WARNING: CPU: 48 PID: 2026 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
>
> Yeah, that happens because we failed to recover the unlinked inode,
> we don't feed errors that occur in inodegc back to the unlink
> recovery code, so it didn't clear the AGI bucket when we failed to
> remove the inode from the unlinked list in inodegc. Hence it goes to
> add the new inode to the start of unlinked list, and doesn't find the
> broken, unrecovered inode that the bucket points to in cache.
>
> IOWs, we fix the problem with feeding back errors from inodegc to
> iunlink recovery, and this specific issue will go away.
>
>> I can spend some more time to debug and understand on how to fix this.
>> But thought of sharing this info meanwhile and see if there are any
>> pointers on how to fix this in kernel.
>
> I suspect that we need to do something like gather an error in
> xfs_inodegc_flush() like we do for gathering the error in
> xfs_btree_split() from the offloaded xfs_btree_split_worker()...
>
Thanks Dave for pointers. I haven't yet started looking into it.
Once I get few other things off my plate. I can start looking into this.
-ritesh
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-03-16 4:46 ` Ritesh Harjani
@ 2023-03-16 5:20 ` Darrick J. Wong
2023-03-17 20:44 ` Darrick J. Wong
0 siblings, 1 reply; 28+ messages in thread
From: Darrick J. Wong @ 2023-03-16 5:20 UTC (permalink / raw)
To: Ritesh Harjani
Cc: shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On Thu, Mar 16, 2023 at 10:16:02AM +0530, Ritesh Harjani wrote:
> "Darrick J. Wong" <djwong@kernel.org> writes:
>
> Hi Darrick,
>
> Thanks for your analysis and quick help on this.
>
> >>
> >> Hi Darrick,
> >>
> >> Please find the information collected from the system. We added some
> >> debug logs and looks like it is exactly what is happening which you
> >> pointed out.
> >>
> >> We added a debug kernel patch to get more info from the system which
> >> you had requested [1]
> >>
> >> 1. We first breaked into emergency shell where root fs is first getting
> >> mounted on /sysroot as "ro" filesystem. Here are the logs.
> >>
> >> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
> >> Mounting /sysroot...
> >> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
> >> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
> >> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
> >> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
> >> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
> >> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
> >> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
> >> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
> >> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
> >> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
> >> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
> >> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
> >> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
> >> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
> >> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
> >> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
> >> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
> >> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
> >>
> >> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
> >> the huge value.
> >
> > Ok, so log recovery finds 3064909 and clears it...
> >
> >> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
> >> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
> >
> > <snip the rest of these...>
> >
> >> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
> >> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
> >> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
> >> [ OK ] Mounted /sysroot.
> >> [ OK ] Reached target Initrd Root File System.
> >>
> >>
> >> 2. Then these are the logs from xfs_repair -n /dev/dm-0
> >> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
> >> printed in above xlog_recover_iunlink_ag() function.
> >>
> >> switch_root:/# xfs_repair -n /dev/dm-0
> >> Phase 1 - find and verify superblock...
> >> Phase 2 - using internal log
> >> - zero log...
> >> - scan filesystem freespace and inode maps...
> >> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
> >
> > ...yet here we find that 3064909 is still on the unlinked list?
> >
> > Just to confirm -- you ran xfs_repair -n after the successful recovery
> > above, right?
> >
> Yes, that's right.
>
> >> - found root inode chunk
> >> Phase 3 - for each AG...
> >> - scan (but don't clear) agi unlinked lists...
> >> - process known inodes and perform inode discovery...
> >> - agno = 0
> >> - agno = 1
> >> - agno = 2
> >> - agno = 3
> >> - process newly discovered inodes...
> >> Phase 4 - check for duplicate blocks...
> >> - setting up duplicate extent list...
> >> - check for inodes claiming duplicate blocks...
> >> - agno = 0
> >> - agno = 2
> >> - agno = 1
> >> - agno = 3
> >> No modify flag set, skipping phase 5
> >> Phase 6 - check inode connectivity...
> >> - traversing filesystem ...
> >> - traversal finished ...
> >> - moving disconnected inodes to lost+found ...
> >> Phase 7 - verify link counts...
> >> would have reset inode 3064909 nlinks from 4294967291 to 2
> >
> > Oh now that's interesting. Inode on unlinked list with grossly nonzero
> > (but probably underflowed) link count. That might explain why iunlink
> > recovery ignores the inode. Is inode 3064909 reachable via the
> > directory tree?
> >
> > Would you mind sending me a metadump to play with? metadump -ago would
> > be best, if filenames/xattrnames aren't sensitive customer data.
>
> Sorry about the delay.
> I am checking for any permissions part internally.
> Meanwhile - I can help out if you would like me to try anything.
Ok. I'll try creating a filesystem with a weirdly high refcount
unlinked inode and I guess you can try it to see if you get the same
symptoms. I've finished with my parent pointers work for the time
being, so I might have some time tomorrow (after I kick the tires on
SETFSUUID) to simulate this and see if I can adapt the AGI repair code
to deal with this.
--D
> >> No modify flag set, skipping filesystem flush and exiting.
> >>
> >>
> >> 3. Then we exit from the shell for the system to continue booting.
> >> Here it will continue.. Just pasting the logs where the warning gets
> >> generated and some extra logs are getting printed for the same inode
> >> with our patch.
> >>
> >>
> >> it continues
> >> ================
> >> [ 587.999113] ------------[ cut here ]------------
> >> [ 587.999121] WARNING: CPU: 48 PID: 2026 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
> >> [ 587.999185] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc xts pseries_rng vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
> >> [ 587.999215] CPU: 48 PID: 2026 Comm: in:imjournal Not tainted 6.2.0-rc8ssh+ #38
> >> [ 587.999219] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> >> [ 587.999222] NIP: c00800000065fa80 LR: c00800000065fa4c CTR: c000000000ea4d40
> >> [ 587.999226] REGS: c00000001aa83650 TRAP: 0700 Not tainted (6.2.0-rc8ssh+)
> >> [ 587.999228] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24224842 XER: 00000000
> >> [ 587.999236] CFAR: c00800000065fa54 IRQMASK: 0
> >> [ 587.999236] GPR00: c00000004570b2c8 c00000001aa838f0 c008000000708300 0000000000000000
> >> [ 587.999236] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c00000000413faf0
> >> [ 587.999236] GPR08: 0000000000000000 c00000000413fba0 0000000000000000 fffffffffffffffd
> >> [ 587.999236] GPR12: 0000000000000040 c000004afeccd880 0000000000000000 0000000004000000
> >> [ 587.999236] GPR16: c00000001aa83b38 c00000001aa83a38 c00000001aa83a68 c000000035264c00
> >> [ 587.999236] GPR20: c00000004570b200 0000000000008000 c00000000886c400 00000000002ec44d
> >> [ 587.999236] GPR24: 000000000014040d 000000000000000d c000000051875400 00000000002ec44d
> >> [ 587.999236] GPR28: c000000035262c00 c00000004570b200 c00000008f2d8b90 000000000014040d
> >> [ 587.999272] NIP [c00800000065fa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
> >> [ 587.999327] LR [c00800000065fa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
> >> [ 587.999379] Call Trace:
> >> [ 587.999381] [c00000001aa838f0] [c00000008f2d8b90] 0xc00000008f2d8b90 (unreliable)
> >> [ 587.999385] [c00000001aa83910] [c008000000660094] xfs_iunlink+0x1bc/0x2c0 [xfs]
> >> [ 587.999438] [c00000001aa839d0] [c008000000664804] xfs_rename+0x69c/0xd10 [xfs]
> >> [ 587.999491] [c00000001aa83b10] [c00800000065e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
> >> [ 587.999544] [c00000001aa83ba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
> >> [ 587.999549] [c00000001aa83c90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
> >> [ 587.999553] [c00000001aa83de0] [c000000000580520] sys_rename+0x60/0x80
> >> [ 587.999557] [c00000001aa83e10] [c000000000033630] system_call_exception+0x150/0x3b0
> >> [ 587.999562] [c00000001aa83e50] [c00000000000c554] system_call_common+0xf4/0x258
> >> [ 587.999567] --- interrupt: c00 at 0x7fff96082e20
> >> [ 587.999569] NIP: 00007fff96082e20 LR: 00007fff95c45e24 CTR: 0000000000000000
> >> [ 587.999572] REGS: c00000001aa83e80 TRAP: 0c00 Not tainted (6.2.0-rc8ssh+)
> >> [ 587.999575] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
> >> [ 587.999584] IRQMASK: 0
> >> [ 587.999584] GPR00: 0000000000000026 00007fff94f5d220 00007fff96207300 00007fff94f5d288
> >> [ 587.999584] GPR04: 0000000172b76b70 0000000000000000 0600000000000000 0000000000000002
> >> [ 587.999584] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> >> [ 587.999584] GPR12: 0000000000000000 00007fff94f666e0 0000000172b65930 0000000000000000
> >> [ 587.999584] GPR16: 0000000132fe7648 00007fff95c47ce0 0000000000000000 000000000000004c
> >> [ 587.999584] GPR20: 0000000000000082 00007fff94f5e3a0 00007fff94f5e398 00007fff880029b0
> >> [ 587.999584] GPR24: 0000000000000000 00007fff94f5e388 00007fff94f5e378 00007fff94f5e3b0
> >> [ 587.999584] GPR28: 00007fff95c60000 00007fff95c605e0 00007fff88000c10 00007fff94f5d288
> >> [ 587.999618] NIP [00007fff96082e20] 0x7fff96082e20
> >> [ 587.999620] LR [00007fff95c45e24] 0x7fff95c45e24
> >> [ 587.999622] --- interrupt: c00
> >> [ 587.999624] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
> >> [ 587.999637] ---[ end trace 0000000000000000 ]---
> >> [ 587.999640] xfs_iunlink_update_backref: next_agino: 3064909 cannot be found
> >> [ 587.999643] xfs_iunlink_insert_inode: Cannot find backref for agino:1311757, ip->i_ino:1311757, next_agino: 3064909 agno:0
> >> [ 587.999646] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x9cc/0xd10 [xfs]
> >>
> >> ^^^ There are the extra info printing the next_agino to be the same
> >> agino 3064909 for xfs_iunlink_lookup has failed.
> >
> > Yep, then runtime code encounters agi[0].unlinked[13] == 3064909, but
> > doesn't find an xfs_inode in the cache for it, and shuts down the
> > filesystem.
> >
>
> Sure, thanks for the info.
>
> > --D
> >
> >>
> >> [ 587.999701] CPU: 48 PID: 2026 Comm: in:imjournal Tainted: G W 6.2.0-rc8ssh+ #38
> >> [ 587.999705] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> >> [ 587.999708] Call Trace:
> >> [ 587.999709] [c00000001aa838f0] [c000000000e87328] dump_stack_lvl+0x6c/0x9c (unreliable)
> >> [ 587.999715] [c00000001aa83920] [c008000000646a84] xfs_error_report+0x5c/0x80 [xfs]
> >> [ 587.999767] [c00000001aa83980] [c008000000676860] xfs_trans_cancel+0x178/0x1b0 [xfs]
> >> [ 587.999823] [c00000001aa839d0] [c008000000664b34] xfs_rename+0x9cc/0xd10 [xfs]
> >> [ 587.999876] [c00000001aa83b10] [c00800000065e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
> >> [ 587.999929] [c00000001aa83ba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
> >> [ 587.999933] [c00000001aa83c90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
> >> [ 587.999937] [c00000001aa83de0] [c000000000580520] sys_rename+0x60/0x80
> >> [ 587.999941] [c00000001aa83e10] [c000000000033630] system_call_exception+0x150/0x3b0
> >> [ 587.999945] [c00000001aa83e50] [c00000000000c554] system_call_common+0xf4/0x258
> >> [ 587.999950] --- interrupt: c00 at 0x7fff96082e20
> >> [ 587.999952] NIP: 00007fff96082e20 LR: 00007fff95c45e24 CTR: 0000000000000000
> >> [ 587.999955] REGS: c00000001aa83e80 TRAP: 0c00 Tainted: G W (6.2.0-rc8ssh+)
> >> [ 587.999958] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
> >> [ 587.999967] IRQMASK: 0
> >> [ 587.999967] GPR00: 0000000000000026 00007fff94f5d220 00007fff96207300 00007fff94f5d288
> >> [ 587.999967] GPR04: 0000000172b76b70 0000000000000000 0600000000000000 0000000000000002
> >> [ 587.999967] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> >> [ 587.999967] GPR12: 0000000000000000 00007fff94f666e0 0000000172b65930 0000000000000000
> >> [ 587.999967] GPR16: 0000000132fe7648 00007fff95c47ce0 0000000000000000 000000000000004c
> >> [ 587.999967] GPR20: 0000000000000082 00007fff94f5e3a0 00007fff94f5e398 00007fff880029b0
> >> [ 587.999967] GPR24: 0000000000000000 00007fff94f5e388 00007fff94f5e378 00007fff94f5e3b0
> >> [ 587.999967] GPR28: 00007fff95c60000 00007fff95c605e0 00007fff88000c10 00007fff94f5d288
> >> [ 588.000000] NIP [00007fff96082e20] 0x7fff96082e20
> >> [ 588.000002] LR [00007fff95c45e24] 0x7fff95c45e24
> >> [ 588.000004] --- interrupt: c00
> >> [ 588.012398] Core dump to |/usr/lib/systemd/systemd-coredump pipe failed
> >> [ 588.020328] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
> >> [ 588.020388] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
> >>
> >>
> >> 4. Here is the patch diff which we used to collect the info.
> >>
> >> <patch>
> >> =============
> >>
> >> root-> git diff
> >> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> >> index 5808abab786c..86b8cab7f759 100644
> >> --- a/fs/xfs/xfs_inode.c
> >> +++ b/fs/xfs/xfs_inode.c
> >> @@ -1859,8 +1859,10 @@ xfs_iunlink_update_backref(
> >> return 0;
> >>
> >> ip = xfs_iunlink_lookup(pag, next_agino);
> >> - if (!ip)
> >> + if (!ip) {
> >> + pr_err("%s: next_agino: %u cannot be found\n", __func__, next_agino);
> >> return -EFSCORRUPTED;
> >> + }
> >> ip->i_prev_unlinked = prev_agino;
> >> return 0;
> >> }
> >> @@ -1935,8 +1937,11 @@ xfs_iunlink_insert_inode(
> >> * inode.
> >> */
> >> error = xfs_iunlink_update_backref(pag, agino, next_agino);
> >> - if (error)
> >> + if (error) {
> >> + pr_crit("%s: Cannot find backref for agino:%u, ip->i_ino:%llu, next_agino: %u agno:%u\n",
> >> + __func__, agino, ip->i_ino, next_agino, pag->pag_agno);
> >> return error;
> >> + }
> >>
> >> if (next_agino != NULLAGINO) {
> >> /*
> >> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> >> index fc61cc024023..035fc1eba871 100644
> >> --- a/fs/xfs/xfs_log.c
> >> +++ b/fs/xfs/xfs_log.c
> >> @@ -825,6 +825,10 @@ xfs_log_mount_finish(
> >> */
> >> mp->m_super->s_flags |= SB_ACTIVE;
> >> xfs_log_work_queue(mp);
> >> + if (xlog_recovery_needed(log))
> >> + pr_crit("%s: Recovery needed is set\n", __func__);
> >> + else
> >> + pr_crit("%s: Recovery needed not set\n", __func__);
> >> if (xlog_recovery_needed(log))
> >> error = xlog_recover_finish(log);
> >> mp->m_super->s_flags &= ~SB_ACTIVE;
> >> diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
> >> index 322eb2ee6c55..6caa8147b443 100644
> >> --- a/fs/xfs/xfs_log_recover.c
> >> +++ b/fs/xfs/xfs_log_recover.c
> >> @@ -2696,8 +2696,13 @@ xlog_recover_iunlink_bucket(
> >> ASSERT(VFS_I(ip)->i_nlink == 0);
> >> ASSERT(VFS_I(ip)->i_mode != 0);
> >> xfs_iflags_clear(ip, XFS_IRECOVERY);
> >> - agino = ip->i_next_unlinked;
> >>
> >> + if (bucket == 13) {
> >> + pr_crit("%s: bucket: %d, agino: %u, ino: %llu, iget ret: %d, previno:%llu, prev_agino:%u\n",
> >> + __func__, bucket, agino, ip->i_ino, error, prev_ip ? prev_ip->i_ino : -1, prev_ip ? XFS_INO_TO_AGINO(mp, prev_ip->i_ino) : -1);
> >> + }
> >> +
> >> + agino = ip->i_next_unlinked;
> >> if (prev_ip) {
> >> ip->i_prev_unlinked = prev_agino;
> >> xfs_irele(prev_ip);
> >> @@ -2789,8 +2794,11 @@ xlog_recover_iunlink_ag(
> >> * bucket and remaining inodes on it unreferenced and
> >> * unfreeable.
> >> */
> >> + pr_crit("%s: Failed in xlog_recover_iunlink_bucket %d\n", __func__, error);
> >> xfs_inodegc_flush(pag->pag_mount);
> >> xlog_recover_clear_agi_bucket(pag, bucket);
> >> + } else {
> >> + pr_crit("%s: ran xlog_recover_iunlink_bucket for agi:%u, bucket:%d\n", __func__, pag->pag_agno, bucket);
> >> }
> >> }
> >>
> >>
> >> > That evidence will guide us towards a kernel patch.
> >>
> >> I can spend some more time to debug and understand on how to fix this.
> >> But thought of sharing this info meanwhile and see if there are any
> >> pointers on how to fix this in kernel.
> >>
> >> Let me know if any other info is needed. We haven't yet run xfs_repair
> >> on the device w/o -n option.
> >>
> >> -ritesh
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-03-16 5:20 ` Darrick J. Wong
@ 2023-03-17 20:44 ` Darrick J. Wong
2023-03-18 16:50 ` Ritesh Harjani
0 siblings, 1 reply; 28+ messages in thread
From: Darrick J. Wong @ 2023-03-17 20:44 UTC (permalink / raw)
To: Ritesh Harjani
Cc: shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
[-- Attachment #1: Type: text/plain, Size: 19115 bytes --]
On Wed, Mar 15, 2023 at 10:20:37PM -0700, Darrick J. Wong wrote:
> On Thu, Mar 16, 2023 at 10:16:02AM +0530, Ritesh Harjani wrote:
> > "Darrick J. Wong" <djwong@kernel.org> writes:
> >
> > Hi Darrick,
> >
> > Thanks for your analysis and quick help on this.
> >
> > >>
> > >> Hi Darrick,
> > >>
> > >> Please find the information collected from the system. We added some
> > >> debug logs and looks like it is exactly what is happening which you
> > >> pointed out.
> > >>
> > >> We added a debug kernel patch to get more info from the system which
> > >> you had requested [1]
> > >>
> > >> 1. We first breaked into emergency shell where root fs is first getting
> > >> mounted on /sysroot as "ro" filesystem. Here are the logs.
> > >>
> > >> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
> > >> Mounting /sysroot...
> > >> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
> > >> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
> > >> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
> > >> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
> > >> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
> > >> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
> > >> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
> > >> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
> > >> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
> > >> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
> > >> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
> > >> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
> > >> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
> > >> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
> > >> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
> > >> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
> > >> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
> > >> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
> > >>
> > >> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
> > >> the huge value.
> > >
> > > Ok, so log recovery finds 3064909 and clears it...
> > >
> > >> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
> > >> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
> > >
> > > <snip the rest of these...>
> > >
> > >> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
> > >> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
> > >> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
> > >> [ OK ] Mounted /sysroot.
> > >> [ OK ] Reached target Initrd Root File System.
> > >>
> > >>
> > >> 2. Then these are the logs from xfs_repair -n /dev/dm-0
> > >> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
> > >> printed in above xlog_recover_iunlink_ag() function.
> > >>
> > >> switch_root:/# xfs_repair -n /dev/dm-0
> > >> Phase 1 - find and verify superblock...
> > >> Phase 2 - using internal log
> > >> - zero log...
> > >> - scan filesystem freespace and inode maps...
> > >> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
> > >
> > > ...yet here we find that 3064909 is still on the unlinked list?
> > >
> > > Just to confirm -- you ran xfs_repair -n after the successful recovery
> > > above, right?
> > >
> > Yes, that's right.
> >
> > >> - found root inode chunk
> > >> Phase 3 - for each AG...
> > >> - scan (but don't clear) agi unlinked lists...
> > >> - process known inodes and perform inode discovery...
> > >> - agno = 0
> > >> - agno = 1
> > >> - agno = 2
> > >> - agno = 3
> > >> - process newly discovered inodes...
> > >> Phase 4 - check for duplicate blocks...
> > >> - setting up duplicate extent list...
> > >> - check for inodes claiming duplicate blocks...
> > >> - agno = 0
> > >> - agno = 2
> > >> - agno = 1
> > >> - agno = 3
> > >> No modify flag set, skipping phase 5
> > >> Phase 6 - check inode connectivity...
> > >> - traversing filesystem ...
> > >> - traversal finished ...
> > >> - moving disconnected inodes to lost+found ...
> > >> Phase 7 - verify link counts...
> > >> would have reset inode 3064909 nlinks from 4294967291 to 2
> > >
> > > Oh now that's interesting. Inode on unlinked list with grossly nonzero
> > > (but probably underflowed) link count. That might explain why iunlink
> > > recovery ignores the inode. Is inode 3064909 reachable via the
> > > directory tree?
> > >
> > > Would you mind sending me a metadump to play with? metadump -ago would
> > > be best, if filenames/xattrnames aren't sensitive customer data.
> >
> > Sorry about the delay.
> > I am checking for any permissions part internally.
> > Meanwhile - I can help out if you would like me to try anything.
>
> Ok. I'll try creating a filesystem with a weirdly high refcount
> unlinked inode and I guess you can try it to see if you get the same
> symptoms. I've finished with my parent pointers work for the time
> being, so I might have some time tomorrow (after I kick the tires on
> SETFSUUID) to simulate this and see if I can adapt the AGI repair code
> to deal with this.
If you uncompress and mdrestore the attached file to a blockdev, mount
it, and run some creat() exerciser, do you get the same symptoms? I've
figured out how to make online fsck deal with it. :)
A possible solution for runtime would be to make it so that
xfs_iunlink_lookup could iget the inode if it's not in cache at all.
--D
> --D
>
> > >> No modify flag set, skipping filesystem flush and exiting.
> > >>
> > >>
> > >> 3. Then we exit from the shell for the system to continue booting.
> > >> Here it will continue.. Just pasting the logs where the warning gets
> > >> generated and some extra logs are getting printed for the same inode
> > >> with our patch.
> > >>
> > >>
> > >> it continues
> > >> ================
> > >> [ 587.999113] ------------[ cut here ]------------
> > >> [ 587.999121] WARNING: CPU: 48 PID: 2026 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs]
> > >> [ 587.999185] Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink rfkill sunrpc xts pseries_rng vmx_crypto xfs libcrc32c sd_mod sg ibmvscsi ibmveth scsi_transport_srp nvme nvme_core t10_pi crc64_rocksoft crc64 dm_mirror dm_region_hash dm_log dm_mod
> > >> [ 587.999215] CPU: 48 PID: 2026 Comm: in:imjournal Not tainted 6.2.0-rc8ssh+ #38
> > >> [ 587.999219] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> > >> [ 587.999222] NIP: c00800000065fa80 LR: c00800000065fa4c CTR: c000000000ea4d40
> > >> [ 587.999226] REGS: c00000001aa83650 TRAP: 0700 Not tainted (6.2.0-rc8ssh+)
> > >> [ 587.999228] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 24224842 XER: 00000000
> > >> [ 587.999236] CFAR: c00800000065fa54 IRQMASK: 0
> > >> [ 587.999236] GPR00: c00000004570b2c8 c00000001aa838f0 c008000000708300 0000000000000000
> > >> [ 587.999236] GPR04: 00000000002ec44d 0000000000000000 0000000000000000 c00000000413faf0
> > >> [ 587.999236] GPR08: 0000000000000000 c00000000413fba0 0000000000000000 fffffffffffffffd
> > >> [ 587.999236] GPR12: 0000000000000040 c000004afeccd880 0000000000000000 0000000004000000
> > >> [ 587.999236] GPR16: c00000001aa83b38 c00000001aa83a38 c00000001aa83a68 c000000035264c00
> > >> [ 587.999236] GPR20: c00000004570b200 0000000000008000 c00000000886c400 00000000002ec44d
> > >> [ 587.999236] GPR24: 000000000014040d 000000000000000d c000000051875400 00000000002ec44d
> > >> [ 587.999236] GPR28: c000000035262c00 c00000004570b200 c00000008f2d8b90 000000000014040d
> > >> [ 587.999272] NIP [c00800000065fa80] xfs_iunlink_lookup+0x58/0x80 [xfs]
> > >> [ 587.999327] LR [c00800000065fa4c] xfs_iunlink_lookup+0x24/0x80 [xfs]
> > >> [ 587.999379] Call Trace:
> > >> [ 587.999381] [c00000001aa838f0] [c00000008f2d8b90] 0xc00000008f2d8b90 (unreliable)
> > >> [ 587.999385] [c00000001aa83910] [c008000000660094] xfs_iunlink+0x1bc/0x2c0 [xfs]
> > >> [ 587.999438] [c00000001aa839d0] [c008000000664804] xfs_rename+0x69c/0xd10 [xfs]
> > >> [ 587.999491] [c00000001aa83b10] [c00800000065e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
> > >> [ 587.999544] [c00000001aa83ba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
> > >> [ 587.999549] [c00000001aa83c90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
> > >> [ 587.999553] [c00000001aa83de0] [c000000000580520] sys_rename+0x60/0x80
> > >> [ 587.999557] [c00000001aa83e10] [c000000000033630] system_call_exception+0x150/0x3b0
> > >> [ 587.999562] [c00000001aa83e50] [c00000000000c554] system_call_common+0xf4/0x258
> > >> [ 587.999567] --- interrupt: c00 at 0x7fff96082e20
> > >> [ 587.999569] NIP: 00007fff96082e20 LR: 00007fff95c45e24 CTR: 0000000000000000
> > >> [ 587.999572] REGS: c00000001aa83e80 TRAP: 0c00 Not tainted (6.2.0-rc8ssh+)
> > >> [ 587.999575] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
> > >> [ 587.999584] IRQMASK: 0
> > >> [ 587.999584] GPR00: 0000000000000026 00007fff94f5d220 00007fff96207300 00007fff94f5d288
> > >> [ 587.999584] GPR04: 0000000172b76b70 0000000000000000 0600000000000000 0000000000000002
> > >> [ 587.999584] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > >> [ 587.999584] GPR12: 0000000000000000 00007fff94f666e0 0000000172b65930 0000000000000000
> > >> [ 587.999584] GPR16: 0000000132fe7648 00007fff95c47ce0 0000000000000000 000000000000004c
> > >> [ 587.999584] GPR20: 0000000000000082 00007fff94f5e3a0 00007fff94f5e398 00007fff880029b0
> > >> [ 587.999584] GPR24: 0000000000000000 00007fff94f5e388 00007fff94f5e378 00007fff94f5e3b0
> > >> [ 587.999584] GPR28: 00007fff95c60000 00007fff95c605e0 00007fff88000c10 00007fff94f5d288
> > >> [ 587.999618] NIP [00007fff96082e20] 0x7fff96082e20
> > >> [ 587.999620] LR [00007fff95c45e24] 0x7fff95c45e24
> > >> [ 587.999622] --- interrupt: c00
> > >> [ 587.999624] Code: 2c230000 4182002c e9230020 2fa90000 419e0020 38210020 e8010010 7c0803a6 4e800020 60000000 60000000 60000000 <0fe00000> 60000000 60000000 60000000
> > >> [ 587.999637] ---[ end trace 0000000000000000 ]---
> > >> [ 587.999640] xfs_iunlink_update_backref: next_agino: 3064909 cannot be found
> > >> [ 587.999643] xfs_iunlink_insert_inode: Cannot find backref for agino:1311757, ip->i_ino:1311757, next_agino: 3064909 agno:0
> > >> [ 587.999646] XFS (dm-0): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_rename+0x9cc/0xd10 [xfs]
> > >>
> > >> ^^^ There are the extra info printing the next_agino to be the same
> > >> agino 3064909 for xfs_iunlink_lookup has failed.
> > >
> > > Yep, then runtime code encounters agi[0].unlinked[13] == 3064909, but
> > > doesn't find an xfs_inode in the cache for it, and shuts down the
> > > filesystem.
> > >
> >
> > Sure, thanks for the info.
> >
> > > --D
> > >
> > >>
> > >> [ 587.999701] CPU: 48 PID: 2026 Comm: in:imjournal Tainted: G W 6.2.0-rc8ssh+ #38
> > >> [ 587.999705] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1010.22 (NH1010_122) hv:phyp pSeries
> > >> [ 587.999708] Call Trace:
> > >> [ 587.999709] [c00000001aa838f0] [c000000000e87328] dump_stack_lvl+0x6c/0x9c (unreliable)
> > >> [ 587.999715] [c00000001aa83920] [c008000000646a84] xfs_error_report+0x5c/0x80 [xfs]
> > >> [ 587.999767] [c00000001aa83980] [c008000000676860] xfs_trans_cancel+0x178/0x1b0 [xfs]
> > >> [ 587.999823] [c00000001aa839d0] [c008000000664b34] xfs_rename+0x9cc/0xd10 [xfs]
> > >> [ 587.999876] [c00000001aa83b10] [c00800000065e020] xfs_vn_rename+0xf8/0x1f0 [xfs]
> > >> [ 587.999929] [c00000001aa83ba0] [c000000000579efc] vfs_rename+0x9bc/0xdf0
> > >> [ 587.999933] [c00000001aa83c90] [c00000000058018c] do_renameat2+0x3dc/0x5c0
> > >> [ 587.999937] [c00000001aa83de0] [c000000000580520] sys_rename+0x60/0x80
> > >> [ 587.999941] [c00000001aa83e10] [c000000000033630] system_call_exception+0x150/0x3b0
> > >> [ 587.999945] [c00000001aa83e50] [c00000000000c554] system_call_common+0xf4/0x258
> > >> [ 587.999950] --- interrupt: c00 at 0x7fff96082e20
> > >> [ 587.999952] NIP: 00007fff96082e20 LR: 00007fff95c45e24 CTR: 0000000000000000
> > >> [ 587.999955] REGS: c00000001aa83e80 TRAP: 0c00 Tainted: G W (6.2.0-rc8ssh+)
> > >> [ 587.999958] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 2a082202 XER: 00000000
> > >> [ 587.999967] IRQMASK: 0
> > >> [ 587.999967] GPR00: 0000000000000026 00007fff94f5d220 00007fff96207300 00007fff94f5d288
> > >> [ 587.999967] GPR04: 0000000172b76b70 0000000000000000 0600000000000000 0000000000000002
> > >> [ 587.999967] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > >> [ 587.999967] GPR12: 0000000000000000 00007fff94f666e0 0000000172b65930 0000000000000000
> > >> [ 587.999967] GPR16: 0000000132fe7648 00007fff95c47ce0 0000000000000000 000000000000004c
> > >> [ 587.999967] GPR20: 0000000000000082 00007fff94f5e3a0 00007fff94f5e398 00007fff880029b0
> > >> [ 587.999967] GPR24: 0000000000000000 00007fff94f5e388 00007fff94f5e378 00007fff94f5e3b0
> > >> [ 587.999967] GPR28: 00007fff95c60000 00007fff95c605e0 00007fff88000c10 00007fff94f5d288
> > >> [ 588.000000] NIP [00007fff96082e20] 0x7fff96082e20
> > >> [ 588.000002] LR [00007fff95c45e24] 0x7fff95c45e24
> > >> [ 588.000004] --- interrupt: c00
> > >> [ 588.012398] Core dump to |/usr/lib/systemd/systemd-coredump pipe failed
> > >> [ 588.020328] XFS (dm-0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x190/0x1b0 [xfs] (fs/xfs/xfs_trans.c:1098). Shutting down filesystem.
> > >> [ 588.020388] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
> > >>
> > >>
> > >> 4. Here is the patch diff which we used to collect the info.
> > >>
> > >> <patch>
> > >> =============
> > >>
> > >> root-> git diff
> > >> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> > >> index 5808abab786c..86b8cab7f759 100644
> > >> --- a/fs/xfs/xfs_inode.c
> > >> +++ b/fs/xfs/xfs_inode.c
> > >> @@ -1859,8 +1859,10 @@ xfs_iunlink_update_backref(
> > >> return 0;
> > >>
> > >> ip = xfs_iunlink_lookup(pag, next_agino);
> > >> - if (!ip)
> > >> + if (!ip) {
> > >> + pr_err("%s: next_agino: %u cannot be found\n", __func__, next_agino);
> > >> return -EFSCORRUPTED;
> > >> + }
> > >> ip->i_prev_unlinked = prev_agino;
> > >> return 0;
> > >> }
> > >> @@ -1935,8 +1937,11 @@ xfs_iunlink_insert_inode(
> > >> * inode.
> > >> */
> > >> error = xfs_iunlink_update_backref(pag, agino, next_agino);
> > >> - if (error)
> > >> + if (error) {
> > >> + pr_crit("%s: Cannot find backref for agino:%u, ip->i_ino:%llu, next_agino: %u agno:%u\n",
> > >> + __func__, agino, ip->i_ino, next_agino, pag->pag_agno);
> > >> return error;
> > >> + }
> > >>
> > >> if (next_agino != NULLAGINO) {
> > >> /*
> > >> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> > >> index fc61cc024023..035fc1eba871 100644
> > >> --- a/fs/xfs/xfs_log.c
> > >> +++ b/fs/xfs/xfs_log.c
> > >> @@ -825,6 +825,10 @@ xfs_log_mount_finish(
> > >> */
> > >> mp->m_super->s_flags |= SB_ACTIVE;
> > >> xfs_log_work_queue(mp);
> > >> + if (xlog_recovery_needed(log))
> > >> + pr_crit("%s: Recovery needed is set\n", __func__);
> > >> + else
> > >> + pr_crit("%s: Recovery needed not set\n", __func__);
> > >> if (xlog_recovery_needed(log))
> > >> error = xlog_recover_finish(log);
> > >> mp->m_super->s_flags &= ~SB_ACTIVE;
> > >> diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
> > >> index 322eb2ee6c55..6caa8147b443 100644
> > >> --- a/fs/xfs/xfs_log_recover.c
> > >> +++ b/fs/xfs/xfs_log_recover.c
> > >> @@ -2696,8 +2696,13 @@ xlog_recover_iunlink_bucket(
> > >> ASSERT(VFS_I(ip)->i_nlink == 0);
> > >> ASSERT(VFS_I(ip)->i_mode != 0);
> > >> xfs_iflags_clear(ip, XFS_IRECOVERY);
> > >> - agino = ip->i_next_unlinked;
> > >>
> > >> + if (bucket == 13) {
> > >> + pr_crit("%s: bucket: %d, agino: %u, ino: %llu, iget ret: %d, previno:%llu, prev_agino:%u\n",
> > >> + __func__, bucket, agino, ip->i_ino, error, prev_ip ? prev_ip->i_ino : -1, prev_ip ? XFS_INO_TO_AGINO(mp, prev_ip->i_ino) : -1);
> > >> + }
> > >> +
> > >> + agino = ip->i_next_unlinked;
> > >> if (prev_ip) {
> > >> ip->i_prev_unlinked = prev_agino;
> > >> xfs_irele(prev_ip);
> > >> @@ -2789,8 +2794,11 @@ xlog_recover_iunlink_ag(
> > >> * bucket and remaining inodes on it unreferenced and
> > >> * unfreeable.
> > >> */
> > >> + pr_crit("%s: Failed in xlog_recover_iunlink_bucket %d\n", __func__, error);
> > >> xfs_inodegc_flush(pag->pag_mount);
> > >> xlog_recover_clear_agi_bucket(pag, bucket);
> > >> + } else {
> > >> + pr_crit("%s: ran xlog_recover_iunlink_bucket for agi:%u, bucket:%d\n", __func__, pag->pag_agno, bucket);
> > >> }
> > >> }
> > >>
> > >>
> > >> > That evidence will guide us towards a kernel patch.
> > >>
> > >> I can spend some more time to debug and understand on how to fix this.
> > >> But thought of sharing this info meanwhile and see if there are any
> > >> pointers on how to fix this in kernel.
> > >>
> > >> Let me know if any other info is needed. We haven't yet run xfs_repair
> > >> on the device w/o -n option.
> > >>
> > >> -ritesh
[-- Attachment #2: ritesh.md.xz --]
[-- Type: application/x-xz, Size: 9036 bytes --]
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-03-17 20:44 ` Darrick J. Wong
@ 2023-03-18 16:50 ` Ritesh Harjani
2023-03-18 19:20 ` Darrick J. Wong
0 siblings, 1 reply; 28+ messages in thread
From: Ritesh Harjani @ 2023-03-18 16:50 UTC (permalink / raw)
To: Darrick J. Wong
Cc: shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
"Darrick J. Wong" <djwong@kernel.org> writes:
> On Wed, Mar 15, 2023 at 10:20:37PM -0700, Darrick J. Wong wrote:
>> On Thu, Mar 16, 2023 at 10:16:02AM +0530, Ritesh Harjani wrote:
>> > "Darrick J. Wong" <djwong@kernel.org> writes:
>> >
>> > Hi Darrick,
>> >
>> > Thanks for your analysis and quick help on this.
>> >
>> > >>
>> > >> Hi Darrick,
>> > >>
>> > >> Please find the information collected from the system. We added some
>> > >> debug logs and looks like it is exactly what is happening which you
>> > >> pointed out.
>> > >>
>> > >> We added a debug kernel patch to get more info from the system which
>> > >> you had requested [1]
>> > >>
>> > >> 1. We first breaked into emergency shell where root fs is first getting
>> > >> mounted on /sysroot as "ro" filesystem. Here are the logs.
>> > >>
>> > >> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
>> > >> Mounting /sysroot...
>> > >> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
>> > >> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
>> > >> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
>> > >> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
>> > >> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
>> > >> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
>> > >> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
>> > >> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
>> > >> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
>> > >> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
>> > >> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
>> > >> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
>> > >> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
>> > >> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
>> > >> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
>> > >> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
>> > >> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
>> > >> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
>> > >>
>> > >> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
>> > >> the huge value.
>> > >
>> > > Ok, so log recovery finds 3064909 and clears it...
>> > >
>> > >> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
>> > >> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
>> > >
>> > > <snip the rest of these...>
>> > >
>> > >> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
>> > >> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
>> > >> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
>> > >> [ OK ] Mounted /sysroot.
>> > >> [ OK ] Reached target Initrd Root File System.
>> > >>
>> > >>
>> > >> 2. Then these are the logs from xfs_repair -n /dev/dm-0
>> > >> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
>> > >> printed in above xlog_recover_iunlink_ag() function.
>> > >>
>> > >> switch_root:/# xfs_repair -n /dev/dm-0
>> > >> Phase 1 - find and verify superblock...
>> > >> Phase 2 - using internal log
>> > >> - zero log...
>> > >> - scan filesystem freespace and inode maps...
>> > >> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
>> > >
>> > > ...yet here we find that 3064909 is still on the unlinked list?
>> > >
>> > > Just to confirm -- you ran xfs_repair -n after the successful recovery
>> > > above, right?
>> > >
>> > Yes, that's right.
>> >
>> > >> - found root inode chunk
>> > >> Phase 3 - for each AG...
>> > >> - scan (but don't clear) agi unlinked lists...
>> > >> - process known inodes and perform inode discovery...
>> > >> - agno = 0
>> > >> - agno = 1
>> > >> - agno = 2
>> > >> - agno = 3
>> > >> - process newly discovered inodes...
>> > >> Phase 4 - check for duplicate blocks...
>> > >> - setting up duplicate extent list...
>> > >> - check for inodes claiming duplicate blocks...
>> > >> - agno = 0
>> > >> - agno = 2
>> > >> - agno = 1
>> > >> - agno = 3
>> > >> No modify flag set, skipping phase 5
>> > >> Phase 6 - check inode connectivity...
>> > >> - traversing filesystem ...
>> > >> - traversal finished ...
>> > >> - moving disconnected inodes to lost+found ...
>> > >> Phase 7 - verify link counts...
>> > >> would have reset inode 3064909 nlinks from 4294967291 to 2
>> > >
>> > > Oh now that's interesting. Inode on unlinked list with grossly nonzero
>> > > (but probably underflowed) link count. That might explain why iunlink
>> > > recovery ignores the inode. Is inode 3064909 reachable via the
>> > > directory tree?
>> > >
>> > > Would you mind sending me a metadump to play with? metadump -ago would
>> > > be best, if filenames/xattrnames aren't sensitive customer data.
>> >
>> > Sorry about the delay.
>> > I am checking for any permissions part internally.
>> > Meanwhile - I can help out if you would like me to try anything.
>>
>> Ok. I'll try creating a filesystem with a weirdly high refcount
>> unlinked inode and I guess you can try it to see if you get the same
>> symptoms. I've finished with my parent pointers work for the time
>> being, so I might have some time tomorrow (after I kick the tires on
>> SETFSUUID) to simulate this and see if I can adapt the AGI repair code
>> to deal with this.
>
> If you uncompress and mdrestore the attached file to a blockdev, mount
> it, and run some creat() exerciser, do you get the same symptoms? I've
> figured out how to make online fsck deal with it. :)
>
> A possible solution for runtime would be to make it so that
> xfs_iunlink_lookup could iget the inode if it's not in cache at all.
>
Hello Darrick,
I did xfs_mdrestore the metadump you provided on a loop mounted
blockdev. I ran fsstress on the root dir of the mounted filesystem,
but I was unable to hit the issue.
I tried the same with the original FS metadump as well and I am unable
to hit the issue while running fsstress on the filesystem.
I am thinking of identifying which file unlink operation was in progress
when we see the issue during mounting. Maybe that will help in
recreating the issue.
Although the xfs_repair -n does show a similar log of unlinked inode
with the metadump you provided.
root@ubuntu:~# xfs_repair -n -o force_geometry /dev/loop7
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
agi unlinked bucket 3 is 6979 in ag 0 (inode=6979)
agi unlinked bucket 4 is 6980 in ag 0 (inode=6980)
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 6979, would move to lost+found
disconnected inode 6980, would move to lost+found
Phase 7 - verify link counts...
would have reset inode 6979 nlinks from 5555 to 1
would have reset inode 6980 nlinks from 0 to 1
No modify flag set, skipping filesystem flush and exiting.
Thanks again for the help. Once I have more info I will update the
thread!
-ritesh
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-03-18 16:50 ` Ritesh Harjani
@ 2023-03-18 19:20 ` Darrick J. Wong
2023-03-20 5:20 ` Ritesh Harjani
0 siblings, 1 reply; 28+ messages in thread
From: Darrick J. Wong @ 2023-03-18 19:20 UTC (permalink / raw)
To: Ritesh Harjani
Cc: shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On Sat, Mar 18, 2023 at 10:20:28PM +0530, Ritesh Harjani wrote:
> "Darrick J. Wong" <djwong@kernel.org> writes:
>
> > On Wed, Mar 15, 2023 at 10:20:37PM -0700, Darrick J. Wong wrote:
> >> On Thu, Mar 16, 2023 at 10:16:02AM +0530, Ritesh Harjani wrote:
> >> > "Darrick J. Wong" <djwong@kernel.org> writes:
> >> >
> >> > Hi Darrick,
> >> >
> >> > Thanks for your analysis and quick help on this.
> >> >
> >> > >>
> >> > >> Hi Darrick,
> >> > >>
> >> > >> Please find the information collected from the system. We added some
> >> > >> debug logs and looks like it is exactly what is happening which you
> >> > >> pointed out.
> >> > >>
> >> > >> We added a debug kernel patch to get more info from the system which
> >> > >> you had requested [1]
> >> > >>
> >> > >> 1. We first breaked into emergency shell where root fs is first getting
> >> > >> mounted on /sysroot as "ro" filesystem. Here are the logs.
> >> > >>
> >> > >> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
> >> > >> Mounting /sysroot...
> >> > >> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
> >> > >> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
> >> > >> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
> >> > >> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
> >> > >> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
> >> > >> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
> >> > >> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
> >> > >> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
> >> > >> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
> >> > >> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
> >> > >> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
> >> > >> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
> >> > >> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
> >> > >> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
> >> > >> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
> >> > >> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
> >> > >> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
> >> > >> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
> >> > >>
> >> > >> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
> >> > >> the huge value.
> >> > >
> >> > > Ok, so log recovery finds 3064909 and clears it...
> >> > >
> >> > >> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
> >> > >> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
> >> > >
> >> > > <snip the rest of these...>
> >> > >
> >> > >> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
> >> > >> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
> >> > >> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
> >> > >> [ OK ] Mounted /sysroot.
> >> > >> [ OK ] Reached target Initrd Root File System.
> >> > >>
> >> > >>
> >> > >> 2. Then these are the logs from xfs_repair -n /dev/dm-0
> >> > >> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
> >> > >> printed in above xlog_recover_iunlink_ag() function.
> >> > >>
> >> > >> switch_root:/# xfs_repair -n /dev/dm-0
> >> > >> Phase 1 - find and verify superblock...
> >> > >> Phase 2 - using internal log
> >> > >> - zero log...
> >> > >> - scan filesystem freespace and inode maps...
> >> > >> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
> >> > >
> >> > > ...yet here we find that 3064909 is still on the unlinked list?
> >> > >
> >> > > Just to confirm -- you ran xfs_repair -n after the successful recovery
> >> > > above, right?
> >> > >
> >> > Yes, that's right.
> >> >
> >> > >> - found root inode chunk
> >> > >> Phase 3 - for each AG...
> >> > >> - scan (but don't clear) agi unlinked lists...
> >> > >> - process known inodes and perform inode discovery...
> >> > >> - agno = 0
> >> > >> - agno = 1
> >> > >> - agno = 2
> >> > >> - agno = 3
> >> > >> - process newly discovered inodes...
> >> > >> Phase 4 - check for duplicate blocks...
> >> > >> - setting up duplicate extent list...
> >> > >> - check for inodes claiming duplicate blocks...
> >> > >> - agno = 0
> >> > >> - agno = 2
> >> > >> - agno = 1
> >> > >> - agno = 3
> >> > >> No modify flag set, skipping phase 5
> >> > >> Phase 6 - check inode connectivity...
> >> > >> - traversing filesystem ...
> >> > >> - traversal finished ...
> >> > >> - moving disconnected inodes to lost+found ...
> >> > >> Phase 7 - verify link counts...
> >> > >> would have reset inode 3064909 nlinks from 4294967291 to 2
> >> > >
> >> > > Oh now that's interesting. Inode on unlinked list with grossly nonzero
> >> > > (but probably underflowed) link count. That might explain why iunlink
> >> > > recovery ignores the inode. Is inode 3064909 reachable via the
> >> > > directory tree?
> >> > >
> >> > > Would you mind sending me a metadump to play with? metadump -ago would
> >> > > be best, if filenames/xattrnames aren't sensitive customer data.
> >> >
> >> > Sorry about the delay.
> >> > I am checking for any permissions part internally.
> >> > Meanwhile - I can help out if you would like me to try anything.
> >>
> >> Ok. I'll try creating a filesystem with a weirdly high refcount
> >> unlinked inode and I guess you can try it to see if you get the same
> >> symptoms. I've finished with my parent pointers work for the time
> >> being, so I might have some time tomorrow (after I kick the tires on
> >> SETFSUUID) to simulate this and see if I can adapt the AGI repair code
> >> to deal with this.
> >
> > If you uncompress and mdrestore the attached file to a blockdev, mount
> > it, and run some creat() exerciser, do you get the same symptoms? I've
> > figured out how to make online fsck deal with it. :)
> >
> > A possible solution for runtime would be to make it so that
> > xfs_iunlink_lookup could iget the inode if it's not in cache at all.
> >
>
> Hello Darrick,
>
> I did xfs_mdrestore the metadump you provided on a loop mounted
> blockdev. I ran fsstress on the root dir of the mounted filesystem,
> but I was unable to hit the issue.
>
> I tried the same with the original FS metadump as well and I am unable
> to hit the issue while running fsstress on the filesystem.
>
> I am thinking of identifying which file unlink operation was in progress
> when we see the issue during mounting. Maybe that will help in
> recreating the issue.
Yeah, creating a bunch of O_TMPFILE files will exercise the unlinked
lists, possibly enough to trip over the affected agi bucket. See
t_open_tmpfiles.c in the fstests repo.
--D
> Although the xfs_repair -n does show a similar log of unlinked inode
> with the metadump you provided.
>
> root@ubuntu:~# xfs_repair -n -o force_geometry /dev/loop7
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
> - zero log...
> - scan filesystem freespace and inode maps...
> agi unlinked bucket 3 is 6979 in ag 0 (inode=6979)
> agi unlinked bucket 4 is 6980 in ag 0 (inode=6980)
> - found root inode chunk
> Phase 3 - for each AG...
> - scan (but don't clear) agi unlinked lists...
> - process known inodes and perform inode discovery...
> - agno = 0
> - process newly discovered inodes...
> Phase 4 - check for duplicate blocks...
> - setting up duplicate extent list...
> - check for inodes claiming duplicate blocks...
> - agno = 0
> No modify flag set, skipping phase 5
> Phase 6 - check inode connectivity...
> - traversing filesystem ...
> - traversal finished ...
> - moving disconnected inodes to lost+found ...
> disconnected inode 6979, would move to lost+found
> disconnected inode 6980, would move to lost+found
> Phase 7 - verify link counts...
> would have reset inode 6979 nlinks from 5555 to 1
> would have reset inode 6980 nlinks from 0 to 1
> No modify flag set, skipping filesystem flush and exiting.
>
> Thanks again for the help. Once I have more info I will update the
> thread!
>
> -ritesh
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-03-18 19:20 ` Darrick J. Wong
@ 2023-03-20 5:20 ` Ritesh Harjani
2023-04-17 11:16 ` Linux regression tracking (Thorsten Leemhuis)
0 siblings, 1 reply; 28+ messages in thread
From: Ritesh Harjani @ 2023-03-20 5:20 UTC (permalink / raw)
To: Darrick J. Wong
Cc: shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
"Darrick J. Wong" <djwong@kernel.org> writes:
> On Sat, Mar 18, 2023 at 10:20:28PM +0530, Ritesh Harjani wrote:
>> "Darrick J. Wong" <djwong@kernel.org> writes:
>>
>> > On Wed, Mar 15, 2023 at 10:20:37PM -0700, Darrick J. Wong wrote:
>> >> On Thu, Mar 16, 2023 at 10:16:02AM +0530, Ritesh Harjani wrote:
>> >> > "Darrick J. Wong" <djwong@kernel.org> writes:
>> >> >
>> >> > Hi Darrick,
>> >> >
>> >> > Thanks for your analysis and quick help on this.
>> >> >
>> >> > >>
>> >> > >> Hi Darrick,
>> >> > >>
>> >> > >> Please find the information collected from the system. We added some
>> >> > >> debug logs and looks like it is exactly what is happening which you
>> >> > >> pointed out.
>> >> > >>
>> >> > >> We added a debug kernel patch to get more info from the system which
>> >> > >> you had requested [1]
>> >> > >>
>> >> > >> 1. We first breaked into emergency shell where root fs is first getting
>> >> > >> mounted on /sysroot as "ro" filesystem. Here are the logs.
>> >> > >>
>> >> > >> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
>> >> > >> Mounting /sysroot...
>> >> > >> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
>> >> > >> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
>> >> > >> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
>> >> > >> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
>> >> > >> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
>> >> > >> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
>> >> > >> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
>> >> > >> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
>> >> > >> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
>> >> > >> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
>> >> > >> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
>> >> > >> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
>> >> > >> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
>> >> > >> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
>> >> > >> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
>> >> > >> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
>> >> > >> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
>> >> > >> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
>> >> > >>
>> >> > >> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
>> >> > >> the huge value.
>> >> > >
>> >> > > Ok, so log recovery finds 3064909 and clears it...
>> >> > >
>> >> > >> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
>> >> > >> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
>> >> > >
>> >> > > <snip the rest of these...>
>> >> > >
>> >> > >> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
>> >> > >> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
>> >> > >> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
>> >> > >> [ OK ] Mounted /sysroot.
>> >> > >> [ OK ] Reached target Initrd Root File System.
>> >> > >>
>> >> > >>
>> >> > >> 2. Then these are the logs from xfs_repair -n /dev/dm-0
>> >> > >> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
>> >> > >> printed in above xlog_recover_iunlink_ag() function.
>> >> > >>
>> >> > >> switch_root:/# xfs_repair -n /dev/dm-0
>> >> > >> Phase 1 - find and verify superblock...
>> >> > >> Phase 2 - using internal log
>> >> > >> - zero log...
>> >> > >> - scan filesystem freespace and inode maps...
>> >> > >> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
>> >> > >
>> >> > > ...yet here we find that 3064909 is still on the unlinked list?
>> >> > >
>> >> > > Just to confirm -- you ran xfs_repair -n after the successful recovery
>> >> > > above, right?
>> >> > >
>> >> > Yes, that's right.
>> >> >
>> >> > >> - found root inode chunk
>> >> > >> Phase 3 - for each AG...
>> >> > >> - scan (but don't clear) agi unlinked lists...
>> >> > >> - process known inodes and perform inode discovery...
>> >> > >> - agno = 0
>> >> > >> - agno = 1
>> >> > >> - agno = 2
>> >> > >> - agno = 3
>> >> > >> - process newly discovered inodes...
>> >> > >> Phase 4 - check for duplicate blocks...
>> >> > >> - setting up duplicate extent list...
>> >> > >> - check for inodes claiming duplicate blocks...
>> >> > >> - agno = 0
>> >> > >> - agno = 2
>> >> > >> - agno = 1
>> >> > >> - agno = 3
>> >> > >> No modify flag set, skipping phase 5
>> >> > >> Phase 6 - check inode connectivity...
>> >> > >> - traversing filesystem ...
>> >> > >> - traversal finished ...
>> >> > >> - moving disconnected inodes to lost+found ...
>> >> > >> Phase 7 - verify link counts...
>> >> > >> would have reset inode 3064909 nlinks from 4294967291 to 2
>> >> > >
>> >> > > Oh now that's interesting. Inode on unlinked list with grossly nonzero
>> >> > > (but probably underflowed) link count. That might explain why iunlink
>> >> > > recovery ignores the inode. Is inode 3064909 reachable via the
>> >> > > directory tree?
>> >> > >
>> >> > > Would you mind sending me a metadump to play with? metadump -ago would
>> >> > > be best, if filenames/xattrnames aren't sensitive customer data.
>> >> >
>> >> > Sorry about the delay.
>> >> > I am checking for any permissions part internally.
>> >> > Meanwhile - I can help out if you would like me to try anything.
>> >>
>> >> Ok. I'll try creating a filesystem with a weirdly high refcount
>> >> unlinked inode and I guess you can try it to see if you get the same
>> >> symptoms. I've finished with my parent pointers work for the time
>> >> being, so I might have some time tomorrow (after I kick the tires on
>> >> SETFSUUID) to simulate this and see if I can adapt the AGI repair code
>> >> to deal with this.
>> >
>> > If you uncompress and mdrestore the attached file to a blockdev, mount
>> > it, and run some creat() exerciser, do you get the same symptoms? I've
>> > figured out how to make online fsck deal with it. :)
>> >
>> > A possible solution for runtime would be to make it so that
>> > xfs_iunlink_lookup could iget the inode if it's not in cache at all.
>> >
>>
>> Hello Darrick,
>>
>> I did xfs_mdrestore the metadump you provided on a loop mounted
>> blockdev. I ran fsstress on the root dir of the mounted filesystem,
>> but I was unable to hit the issue.
>>
>> I tried the same with the original FS metadump as well and I am unable
>> to hit the issue while running fsstress on the filesystem.
>>
>> I am thinking of identifying which file unlink operation was in progress
>> when we see the issue during mounting. Maybe that will help in
>> recreating the issue.
>
> Yeah, creating a bunch of O_TMPFILE files will exercise the unlinked
> lists, possibly enough to trip over the affected agi bucket. See
> t_open_tmpfiles.c in the fstests repo.
Hello Darrick,
Yes, I am tripping over the issue very easily when I run t_open_tmpfiles
testcase for the metadump you shared. (Not hitting with the original dump
though. Will try to fetch more information on whay is that).
Here is the call stack with your metadump when we try to run
t_open_tmpfiles test case.
Its the same warning message which we were hitting too in the original
case too.
xfs_iunlink_lookup()
<...>
/*
* Inode not in memory or in RCU freeing limbo should not happen.
* Warn about this and let the caller handle the failure.
*/
if (WARN_ON_ONCE(!ip || !ip->i_ino)) {
rcu_read_unlock();
return NULL;
}
<...>
[43873.070585] xfs filesystem being mounted at /mnt1/scratch supports timestamps until 2038 (0x7fffffff)
root@ubuntu:~# [43905.483065] ------------[ cut here ]------------
[43905.485250] WARNING: CPU: 0 PID: 2379 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x14c/0x1e0
[43905.488325] Modules linked in:
[43905.489594] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Not tainted 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
[43905.492828] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
[43905.496604] RIP: 0010:xfs_iunlink_lookup+0x14c/0x1e0
[43905.498341] Code: 0f 85 6e ff ff ff 48 c7 c2 a8 95 be 82 be 22 03 00 00 48 c7 c7 30 23 b7 82 c6 05 c8 71 84 01 01 e8 e9 d3 91 ff e9 6
[43905.504324] RSP: 0018:ffffc9000405fb98 EFLAGS: 00010246
[43905.506224] RAX: 0000000000000000 RBX: 0000000000001b43 RCX: 0000000000000000
[43905.508624] RDX: ffff8891f1edf488 RSI: ffff8891f1edf4c8 RDI: 0000000000001b43
[43905.511087] RBP: 0000000000001b43 R08: 0000000000000000 R09: ffff88931446ba80
[43905.514465] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[43905.517947] R13: ffff889313f67840 R14: ffff8892c0155b00 R15: ffff8889dc9b2900
[43905.521519] FS: 00007ffff7fb2740(0000) GS:ffff889dc7600000(0000) knlGS:0000000000000000
[43905.525570] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[43905.528402] CR2: 0000555555556060 CR3: 00000011b4790006 CR4: 0000000000170ef0
[43905.532008] Call Trace:
[43905.533399] <TASK>
[43905.534473] xfs_iunlink_insert_inode+0x7a/0x100
[43905.536663] xfs_iunlink+0xa4/0x190
[43905.537962] xfs_create_tmpfile+0x277/0x2e0
[43905.539654] xfs_generic_create+0x100/0x350
[43905.541303] xfs_vn_tmpfile+0x1f/0x40
[43905.542920] vfs_tmpfile+0x10e/0x1b0
[43905.544307] path_openat+0x157/0x200
[43905.545813] do_filp_open+0xad/0x150
[43905.547213] ? alloc_fd+0x12d/0x220
[43905.548646] ? alloc_fd+0x12d/0x220
[43905.550014] ? lock_release+0x7f/0x130
[43905.551435] ? do_raw_spin_unlock+0x4f/0xa0
[43905.553045] ? _raw_spin_unlock+0x2d/0x50
[43905.554554] ? alloc_fd+0x12d/0x220
[43905.556264] do_sys_openat2+0x9b/0x160
[43905.557680] __x64_sys_openat+0x58/0xa0
[43905.559065] do_syscall_64+0x3f/0x90
[43905.560589] entry_SYSCALL_64_after_hwframe+0x72/0xdc
[43905.562377] RIP: 0033:0x7ffff7d0ca45
[43905.563970] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
[43905.570038] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
[43905.572747] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
[43905.575246] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
[43905.577782] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
[43905.580315] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
[43905.582850] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
[43905.585438] </TASK>
[43905.586528] irq event stamp: 14045
[43905.587828] hardirqs last enabled at (14055): [<ffffffff8121bc02>] __up_console_sem+0x52/0x60
[43905.590861] hardirqs last disabled at (14066): [<ffffffff8121bbe7>] __up_console_sem+0x37/0x60
[43905.593856] softirqs last enabled at (13920): [<ffffffff82231b5a>] __do_softirq+0x2ea/0x3e1
[43905.596813] softirqs last disabled at (13909): [<ffffffff8119573f>] irq_exit_rcu+0xdf/0x140
[43905.599766] ---[ end trace 0000000000000000 ]---
[43905.601450] XFS (loop7): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_create_tmpfile+0x1c6/00
[43905.606100] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Tainted: G W 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
[43905.609797] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
[43905.614562] Call Trace:
[43905.616112] <TASK>
[43905.617245] dump_stack_lvl+0x66/0x80
[43905.619054] xfs_trans_cancel+0x138/0x1f0
[43905.620898] xfs_create_tmpfile+0x1c6/0x2e0
[43905.623140] xfs_generic_create+0x100/0x350
[43905.625483] xfs_vn_tmpfile+0x1f/0x40
[43905.627372] vfs_tmpfile+0x10e/0x1b0
[43905.629413] path_openat+0x157/0x200
[43905.631204] do_filp_open+0xad/0x150
[43905.633050] ? alloc_fd+0x12d/0x220
[43905.634844] ? alloc_fd+0x12d/0x220
[43905.636602] ? lock_release+0x7f/0x130
[43905.638479] ? do_raw_spin_unlock+0x4f/0xa0
[43905.640726] ? _raw_spin_unlock+0x2d/0x50
[43905.642916] ? alloc_fd+0x12d/0x220
[43905.644375] do_sys_openat2+0x9b/0x160
[43905.645763] __x64_sys_openat+0x58/0xa0
[43905.647145] do_syscall_64+0x3f/0x90
[43905.648685] entry_SYSCALL_64_after_hwframe+0x72/0xdc
[43905.650430] RIP: 0033:0x7ffff7d0ca45
[43905.651731] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
[43905.657637] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
[43905.660141] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
[43905.662525] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
[43905.665086] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
[43905.667455] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
[43905.669830] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
[43905.672193] </TASK>
[43905.689666] XFS (loop7): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x151/0x1f0 (fs/xfs/xfs_trans.c:1098). Shu.
[43905.694215] XFS (loop7): Please unmount the filesystem and rectify the problem(s)
-ritesh
>
> --D
>
>> Although the xfs_repair -n does show a similar log of unlinked inode
>> with the metadump you provided.
>>
>> root@ubuntu:~# xfs_repair -n -o force_geometry /dev/loop7
>> Phase 1 - find and verify superblock...
>> Phase 2 - using internal log
>> - zero log...
>> - scan filesystem freespace and inode maps...
>> agi unlinked bucket 3 is 6979 in ag 0 (inode=6979)
>> agi unlinked bucket 4 is 6980 in ag 0 (inode=6980)
>> - found root inode chunk
>> Phase 3 - for each AG...
>> - scan (but don't clear) agi unlinked lists...
>> - process known inodes and perform inode discovery...
>> - agno = 0
>> - process newly discovered inodes...
>> Phase 4 - check for duplicate blocks...
>> - setting up duplicate extent list...
>> - check for inodes claiming duplicate blocks...
>> - agno = 0
>> No modify flag set, skipping phase 5
>> Phase 6 - check inode connectivity...
>> - traversing filesystem ...
>> - traversal finished ...
>> - moving disconnected inodes to lost+found ...
>> disconnected inode 6979, would move to lost+found
>> disconnected inode 6980, would move to lost+found
>> Phase 7 - verify link counts...
>> would have reset inode 6979 nlinks from 5555 to 1
>> would have reset inode 6980 nlinks from 0 to 1
>> No modify flag set, skipping filesystem flush and exiting.
>>
>> Thanks again for the help. Once I have more info I will update the
>> thread!
>>
>> -ritesh
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-03-20 5:20 ` Ritesh Harjani
@ 2023-04-17 11:16 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-18 4:56 ` Darrick J. Wong
0 siblings, 1 reply; 28+ messages in thread
From: Linux regression tracking (Thorsten Leemhuis) @ 2023-04-17 11:16 UTC (permalink / raw)
To: Ritesh Harjani (IBM), Darrick J. Wong
Cc: shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin,
Linux kernel regressions list
Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
for once, to make this easily accessible to everyone.
Has any progress been made to fix below regression? It doesn't look like
it from here, hence I wondered if it fall through the cracks. Or is
there some good reason why this is safe to ignore?
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
#regzbot poke
On 20.03.23 06:20, Ritesh Harjani (IBM) wrote:
> "Darrick J. Wong" <djwong@kernel.org> writes:
>
>> On Sat, Mar 18, 2023 at 10:20:28PM +0530, Ritesh Harjani wrote:
>>> "Darrick J. Wong" <djwong@kernel.org> writes:
>>>
>>>> On Wed, Mar 15, 2023 at 10:20:37PM -0700, Darrick J. Wong wrote:
>>>>> On Thu, Mar 16, 2023 at 10:16:02AM +0530, Ritesh Harjani wrote:
>>>>>> "Darrick J. Wong" <djwong@kernel.org> writes:
>>>>>>
>>>>>> Hi Darrick,
>>>>>>
>>>>>> Thanks for your analysis and quick help on this.
>>>>>>
>>>>>>>>
>>>>>>>> Hi Darrick,
>>>>>>>>
>>>>>>>> Please find the information collected from the system. We added some
>>>>>>>> debug logs and looks like it is exactly what is happening which you
>>>>>>>> pointed out.
>>>>>>>>
>>>>>>>> We added a debug kernel patch to get more info from the system which
>>>>>>>> you had requested [1]
>>>>>>>>
>>>>>>>> 1. We first breaked into emergency shell where root fs is first getting
>>>>>>>> mounted on /sysroot as "ro" filesystem. Here are the logs.
>>>>>>>>
>>>>>>>> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
>>>>>>>> Mounting /sysroot...
>>>>>>>> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
>>>>>>>> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
>>>>>>>> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
>>>>>>>> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
>>>>>>>> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
>>>>>>>> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
>>>>>>>> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
>>>>>>>> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
>>>>>>>> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
>>>>>>>> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
>>>>>>>> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
>>>>>>>> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
>>>>>>>> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
>>>>>>>> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
>>>>>>>> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
>>>>>>>> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
>>>>>>>> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
>>>>>>>> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
>>>>>>>>
>>>>>>>> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
>>>>>>>> the huge value.
>>>>>>>
>>>>>>> Ok, so log recovery finds 3064909 and clears it...
>>>>>>>
>>>>>>>> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
>>>>>>>> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
>>>>>>>
>>>>>>> <snip the rest of these...>
>>>>>>>
>>>>>>>> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
>>>>>>>> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
>>>>>>>> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
>>>>>>>> [ OK ] Mounted /sysroot.
>>>>>>>> [ OK ] Reached target Initrd Root File System.
>>>>>>>>
>>>>>>>>
>>>>>>>> 2. Then these are the logs from xfs_repair -n /dev/dm-0
>>>>>>>> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
>>>>>>>> printed in above xlog_recover_iunlink_ag() function.
>>>>>>>>
>>>>>>>> switch_root:/# xfs_repair -n /dev/dm-0
>>>>>>>> Phase 1 - find and verify superblock...
>>>>>>>> Phase 2 - using internal log
>>>>>>>> - zero log...
>>>>>>>> - scan filesystem freespace and inode maps...
>>>>>>>> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
>>>>>>>
>>>>>>> ...yet here we find that 3064909 is still on the unlinked list?
>>>>>>>
>>>>>>> Just to confirm -- you ran xfs_repair -n after the successful recovery
>>>>>>> above, right?
>>>>>>>
>>>>>> Yes, that's right.
>>>>>>
>>>>>>>> - found root inode chunk
>>>>>>>> Phase 3 - for each AG...
>>>>>>>> - scan (but don't clear) agi unlinked lists...
>>>>>>>> - process known inodes and perform inode discovery...
>>>>>>>> - agno = 0
>>>>>>>> - agno = 1
>>>>>>>> - agno = 2
>>>>>>>> - agno = 3
>>>>>>>> - process newly discovered inodes...
>>>>>>>> Phase 4 - check for duplicate blocks...
>>>>>>>> - setting up duplicate extent list...
>>>>>>>> - check for inodes claiming duplicate blocks...
>>>>>>>> - agno = 0
>>>>>>>> - agno = 2
>>>>>>>> - agno = 1
>>>>>>>> - agno = 3
>>>>>>>> No modify flag set, skipping phase 5
>>>>>>>> Phase 6 - check inode connectivity...
>>>>>>>> - traversing filesystem ...
>>>>>>>> - traversal finished ...
>>>>>>>> - moving disconnected inodes to lost+found ...
>>>>>>>> Phase 7 - verify link counts...
>>>>>>>> would have reset inode 3064909 nlinks from 4294967291 to 2
>>>>>>>
>>>>>>> Oh now that's interesting. Inode on unlinked list with grossly nonzero
>>>>>>> (but probably underflowed) link count. That might explain why iunlink
>>>>>>> recovery ignores the inode. Is inode 3064909 reachable via the
>>>>>>> directory tree?
>>>>>>>
>>>>>>> Would you mind sending me a metadump to play with? metadump -ago would
>>>>>>> be best, if filenames/xattrnames aren't sensitive customer data.
>>>>>>
>>>>>> Sorry about the delay.
>>>>>> I am checking for any permissions part internally.
>>>>>> Meanwhile - I can help out if you would like me to try anything.
>>>>>
>>>>> Ok. I'll try creating a filesystem with a weirdly high refcount
>>>>> unlinked inode and I guess you can try it to see if you get the same
>>>>> symptoms. I've finished with my parent pointers work for the time
>>>>> being, so I might have some time tomorrow (after I kick the tires on
>>>>> SETFSUUID) to simulate this and see if I can adapt the AGI repair code
>>>>> to deal with this.
>>>>
>>>> If you uncompress and mdrestore the attached file to a blockdev, mount
>>>> it, and run some creat() exerciser, do you get the same symptoms? I've
>>>> figured out how to make online fsck deal with it. :)
>>>>
>>>> A possible solution for runtime would be to make it so that
>>>> xfs_iunlink_lookup could iget the inode if it's not in cache at all.
>>>>
>>>
>>> Hello Darrick,
>>>
>>> I did xfs_mdrestore the metadump you provided on a loop mounted
>>> blockdev. I ran fsstress on the root dir of the mounted filesystem,
>>> but I was unable to hit the issue.
>>>
>>> I tried the same with the original FS metadump as well and I am unable
>>> to hit the issue while running fsstress on the filesystem.
>>>
>>> I am thinking of identifying which file unlink operation was in progress
>>> when we see the issue during mounting. Maybe that will help in
>>> recreating the issue.
>>
>> Yeah, creating a bunch of O_TMPFILE files will exercise the unlinked
>> lists, possibly enough to trip over the affected agi bucket. See
>> t_open_tmpfiles.c in the fstests repo.
>
>
> Hello Darrick,
>
> Yes, I am tripping over the issue very easily when I run t_open_tmpfiles
> testcase for the metadump you shared. (Not hitting with the original dump
> though. Will try to fetch more information on whay is that).
>
> Here is the call stack with your metadump when we try to run
> t_open_tmpfiles test case.
> Its the same warning message which we were hitting too in the original
> case too.
>
> xfs_iunlink_lookup()
> <...>
> /*
> * Inode not in memory or in RCU freeing limbo should not happen.
> * Warn about this and let the caller handle the failure.
> */
> if (WARN_ON_ONCE(!ip || !ip->i_ino)) {
> rcu_read_unlock();
> return NULL;
> }
> <...>
>
> [43873.070585] xfs filesystem being mounted at /mnt1/scratch supports timestamps until 2038 (0x7fffffff)
> root@ubuntu:~# [43905.483065] ------------[ cut here ]------------
> [43905.485250] WARNING: CPU: 0 PID: 2379 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x14c/0x1e0
> [43905.488325] Modules linked in:
> [43905.489594] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Not tainted 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
> [43905.492828] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
> [43905.496604] RIP: 0010:xfs_iunlink_lookup+0x14c/0x1e0
> [43905.498341] Code: 0f 85 6e ff ff ff 48 c7 c2 a8 95 be 82 be 22 03 00 00 48 c7 c7 30 23 b7 82 c6 05 c8 71 84 01 01 e8 e9 d3 91 ff e9 6
> [43905.504324] RSP: 0018:ffffc9000405fb98 EFLAGS: 00010246
> [43905.506224] RAX: 0000000000000000 RBX: 0000000000001b43 RCX: 0000000000000000
> [43905.508624] RDX: ffff8891f1edf488 RSI: ffff8891f1edf4c8 RDI: 0000000000001b43
> [43905.511087] RBP: 0000000000001b43 R08: 0000000000000000 R09: ffff88931446ba80
> [43905.514465] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
> [43905.517947] R13: ffff889313f67840 R14: ffff8892c0155b00 R15: ffff8889dc9b2900
> [43905.521519] FS: 00007ffff7fb2740(0000) GS:ffff889dc7600000(0000) knlGS:0000000000000000
> [43905.525570] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [43905.528402] CR2: 0000555555556060 CR3: 00000011b4790006 CR4: 0000000000170ef0
> [43905.532008] Call Trace:
> [43905.533399] <TASK>
> [43905.534473] xfs_iunlink_insert_inode+0x7a/0x100
> [43905.536663] xfs_iunlink+0xa4/0x190
> [43905.537962] xfs_create_tmpfile+0x277/0x2e0
> [43905.539654] xfs_generic_create+0x100/0x350
> [43905.541303] xfs_vn_tmpfile+0x1f/0x40
> [43905.542920] vfs_tmpfile+0x10e/0x1b0
> [43905.544307] path_openat+0x157/0x200
> [43905.545813] do_filp_open+0xad/0x150
> [43905.547213] ? alloc_fd+0x12d/0x220
> [43905.548646] ? alloc_fd+0x12d/0x220
> [43905.550014] ? lock_release+0x7f/0x130
> [43905.551435] ? do_raw_spin_unlock+0x4f/0xa0
> [43905.553045] ? _raw_spin_unlock+0x2d/0x50
> [43905.554554] ? alloc_fd+0x12d/0x220
> [43905.556264] do_sys_openat2+0x9b/0x160
> [43905.557680] __x64_sys_openat+0x58/0xa0
> [43905.559065] do_syscall_64+0x3f/0x90
> [43905.560589] entry_SYSCALL_64_after_hwframe+0x72/0xdc
> [43905.562377] RIP: 0033:0x7ffff7d0ca45
> [43905.563970] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
> [43905.570038] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
> [43905.572747] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
> [43905.575246] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
> [43905.577782] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
> [43905.580315] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
> [43905.582850] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
> [43905.585438] </TASK>
> [43905.586528] irq event stamp: 14045
> [43905.587828] hardirqs last enabled at (14055): [<ffffffff8121bc02>] __up_console_sem+0x52/0x60
> [43905.590861] hardirqs last disabled at (14066): [<ffffffff8121bbe7>] __up_console_sem+0x37/0x60
> [43905.593856] softirqs last enabled at (13920): [<ffffffff82231b5a>] __do_softirq+0x2ea/0x3e1
> [43905.596813] softirqs last disabled at (13909): [<ffffffff8119573f>] irq_exit_rcu+0xdf/0x140
> [43905.599766] ---[ end trace 0000000000000000 ]---
> [43905.601450] XFS (loop7): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_create_tmpfile+0x1c6/00
> [43905.606100] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Tainted: G W 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
> [43905.609797] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
> [43905.614562] Call Trace:
> [43905.616112] <TASK>
> [43905.617245] dump_stack_lvl+0x66/0x80
> [43905.619054] xfs_trans_cancel+0x138/0x1f0
> [43905.620898] xfs_create_tmpfile+0x1c6/0x2e0
> [43905.623140] xfs_generic_create+0x100/0x350
> [43905.625483] xfs_vn_tmpfile+0x1f/0x40
> [43905.627372] vfs_tmpfile+0x10e/0x1b0
> [43905.629413] path_openat+0x157/0x200
> [43905.631204] do_filp_open+0xad/0x150
> [43905.633050] ? alloc_fd+0x12d/0x220
> [43905.634844] ? alloc_fd+0x12d/0x220
> [43905.636602] ? lock_release+0x7f/0x130
> [43905.638479] ? do_raw_spin_unlock+0x4f/0xa0
> [43905.640726] ? _raw_spin_unlock+0x2d/0x50
> [43905.642916] ? alloc_fd+0x12d/0x220
> [43905.644375] do_sys_openat2+0x9b/0x160
> [43905.645763] __x64_sys_openat+0x58/0xa0
> [43905.647145] do_syscall_64+0x3f/0x90
> [43905.648685] entry_SYSCALL_64_after_hwframe+0x72/0xdc
> [43905.650430] RIP: 0033:0x7ffff7d0ca45
> [43905.651731] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
> [43905.657637] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
> [43905.660141] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
> [43905.662525] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
> [43905.665086] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
> [43905.667455] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
> [43905.669830] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
> [43905.672193] </TASK>
> [43905.689666] XFS (loop7): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x151/0x1f0 (fs/xfs/xfs_trans.c:1098). Shu.
> [43905.694215] XFS (loop7): Please unmount the filesystem and rectify the problem(s)
>
>
> -ritesh
>
>
>>
>> --D
>>
>>> Although the xfs_repair -n does show a similar log of unlinked inode
>>> with the metadump you provided.
>>>
>>> root@ubuntu:~# xfs_repair -n -o force_geometry /dev/loop7
>>> Phase 1 - find and verify superblock...
>>> Phase 2 - using internal log
>>> - zero log...
>>> - scan filesystem freespace and inode maps...
>>> agi unlinked bucket 3 is 6979 in ag 0 (inode=6979)
>>> agi unlinked bucket 4 is 6980 in ag 0 (inode=6980)
>>> - found root inode chunk
>>> Phase 3 - for each AG...
>>> - scan (but don't clear) agi unlinked lists...
>>> - process known inodes and perform inode discovery...
>>> - agno = 0
>>> - process newly discovered inodes...
>>> Phase 4 - check for duplicate blocks...
>>> - setting up duplicate extent list...
>>> - check for inodes claiming duplicate blocks...
>>> - agno = 0
>>> No modify flag set, skipping phase 5
>>> Phase 6 - check inode connectivity...
>>> - traversing filesystem ...
>>> - traversal finished ...
>>> - moving disconnected inodes to lost+found ...
>>> disconnected inode 6979, would move to lost+found
>>> disconnected inode 6980, would move to lost+found
>>> Phase 7 - verify link counts...
>>> would have reset inode 6979 nlinks from 5555 to 1
>>> would have reset inode 6980 nlinks from 0 to 1
>>> No modify flag set, skipping filesystem flush and exiting.
>>>
>>> Thanks again for the help. Once I have more info I will update the
>>> thread!
>>>
>>> -ritesh
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-04-17 11:16 ` Linux regression tracking (Thorsten Leemhuis)
@ 2023-04-18 4:56 ` Darrick J. Wong
2023-04-21 13:04 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-05 13:27 ` Thorsten Leemhuis
0 siblings, 2 replies; 28+ messages in thread
From: Darrick J. Wong @ 2023-04-18 4:56 UTC (permalink / raw)
To: Linux regressions mailing list
Cc: Ritesh Harjani (IBM),
shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On Mon, Apr 17, 2023 at 01:16:53PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> for once, to make this easily accessible to everyone.
>
> Has any progress been made to fix below regression? It doesn't look like
> it from here, hence I wondered if it fall through the cracks. Or is
> there some good reason why this is safe to ignore?
Still working on thinking up a reasonable strategy to reload the incore
iunlink list if we trip over this. Online repair now knows how to do
this[1], but I haven't had time to figure out if this will work
generally. It's gotten very hard to keep my head above water with all
the fussy bots, syzbot zeroday public disclosures, and all the other
stuff I already had to do.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/tree/fs/xfs/scrub/agheader_repair.c?h=repair-iunlink&id=1b1cedf6888c309e6c31f76d5c831c5b5748f153#n1019
Also been busy helping Dave get online fsck fixes lifted to for-next,
QA'd, and rebasing djwong-dev atop all that.
--D
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
>
> #regzbot poke
>
> On 20.03.23 06:20, Ritesh Harjani (IBM) wrote:
> > "Darrick J. Wong" <djwong@kernel.org> writes:
> >
> >> On Sat, Mar 18, 2023 at 10:20:28PM +0530, Ritesh Harjani wrote:
> >>> "Darrick J. Wong" <djwong@kernel.org> writes:
> >>>
> >>>> On Wed, Mar 15, 2023 at 10:20:37PM -0700, Darrick J. Wong wrote:
> >>>>> On Thu, Mar 16, 2023 at 10:16:02AM +0530, Ritesh Harjani wrote:
> >>>>>> "Darrick J. Wong" <djwong@kernel.org> writes:
> >>>>>>
> >>>>>> Hi Darrick,
> >>>>>>
> >>>>>> Thanks for your analysis and quick help on this.
> >>>>>>
> >>>>>>>>
> >>>>>>>> Hi Darrick,
> >>>>>>>>
> >>>>>>>> Please find the information collected from the system. We added some
> >>>>>>>> debug logs and looks like it is exactly what is happening which you
> >>>>>>>> pointed out.
> >>>>>>>>
> >>>>>>>> We added a debug kernel patch to get more info from the system which
> >>>>>>>> you had requested [1]
> >>>>>>>>
> >>>>>>>> 1. We first breaked into emergency shell where root fs is first getting
> >>>>>>>> mounted on /sysroot as "ro" filesystem. Here are the logs.
> >>>>>>>>
> >>>>>>>> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
> >>>>>>>> Mounting /sysroot...
> >>>>>>>> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
> >>>>>>>> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
> >>>>>>>> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
> >>>>>>>> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
> >>>>>>>> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
> >>>>>>>> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
> >>>>>>>> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
> >>>>>>>> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
> >>>>>>>> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
> >>>>>>>> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
> >>>>>>>> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
> >>>>>>>> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
> >>>>>>>> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
> >>>>>>>> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
> >>>>>>>> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
> >>>>>>>> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
> >>>>>>>> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
> >>>>>>>> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
> >>>>>>>>
> >>>>>>>> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
> >>>>>>>> the huge value.
> >>>>>>>
> >>>>>>> Ok, so log recovery finds 3064909 and clears it...
> >>>>>>>
> >>>>>>>> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
> >>>>>>>> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
> >>>>>>>
> >>>>>>> <snip the rest of these...>
> >>>>>>>
> >>>>>>>> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
> >>>>>>>> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
> >>>>>>>> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
> >>>>>>>> [ OK ] Mounted /sysroot.
> >>>>>>>> [ OK ] Reached target Initrd Root File System.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> 2. Then these are the logs from xfs_repair -n /dev/dm-0
> >>>>>>>> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
> >>>>>>>> printed in above xlog_recover_iunlink_ag() function.
> >>>>>>>>
> >>>>>>>> switch_root:/# xfs_repair -n /dev/dm-0
> >>>>>>>> Phase 1 - find and verify superblock...
> >>>>>>>> Phase 2 - using internal log
> >>>>>>>> - zero log...
> >>>>>>>> - scan filesystem freespace and inode maps...
> >>>>>>>> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
> >>>>>>>
> >>>>>>> ...yet here we find that 3064909 is still on the unlinked list?
> >>>>>>>
> >>>>>>> Just to confirm -- you ran xfs_repair -n after the successful recovery
> >>>>>>> above, right?
> >>>>>>>
> >>>>>> Yes, that's right.
> >>>>>>
> >>>>>>>> - found root inode chunk
> >>>>>>>> Phase 3 - for each AG...
> >>>>>>>> - scan (but don't clear) agi unlinked lists...
> >>>>>>>> - process known inodes and perform inode discovery...
> >>>>>>>> - agno = 0
> >>>>>>>> - agno = 1
> >>>>>>>> - agno = 2
> >>>>>>>> - agno = 3
> >>>>>>>> - process newly discovered inodes...
> >>>>>>>> Phase 4 - check for duplicate blocks...
> >>>>>>>> - setting up duplicate extent list...
> >>>>>>>> - check for inodes claiming duplicate blocks...
> >>>>>>>> - agno = 0
> >>>>>>>> - agno = 2
> >>>>>>>> - agno = 1
> >>>>>>>> - agno = 3
> >>>>>>>> No modify flag set, skipping phase 5
> >>>>>>>> Phase 6 - check inode connectivity...
> >>>>>>>> - traversing filesystem ...
> >>>>>>>> - traversal finished ...
> >>>>>>>> - moving disconnected inodes to lost+found ...
> >>>>>>>> Phase 7 - verify link counts...
> >>>>>>>> would have reset inode 3064909 nlinks from 4294967291 to 2
> >>>>>>>
> >>>>>>> Oh now that's interesting. Inode on unlinked list with grossly nonzero
> >>>>>>> (but probably underflowed) link count. That might explain why iunlink
> >>>>>>> recovery ignores the inode. Is inode 3064909 reachable via the
> >>>>>>> directory tree?
> >>>>>>>
> >>>>>>> Would you mind sending me a metadump to play with? metadump -ago would
> >>>>>>> be best, if filenames/xattrnames aren't sensitive customer data.
> >>>>>>
> >>>>>> Sorry about the delay.
> >>>>>> I am checking for any permissions part internally.
> >>>>>> Meanwhile - I can help out if you would like me to try anything.
> >>>>>
> >>>>> Ok. I'll try creating a filesystem with a weirdly high refcount
> >>>>> unlinked inode and I guess you can try it to see if you get the same
> >>>>> symptoms. I've finished with my parent pointers work for the time
> >>>>> being, so I might have some time tomorrow (after I kick the tires on
> >>>>> SETFSUUID) to simulate this and see if I can adapt the AGI repair code
> >>>>> to deal with this.
> >>>>
> >>>> If you uncompress and mdrestore the attached file to a blockdev, mount
> >>>> it, and run some creat() exerciser, do you get the same symptoms? I've
> >>>> figured out how to make online fsck deal with it. :)
> >>>>
> >>>> A possible solution for runtime would be to make it so that
> >>>> xfs_iunlink_lookup could iget the inode if it's not in cache at all.
> >>>>
> >>>
> >>> Hello Darrick,
> >>>
> >>> I did xfs_mdrestore the metadump you provided on a loop mounted
> >>> blockdev. I ran fsstress on the root dir of the mounted filesystem,
> >>> but I was unable to hit the issue.
> >>>
> >>> I tried the same with the original FS metadump as well and I am unable
> >>> to hit the issue while running fsstress on the filesystem.
> >>>
> >>> I am thinking of identifying which file unlink operation was in progress
> >>> when we see the issue during mounting. Maybe that will help in
> >>> recreating the issue.
> >>
> >> Yeah, creating a bunch of O_TMPFILE files will exercise the unlinked
> >> lists, possibly enough to trip over the affected agi bucket. See
> >> t_open_tmpfiles.c in the fstests repo.
> >
> >
> > Hello Darrick,
> >
> > Yes, I am tripping over the issue very easily when I run t_open_tmpfiles
> > testcase for the metadump you shared. (Not hitting with the original dump
> > though. Will try to fetch more information on whay is that).
> >
> > Here is the call stack with your metadump when we try to run
> > t_open_tmpfiles test case.
> > Its the same warning message which we were hitting too in the original
> > case too.
> >
> > xfs_iunlink_lookup()
> > <...>
> > /*
> > * Inode not in memory or in RCU freeing limbo should not happen.
> > * Warn about this and let the caller handle the failure.
> > */
> > if (WARN_ON_ONCE(!ip || !ip->i_ino)) {
> > rcu_read_unlock();
> > return NULL;
> > }
> > <...>
> >
> > [43873.070585] xfs filesystem being mounted at /mnt1/scratch supports timestamps until 2038 (0x7fffffff)
> > root@ubuntu:~# [43905.483065] ------------[ cut here ]------------
> > [43905.485250] WARNING: CPU: 0 PID: 2379 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x14c/0x1e0
> > [43905.488325] Modules linked in:
> > [43905.489594] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Not tainted 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
> > [43905.492828] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
> > [43905.496604] RIP: 0010:xfs_iunlink_lookup+0x14c/0x1e0
> > [43905.498341] Code: 0f 85 6e ff ff ff 48 c7 c2 a8 95 be 82 be 22 03 00 00 48 c7 c7 30 23 b7 82 c6 05 c8 71 84 01 01 e8 e9 d3 91 ff e9 6
> > [43905.504324] RSP: 0018:ffffc9000405fb98 EFLAGS: 00010246
> > [43905.506224] RAX: 0000000000000000 RBX: 0000000000001b43 RCX: 0000000000000000
> > [43905.508624] RDX: ffff8891f1edf488 RSI: ffff8891f1edf4c8 RDI: 0000000000001b43
> > [43905.511087] RBP: 0000000000001b43 R08: 0000000000000000 R09: ffff88931446ba80
> > [43905.514465] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
> > [43905.517947] R13: ffff889313f67840 R14: ffff8892c0155b00 R15: ffff8889dc9b2900
> > [43905.521519] FS: 00007ffff7fb2740(0000) GS:ffff889dc7600000(0000) knlGS:0000000000000000
> > [43905.525570] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [43905.528402] CR2: 0000555555556060 CR3: 00000011b4790006 CR4: 0000000000170ef0
> > [43905.532008] Call Trace:
> > [43905.533399] <TASK>
> > [43905.534473] xfs_iunlink_insert_inode+0x7a/0x100
> > [43905.536663] xfs_iunlink+0xa4/0x190
> > [43905.537962] xfs_create_tmpfile+0x277/0x2e0
> > [43905.539654] xfs_generic_create+0x100/0x350
> > [43905.541303] xfs_vn_tmpfile+0x1f/0x40
> > [43905.542920] vfs_tmpfile+0x10e/0x1b0
> > [43905.544307] path_openat+0x157/0x200
> > [43905.545813] do_filp_open+0xad/0x150
> > [43905.547213] ? alloc_fd+0x12d/0x220
> > [43905.548646] ? alloc_fd+0x12d/0x220
> > [43905.550014] ? lock_release+0x7f/0x130
> > [43905.551435] ? do_raw_spin_unlock+0x4f/0xa0
> > [43905.553045] ? _raw_spin_unlock+0x2d/0x50
> > [43905.554554] ? alloc_fd+0x12d/0x220
> > [43905.556264] do_sys_openat2+0x9b/0x160
> > [43905.557680] __x64_sys_openat+0x58/0xa0
> > [43905.559065] do_syscall_64+0x3f/0x90
> > [43905.560589] entry_SYSCALL_64_after_hwframe+0x72/0xdc
> > [43905.562377] RIP: 0033:0x7ffff7d0ca45
> > [43905.563970] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
> > [43905.570038] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
> > [43905.572747] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
> > [43905.575246] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
> > [43905.577782] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
> > [43905.580315] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
> > [43905.582850] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
> > [43905.585438] </TASK>
> > [43905.586528] irq event stamp: 14045
> > [43905.587828] hardirqs last enabled at (14055): [<ffffffff8121bc02>] __up_console_sem+0x52/0x60
> > [43905.590861] hardirqs last disabled at (14066): [<ffffffff8121bbe7>] __up_console_sem+0x37/0x60
> > [43905.593856] softirqs last enabled at (13920): [<ffffffff82231b5a>] __do_softirq+0x2ea/0x3e1
> > [43905.596813] softirqs last disabled at (13909): [<ffffffff8119573f>] irq_exit_rcu+0xdf/0x140
> > [43905.599766] ---[ end trace 0000000000000000 ]---
> > [43905.601450] XFS (loop7): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_create_tmpfile+0x1c6/00
> > [43905.606100] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Tainted: G W 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
> > [43905.609797] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
> > [43905.614562] Call Trace:
> > [43905.616112] <TASK>
> > [43905.617245] dump_stack_lvl+0x66/0x80
> > [43905.619054] xfs_trans_cancel+0x138/0x1f0
> > [43905.620898] xfs_create_tmpfile+0x1c6/0x2e0
> > [43905.623140] xfs_generic_create+0x100/0x350
> > [43905.625483] xfs_vn_tmpfile+0x1f/0x40
> > [43905.627372] vfs_tmpfile+0x10e/0x1b0
> > [43905.629413] path_openat+0x157/0x200
> > [43905.631204] do_filp_open+0xad/0x150
> > [43905.633050] ? alloc_fd+0x12d/0x220
> > [43905.634844] ? alloc_fd+0x12d/0x220
> > [43905.636602] ? lock_release+0x7f/0x130
> > [43905.638479] ? do_raw_spin_unlock+0x4f/0xa0
> > [43905.640726] ? _raw_spin_unlock+0x2d/0x50
> > [43905.642916] ? alloc_fd+0x12d/0x220
> > [43905.644375] do_sys_openat2+0x9b/0x160
> > [43905.645763] __x64_sys_openat+0x58/0xa0
> > [43905.647145] do_syscall_64+0x3f/0x90
> > [43905.648685] entry_SYSCALL_64_after_hwframe+0x72/0xdc
> > [43905.650430] RIP: 0033:0x7ffff7d0ca45
> > [43905.651731] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
> > [43905.657637] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
> > [43905.660141] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
> > [43905.662525] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
> > [43905.665086] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
> > [43905.667455] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
> > [43905.669830] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
> > [43905.672193] </TASK>
> > [43905.689666] XFS (loop7): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x151/0x1f0 (fs/xfs/xfs_trans.c:1098). Shu.
> > [43905.694215] XFS (loop7): Please unmount the filesystem and rectify the problem(s)
> >
> >
> > -ritesh
> >
> >
> >>
> >> --D
> >>
> >>> Although the xfs_repair -n does show a similar log of unlinked inode
> >>> with the metadump you provided.
> >>>
> >>> root@ubuntu:~# xfs_repair -n -o force_geometry /dev/loop7
> >>> Phase 1 - find and verify superblock...
> >>> Phase 2 - using internal log
> >>> - zero log...
> >>> - scan filesystem freespace and inode maps...
> >>> agi unlinked bucket 3 is 6979 in ag 0 (inode=6979)
> >>> agi unlinked bucket 4 is 6980 in ag 0 (inode=6980)
> >>> - found root inode chunk
> >>> Phase 3 - for each AG...
> >>> - scan (but don't clear) agi unlinked lists...
> >>> - process known inodes and perform inode discovery...
> >>> - agno = 0
> >>> - process newly discovered inodes...
> >>> Phase 4 - check for duplicate blocks...
> >>> - setting up duplicate extent list...
> >>> - check for inodes claiming duplicate blocks...
> >>> - agno = 0
> >>> No modify flag set, skipping phase 5
> >>> Phase 6 - check inode connectivity...
> >>> - traversing filesystem ...
> >>> - traversal finished ...
> >>> - moving disconnected inodes to lost+found ...
> >>> disconnected inode 6979, would move to lost+found
> >>> disconnected inode 6980, would move to lost+found
> >>> Phase 7 - verify link counts...
> >>> would have reset inode 6979 nlinks from 5555 to 1
> >>> would have reset inode 6980 nlinks from 0 to 1
> >>> No modify flag set, skipping filesystem flush and exiting.
> >>>
> >>> Thanks again for the help. Once I have more info I will update the
> >>> thread!
> >>>
> >>> -ritesh
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-04-18 4:56 ` Darrick J. Wong
@ 2023-04-21 13:04 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-05 13:27 ` Thorsten Leemhuis
1 sibling, 0 replies; 28+ messages in thread
From: Linux regression tracking (Thorsten Leemhuis) @ 2023-04-21 13:04 UTC (permalink / raw)
To: Darrick J. Wong, Linux regressions mailing list
Cc: Ritesh Harjani (IBM),
shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On 18.04.23 06:56, Darrick J. Wong wrote:
> On Mon, Apr 17, 2023 at 01:16:53PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
>> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
>> for once, to make this easily accessible to everyone.
>>
>> Has any progress been made to fix below regression? It doesn't look like
>> it from here, hence I wondered if it fall through the cracks. Or is
>> there some good reason why this is safe to ignore?
>
> Still working on thinking up a reasonable strategy to reload the incore
> iunlink list if we trip over this. Online repair now knows how to do
> this[1], but I haven't had time to figure out if this will work
> generally.
Okay, thx for the update.
> It's gotten very hard to keep my head above water with all
> the fussy bots, syzbot zeroday public disclosures, and all the other
> stuff I already had to do.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/tree/fs/xfs/scrub/agheader_repair.c?h=repair-iunlink&id=1b1cedf6888c309e6c31f76d5c831c5b5748f153#n1019
Well, FWIW, you don't have to care about regzbot at all, if you fix
regressions in a timely manner and use Link: tags to point to the
reports -- both of which was expected even before regzbot came into
being (but yes, it made Link: tags more important).
But well, if we ever get into a discussion like this again, you don't
want to mentioned things like...
> Also been busy helping Dave get online fsck fixes lifted to for-next,
> QA'd, and rebasing djwong-dev atop all that.
...this the next time, as it sounds like feature work is taking
precedence over fixing regressions -- and that's something I (and Linus)
don't like to hear. But whatever, I'll for now assume there are good
reasons for that in this case.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
>> On 20.03.23 06:20, Ritesh Harjani (IBM) wrote:
>>> "Darrick J. Wong" <djwong@kernel.org> writes:
>>>
>>>> On Sat, Mar 18, 2023 at 10:20:28PM +0530, Ritesh Harjani wrote:
>>>>> "Darrick J. Wong" <djwong@kernel.org> writes:
>>>>>
>>>>>> On Wed, Mar 15, 2023 at 10:20:37PM -0700, Darrick J. Wong wrote:
>>>>>>> On Thu, Mar 16, 2023 at 10:16:02AM +0530, Ritesh Harjani wrote:
>>>>>>>> "Darrick J. Wong" <djwong@kernel.org> writes:
>>>>>>>>
>>>>>>>> Hi Darrick,
>>>>>>>>
>>>>>>>> Thanks for your analysis and quick help on this.
>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Darrick,
>>>>>>>>>>
>>>>>>>>>> Please find the information collected from the system. We added some
>>>>>>>>>> debug logs and looks like it is exactly what is happening which you
>>>>>>>>>> pointed out.
>>>>>>>>>>
>>>>>>>>>> We added a debug kernel patch to get more info from the system which
>>>>>>>>>> you had requested [1]
>>>>>>>>>>
>>>>>>>>>> 1. We first breaked into emergency shell where root fs is first getting
>>>>>>>>>> mounted on /sysroot as "ro" filesystem. Here are the logs.
>>>>>>>>>>
>>>>>>>>>> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
>>>>>>>>>> Mounting /sysroot...
>>>>>>>>>> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
>>>>>>>>>> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
>>>>>>>>>> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
>>>>>>>>>> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
>>>>>>>>>> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
>>>>>>>>>> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
>>>>>>>>>> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
>>>>>>>>>> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
>>>>>>>>>> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
>>>>>>>>>> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
>>>>>>>>>> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
>>>>>>>>>> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
>>>>>>>>>> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
>>>>>>>>>> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
>>>>>>>>>> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
>>>>>>>>>> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
>>>>>>>>>> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
>>>>>>>>>> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
>>>>>>>>>>
>>>>>>>>>> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
>>>>>>>>>> the huge value.
>>>>>>>>>
>>>>>>>>> Ok, so log recovery finds 3064909 and clears it...
>>>>>>>>>
>>>>>>>>>> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
>>>>>>>>>> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
>>>>>>>>>
>>>>>>>>> <snip the rest of these...>
>>>>>>>>>
>>>>>>>>>> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
>>>>>>>>>> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
>>>>>>>>>> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
>>>>>>>>>> [ OK ] Mounted /sysroot.
>>>>>>>>>> [ OK ] Reached target Initrd Root File System.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2. Then these are the logs from xfs_repair -n /dev/dm-0
>>>>>>>>>> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
>>>>>>>>>> printed in above xlog_recover_iunlink_ag() function.
>>>>>>>>>>
>>>>>>>>>> switch_root:/# xfs_repair -n /dev/dm-0
>>>>>>>>>> Phase 1 - find and verify superblock...
>>>>>>>>>> Phase 2 - using internal log
>>>>>>>>>> - zero log...
>>>>>>>>>> - scan filesystem freespace and inode maps...
>>>>>>>>>> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
>>>>>>>>>
>>>>>>>>> ...yet here we find that 3064909 is still on the unlinked list?
>>>>>>>>>
>>>>>>>>> Just to confirm -- you ran xfs_repair -n after the successful recovery
>>>>>>>>> above, right?
>>>>>>>>>
>>>>>>>> Yes, that's right.
>>>>>>>>
>>>>>>>>>> - found root inode chunk
>>>>>>>>>> Phase 3 - for each AG...
>>>>>>>>>> - scan (but don't clear) agi unlinked lists...
>>>>>>>>>> - process known inodes and perform inode discovery...
>>>>>>>>>> - agno = 0
>>>>>>>>>> - agno = 1
>>>>>>>>>> - agno = 2
>>>>>>>>>> - agno = 3
>>>>>>>>>> - process newly discovered inodes...
>>>>>>>>>> Phase 4 - check for duplicate blocks...
>>>>>>>>>> - setting up duplicate extent list...
>>>>>>>>>> - check for inodes claiming duplicate blocks...
>>>>>>>>>> - agno = 0
>>>>>>>>>> - agno = 2
>>>>>>>>>> - agno = 1
>>>>>>>>>> - agno = 3
>>>>>>>>>> No modify flag set, skipping phase 5
>>>>>>>>>> Phase 6 - check inode connectivity...
>>>>>>>>>> - traversing filesystem ...
>>>>>>>>>> - traversal finished ...
>>>>>>>>>> - moving disconnected inodes to lost+found ...
>>>>>>>>>> Phase 7 - verify link counts...
>>>>>>>>>> would have reset inode 3064909 nlinks from 4294967291 to 2
>>>>>>>>>
>>>>>>>>> Oh now that's interesting. Inode on unlinked list with grossly nonzero
>>>>>>>>> (but probably underflowed) link count. That might explain why iunlink
>>>>>>>>> recovery ignores the inode. Is inode 3064909 reachable via the
>>>>>>>>> directory tree?
>>>>>>>>>
>>>>>>>>> Would you mind sending me a metadump to play with? metadump -ago would
>>>>>>>>> be best, if filenames/xattrnames aren't sensitive customer data.
>>>>>>>>
>>>>>>>> Sorry about the delay.
>>>>>>>> I am checking for any permissions part internally.
>>>>>>>> Meanwhile - I can help out if you would like me to try anything.
>>>>>>>
>>>>>>> Ok. I'll try creating a filesystem with a weirdly high refcount
>>>>>>> unlinked inode and I guess you can try it to see if you get the same
>>>>>>> symptoms. I've finished with my parent pointers work for the time
>>>>>>> being, so I might have some time tomorrow (after I kick the tires on
>>>>>>> SETFSUUID) to simulate this and see if I can adapt the AGI repair code
>>>>>>> to deal with this.
>>>>>>
>>>>>> If you uncompress and mdrestore the attached file to a blockdev, mount
>>>>>> it, and run some creat() exerciser, do you get the same symptoms? I've
>>>>>> figured out how to make online fsck deal with it. :)
>>>>>>
>>>>>> A possible solution for runtime would be to make it so that
>>>>>> xfs_iunlink_lookup could iget the inode if it's not in cache at all.
>>>>>>
>>>>>
>>>>> Hello Darrick,
>>>>>
>>>>> I did xfs_mdrestore the metadump you provided on a loop mounted
>>>>> blockdev. I ran fsstress on the root dir of the mounted filesystem,
>>>>> but I was unable to hit the issue.
>>>>>
>>>>> I tried the same with the original FS metadump as well and I am unable
>>>>> to hit the issue while running fsstress on the filesystem.
>>>>>
>>>>> I am thinking of identifying which file unlink operation was in progress
>>>>> when we see the issue during mounting. Maybe that will help in
>>>>> recreating the issue.
>>>>
>>>> Yeah, creating a bunch of O_TMPFILE files will exercise the unlinked
>>>> lists, possibly enough to trip over the affected agi bucket. See
>>>> t_open_tmpfiles.c in the fstests repo.
>>>
>>>
>>> Hello Darrick,
>>>
>>> Yes, I am tripping over the issue very easily when I run t_open_tmpfiles
>>> testcase for the metadump you shared. (Not hitting with the original dump
>>> though. Will try to fetch more information on whay is that).
>>>
>>> Here is the call stack with your metadump when we try to run
>>> t_open_tmpfiles test case.
>>> Its the same warning message which we were hitting too in the original
>>> case too.
>>>
>>> xfs_iunlink_lookup()
>>> <...>
>>> /*
>>> * Inode not in memory or in RCU freeing limbo should not happen.
>>> * Warn about this and let the caller handle the failure.
>>> */
>>> if (WARN_ON_ONCE(!ip || !ip->i_ino)) {
>>> rcu_read_unlock();
>>> return NULL;
>>> }
>>> <...>
>>>
>>> [43873.070585] xfs filesystem being mounted at /mnt1/scratch supports timestamps until 2038 (0x7fffffff)
>>> root@ubuntu:~# [43905.483065] ------------[ cut here ]------------
>>> [43905.485250] WARNING: CPU: 0 PID: 2379 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x14c/0x1e0
>>> [43905.488325] Modules linked in:
>>> [43905.489594] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Not tainted 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
>>> [43905.492828] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
>>> [43905.496604] RIP: 0010:xfs_iunlink_lookup+0x14c/0x1e0
>>> [43905.498341] Code: 0f 85 6e ff ff ff 48 c7 c2 a8 95 be 82 be 22 03 00 00 48 c7 c7 30 23 b7 82 c6 05 c8 71 84 01 01 e8 e9 d3 91 ff e9 6
>>> [43905.504324] RSP: 0018:ffffc9000405fb98 EFLAGS: 00010246
>>> [43905.506224] RAX: 0000000000000000 RBX: 0000000000001b43 RCX: 0000000000000000
>>> [43905.508624] RDX: ffff8891f1edf488 RSI: ffff8891f1edf4c8 RDI: 0000000000001b43
>>> [43905.511087] RBP: 0000000000001b43 R08: 0000000000000000 R09: ffff88931446ba80
>>> [43905.514465] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
>>> [43905.517947] R13: ffff889313f67840 R14: ffff8892c0155b00 R15: ffff8889dc9b2900
>>> [43905.521519] FS: 00007ffff7fb2740(0000) GS:ffff889dc7600000(0000) knlGS:0000000000000000
>>> [43905.525570] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>>> [43905.528402] CR2: 0000555555556060 CR3: 00000011b4790006 CR4: 0000000000170ef0
>>> [43905.532008] Call Trace:
>>> [43905.533399] <TASK>
>>> [43905.534473] xfs_iunlink_insert_inode+0x7a/0x100
>>> [43905.536663] xfs_iunlink+0xa4/0x190
>>> [43905.537962] xfs_create_tmpfile+0x277/0x2e0
>>> [43905.539654] xfs_generic_create+0x100/0x350
>>> [43905.541303] xfs_vn_tmpfile+0x1f/0x40
>>> [43905.542920] vfs_tmpfile+0x10e/0x1b0
>>> [43905.544307] path_openat+0x157/0x200
>>> [43905.545813] do_filp_open+0xad/0x150
>>> [43905.547213] ? alloc_fd+0x12d/0x220
>>> [43905.548646] ? alloc_fd+0x12d/0x220
>>> [43905.550014] ? lock_release+0x7f/0x130
>>> [43905.551435] ? do_raw_spin_unlock+0x4f/0xa0
>>> [43905.553045] ? _raw_spin_unlock+0x2d/0x50
>>> [43905.554554] ? alloc_fd+0x12d/0x220
>>> [43905.556264] do_sys_openat2+0x9b/0x160
>>> [43905.557680] __x64_sys_openat+0x58/0xa0
>>> [43905.559065] do_syscall_64+0x3f/0x90
>>> [43905.560589] entry_SYSCALL_64_after_hwframe+0x72/0xdc
>>> [43905.562377] RIP: 0033:0x7ffff7d0ca45
>>> [43905.563970] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
>>> [43905.570038] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
>>> [43905.572747] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
>>> [43905.575246] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
>>> [43905.577782] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
>>> [43905.580315] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
>>> [43905.582850] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
>>> [43905.585438] </TASK>
>>> [43905.586528] irq event stamp: 14045
>>> [43905.587828] hardirqs last enabled at (14055): [<ffffffff8121bc02>] __up_console_sem+0x52/0x60
>>> [43905.590861] hardirqs last disabled at (14066): [<ffffffff8121bbe7>] __up_console_sem+0x37/0x60
>>> [43905.593856] softirqs last enabled at (13920): [<ffffffff82231b5a>] __do_softirq+0x2ea/0x3e1
>>> [43905.596813] softirqs last disabled at (13909): [<ffffffff8119573f>] irq_exit_rcu+0xdf/0x140
>>> [43905.599766] ---[ end trace 0000000000000000 ]---
>>> [43905.601450] XFS (loop7): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_create_tmpfile+0x1c6/00
>>> [43905.606100] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Tainted: G W 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
>>> [43905.609797] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
>>> [43905.614562] Call Trace:
>>> [43905.616112] <TASK>
>>> [43905.617245] dump_stack_lvl+0x66/0x80
>>> [43905.619054] xfs_trans_cancel+0x138/0x1f0
>>> [43905.620898] xfs_create_tmpfile+0x1c6/0x2e0
>>> [43905.623140] xfs_generic_create+0x100/0x350
>>> [43905.625483] xfs_vn_tmpfile+0x1f/0x40
>>> [43905.627372] vfs_tmpfile+0x10e/0x1b0
>>> [43905.629413] path_openat+0x157/0x200
>>> [43905.631204] do_filp_open+0xad/0x150
>>> [43905.633050] ? alloc_fd+0x12d/0x220
>>> [43905.634844] ? alloc_fd+0x12d/0x220
>>> [43905.636602] ? lock_release+0x7f/0x130
>>> [43905.638479] ? do_raw_spin_unlock+0x4f/0xa0
>>> [43905.640726] ? _raw_spin_unlock+0x2d/0x50
>>> [43905.642916] ? alloc_fd+0x12d/0x220
>>> [43905.644375] do_sys_openat2+0x9b/0x160
>>> [43905.645763] __x64_sys_openat+0x58/0xa0
>>> [43905.647145] do_syscall_64+0x3f/0x90
>>> [43905.648685] entry_SYSCALL_64_after_hwframe+0x72/0xdc
>>> [43905.650430] RIP: 0033:0x7ffff7d0ca45
>>> [43905.651731] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
>>> [43905.657637] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
>>> [43905.660141] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
>>> [43905.662525] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
>>> [43905.665086] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
>>> [43905.667455] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
>>> [43905.669830] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
>>> [43905.672193] </TASK>
>>> [43905.689666] XFS (loop7): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x151/0x1f0 (fs/xfs/xfs_trans.c:1098). Shu.
>>> [43905.694215] XFS (loop7): Please unmount the filesystem and rectify the problem(s)
>>>
>>>
>>> -ritesh
>>>
>>>
>>>>
>>>> --D
>>>>
>>>>> Although the xfs_repair -n does show a similar log of unlinked inode
>>>>> with the metadump you provided.
>>>>>
>>>>> root@ubuntu:~# xfs_repair -n -o force_geometry /dev/loop7
>>>>> Phase 1 - find and verify superblock...
>>>>> Phase 2 - using internal log
>>>>> - zero log...
>>>>> - scan filesystem freespace and inode maps...
>>>>> agi unlinked bucket 3 is 6979 in ag 0 (inode=6979)
>>>>> agi unlinked bucket 4 is 6980 in ag 0 (inode=6980)
>>>>> - found root inode chunk
>>>>> Phase 3 - for each AG...
>>>>> - scan (but don't clear) agi unlinked lists...
>>>>> - process known inodes and perform inode discovery...
>>>>> - agno = 0
>>>>> - process newly discovered inodes...
>>>>> Phase 4 - check for duplicate blocks...
>>>>> - setting up duplicate extent list...
>>>>> - check for inodes claiming duplicate blocks...
>>>>> - agno = 0
>>>>> No modify flag set, skipping phase 5
>>>>> Phase 6 - check inode connectivity...
>>>>> - traversing filesystem ...
>>>>> - traversal finished ...
>>>>> - moving disconnected inodes to lost+found ...
>>>>> disconnected inode 6979, would move to lost+found
>>>>> disconnected inode 6980, would move to lost+found
>>>>> Phase 7 - verify link counts...
>>>>> would have reset inode 6979 nlinks from 5555 to 1
>>>>> would have reset inode 6980 nlinks from 0 to 1
>>>>> No modify flag set, skipping filesystem flush and exiting.
>>>>>
>>>>> Thanks again for the help. Once I have more info I will update the
>>>>> thread!
>>>>>
>>>>> -ritesh
>
>
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-04-18 4:56 ` Darrick J. Wong
2023-04-21 13:04 ` Linux regression tracking (Thorsten Leemhuis)
@ 2023-06-05 13:27 ` Thorsten Leemhuis
2023-06-05 21:57 ` Darrick J. Wong
1 sibling, 1 reply; 28+ messages in thread
From: Thorsten Leemhuis @ 2023-06-05 13:27 UTC (permalink / raw)
To: Darrick J. Wong, Linux regressions mailing list
Cc: Ritesh Harjani (IBM),
shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
/me waves friendly
On 18.04.23 06:56, Darrick J. Wong wrote:
> On Mon, Apr 17, 2023 at 01:16:53PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
>> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
>> for once, to make this easily accessible to everyone.
>>
>> Has any progress been made to fix below regression? It doesn't look like
>> it from here, hence I wondered if it fall through the cracks. Or is
>> there some good reason why this is safe to ignore?
>
> Still working on thinking up a reasonable strategy to reload the incore
> iunlink list if we trip over this. Online repair now knows how to do
> this[1], but I haven't had time to figure out if this will work
> generally. [...]
I still have this issue on my list of tracked regressions, hence please
allow me to ask: was there any progress to resolve this? Doesn't look
like it, but from my point it's easy to miss something.
BTW, in case this was not yet addressed: if you have a few seconds,
could you please (just briefly!) explain why it seems to take quite a
while to resolve this? A "not booting" regressions sounds like something
that I'm pretty sure Linus normally wants to see addressed rather sooner
than later. But that apparently is not the case here. I know that XFS
devs normally take regressions seriously, hence I assume there are good
reasons for it. But I'd like to roughly understand them (is this a
extremely corner case issue others are unlike to run into or something
like that?), as I don't want Linus on my back with questions like "why
didn't you put more pressure on the XFS maintainers" or "you should have
told me about this".
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
#regzbot poke
>> On 20.03.23 06:20, Ritesh Harjani (IBM) wrote:
>>> "Darrick J. Wong" <djwong@kernel.org> writes:
>>>
>>>> On Sat, Mar 18, 2023 at 10:20:28PM +0530, Ritesh Harjani wrote:
>>>>> "Darrick J. Wong" <djwong@kernel.org> writes:
>>>>>
>>>>>> On Wed, Mar 15, 2023 at 10:20:37PM -0700, Darrick J. Wong wrote:
>>>>>>> On Thu, Mar 16, 2023 at 10:16:02AM +0530, Ritesh Harjani wrote:
>>>>>>>> "Darrick J. Wong" <djwong@kernel.org> writes:
>>>>>>>>
>>>>>>>> Hi Darrick,
>>>>>>>>
>>>>>>>> Thanks for your analysis and quick help on this.
>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Darrick,
>>>>>>>>>>
>>>>>>>>>> Please find the information collected from the system. We added some
>>>>>>>>>> debug logs and looks like it is exactly what is happening which you
>>>>>>>>>> pointed out.
>>>>>>>>>>
>>>>>>>>>> We added a debug kernel patch to get more info from the system which
>>>>>>>>>> you had requested [1]
>>>>>>>>>>
>>>>>>>>>> 1. We first breaked into emergency shell where root fs is first getting
>>>>>>>>>> mounted on /sysroot as "ro" filesystem. Here are the logs.
>>>>>>>>>>
>>>>>>>>>> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
>>>>>>>>>> Mounting /sysroot...
>>>>>>>>>> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
>>>>>>>>>> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
>>>>>>>>>> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
>>>>>>>>>> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
>>>>>>>>>> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
>>>>>>>>>> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
>>>>>>>>>> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
>>>>>>>>>> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
>>>>>>>>>> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
>>>>>>>>>> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
>>>>>>>>>> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
>>>>>>>>>> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
>>>>>>>>>> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
>>>>>>>>>> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
>>>>>>>>>> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
>>>>>>>>>> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
>>>>>>>>>> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
>>>>>>>>>> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
>>>>>>>>>>
>>>>>>>>>> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
>>>>>>>>>> the huge value.
>>>>>>>>>
>>>>>>>>> Ok, so log recovery finds 3064909 and clears it...
>>>>>>>>>
>>>>>>>>>> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
>>>>>>>>>> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
>>>>>>>>>
>>>>>>>>> <snip the rest of these...>
>>>>>>>>>
>>>>>>>>>> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
>>>>>>>>>> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
>>>>>>>>>> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
>>>>>>>>>> [ OK ] Mounted /sysroot.
>>>>>>>>>> [ OK ] Reached target Initrd Root File System.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2. Then these are the logs from xfs_repair -n /dev/dm-0
>>>>>>>>>> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
>>>>>>>>>> printed in above xlog_recover_iunlink_ag() function.
>>>>>>>>>>
>>>>>>>>>> switch_root:/# xfs_repair -n /dev/dm-0
>>>>>>>>>> Phase 1 - find and verify superblock...
>>>>>>>>>> Phase 2 - using internal log
>>>>>>>>>> - zero log...
>>>>>>>>>> - scan filesystem freespace and inode maps...
>>>>>>>>>> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
>>>>>>>>>
>>>>>>>>> ...yet here we find that 3064909 is still on the unlinked list?
>>>>>>>>>
>>>>>>>>> Just to confirm -- you ran xfs_repair -n after the successful recovery
>>>>>>>>> above, right?
>>>>>>>>>
>>>>>>>> Yes, that's right.
>>>>>>>>
>>>>>>>>>> - found root inode chunk
>>>>>>>>>> Phase 3 - for each AG...
>>>>>>>>>> - scan (but don't clear) agi unlinked lists...
>>>>>>>>>> - process known inodes and perform inode discovery...
>>>>>>>>>> - agno = 0
>>>>>>>>>> - agno = 1
>>>>>>>>>> - agno = 2
>>>>>>>>>> - agno = 3
>>>>>>>>>> - process newly discovered inodes...
>>>>>>>>>> Phase 4 - check for duplicate blocks...
>>>>>>>>>> - setting up duplicate extent list...
>>>>>>>>>> - check for inodes claiming duplicate blocks...
>>>>>>>>>> - agno = 0
>>>>>>>>>> - agno = 2
>>>>>>>>>> - agno = 1
>>>>>>>>>> - agno = 3
>>>>>>>>>> No modify flag set, skipping phase 5
>>>>>>>>>> Phase 6 - check inode connectivity...
>>>>>>>>>> - traversing filesystem ...
>>>>>>>>>> - traversal finished ...
>>>>>>>>>> - moving disconnected inodes to lost+found ...
>>>>>>>>>> Phase 7 - verify link counts...
>>>>>>>>>> would have reset inode 3064909 nlinks from 4294967291 to 2
>>>>>>>>>
>>>>>>>>> Oh now that's interesting. Inode on unlinked list with grossly nonzero
>>>>>>>>> (but probably underflowed) link count. That might explain why iunlink
>>>>>>>>> recovery ignores the inode. Is inode 3064909 reachable via the
>>>>>>>>> directory tree?
>>>>>>>>>
>>>>>>>>> Would you mind sending me a metadump to play with? metadump -ago would
>>>>>>>>> be best, if filenames/xattrnames aren't sensitive customer data.
>>>>>>>>
>>>>>>>> Sorry about the delay.
>>>>>>>> I am checking for any permissions part internally.
>>>>>>>> Meanwhile - I can help out if you would like me to try anything.
>>>>>>>
>>>>>>> Ok. I'll try creating a filesystem with a weirdly high refcount
>>>>>>> unlinked inode and I guess you can try it to see if you get the same
>>>>>>> symptoms. I've finished with my parent pointers work for the time
>>>>>>> being, so I might have some time tomorrow (after I kick the tires on
>>>>>>> SETFSUUID) to simulate this and see if I can adapt the AGI repair code
>>>>>>> to deal with this.
>>>>>>
>>>>>> If you uncompress and mdrestore the attached file to a blockdev, mount
>>>>>> it, and run some creat() exerciser, do you get the same symptoms? I've
>>>>>> figured out how to make online fsck deal with it. :)
>>>>>>
>>>>>> A possible solution for runtime would be to make it so that
>>>>>> xfs_iunlink_lookup could iget the inode if it's not in cache at all.
>>>>>>
>>>>>
>>>>> Hello Darrick,
>>>>>
>>>>> I did xfs_mdrestore the metadump you provided on a loop mounted
>>>>> blockdev. I ran fsstress on the root dir of the mounted filesystem,
>>>>> but I was unable to hit the issue.
>>>>>
>>>>> I tried the same with the original FS metadump as well and I am unable
>>>>> to hit the issue while running fsstress on the filesystem.
>>>>>
>>>>> I am thinking of identifying which file unlink operation was in progress
>>>>> when we see the issue during mounting. Maybe that will help in
>>>>> recreating the issue.
>>>>
>>>> Yeah, creating a bunch of O_TMPFILE files will exercise the unlinked
>>>> lists, possibly enough to trip over the affected agi bucket. See
>>>> t_open_tmpfiles.c in the fstests repo.
>>>
>>>
>>> Hello Darrick,
>>>
>>> Yes, I am tripping over the issue very easily when I run t_open_tmpfiles
>>> testcase for the metadump you shared. (Not hitting with the original dump
>>> though. Will try to fetch more information on whay is that).
>>>
>>> Here is the call stack with your metadump when we try to run
>>> t_open_tmpfiles test case.
>>> Its the same warning message which we were hitting too in the original
>>> case too.
>>>
>>> xfs_iunlink_lookup()
>>> <...>
>>> /*
>>> * Inode not in memory or in RCU freeing limbo should not happen.
>>> * Warn about this and let the caller handle the failure.
>>> */
>>> if (WARN_ON_ONCE(!ip || !ip->i_ino)) {
>>> rcu_read_unlock();
>>> return NULL;
>>> }
>>> <...>
>>>
>>> [43873.070585] xfs filesystem being mounted at /mnt1/scratch supports timestamps until 2038 (0x7fffffff)
>>> root@ubuntu:~# [43905.483065] ------------[ cut here ]------------
>>> [43905.485250] WARNING: CPU: 0 PID: 2379 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x14c/0x1e0
>>> [43905.488325] Modules linked in:
>>> [43905.489594] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Not tainted 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
>>> [43905.492828] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
>>> [43905.496604] RIP: 0010:xfs_iunlink_lookup+0x14c/0x1e0
>>> [43905.498341] Code: 0f 85 6e ff ff ff 48 c7 c2 a8 95 be 82 be 22 03 00 00 48 c7 c7 30 23 b7 82 c6 05 c8 71 84 01 01 e8 e9 d3 91 ff e9 6
>>> [43905.504324] RSP: 0018:ffffc9000405fb98 EFLAGS: 00010246
>>> [43905.506224] RAX: 0000000000000000 RBX: 0000000000001b43 RCX: 0000000000000000
>>> [43905.508624] RDX: ffff8891f1edf488 RSI: ffff8891f1edf4c8 RDI: 0000000000001b43
>>> [43905.511087] RBP: 0000000000001b43 R08: 0000000000000000 R09: ffff88931446ba80
>>> [43905.514465] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
>>> [43905.517947] R13: ffff889313f67840 R14: ffff8892c0155b00 R15: ffff8889dc9b2900
>>> [43905.521519] FS: 00007ffff7fb2740(0000) GS:ffff889dc7600000(0000) knlGS:0000000000000000
>>> [43905.525570] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>>> [43905.528402] CR2: 0000555555556060 CR3: 00000011b4790006 CR4: 0000000000170ef0
>>> [43905.532008] Call Trace:
>>> [43905.533399] <TASK>
>>> [43905.534473] xfs_iunlink_insert_inode+0x7a/0x100
>>> [43905.536663] xfs_iunlink+0xa4/0x190
>>> [43905.537962] xfs_create_tmpfile+0x277/0x2e0
>>> [43905.539654] xfs_generic_create+0x100/0x350
>>> [43905.541303] xfs_vn_tmpfile+0x1f/0x40
>>> [43905.542920] vfs_tmpfile+0x10e/0x1b0
>>> [43905.544307] path_openat+0x157/0x200
>>> [43905.545813] do_filp_open+0xad/0x150
>>> [43905.547213] ? alloc_fd+0x12d/0x220
>>> [43905.548646] ? alloc_fd+0x12d/0x220
>>> [43905.550014] ? lock_release+0x7f/0x130
>>> [43905.551435] ? do_raw_spin_unlock+0x4f/0xa0
>>> [43905.553045] ? _raw_spin_unlock+0x2d/0x50
>>> [43905.554554] ? alloc_fd+0x12d/0x220
>>> [43905.556264] do_sys_openat2+0x9b/0x160
>>> [43905.557680] __x64_sys_openat+0x58/0xa0
>>> [43905.559065] do_syscall_64+0x3f/0x90
>>> [43905.560589] entry_SYSCALL_64_after_hwframe+0x72/0xdc
>>> [43905.562377] RIP: 0033:0x7ffff7d0ca45
>>> [43905.563970] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
>>> [43905.570038] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
>>> [43905.572747] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
>>> [43905.575246] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
>>> [43905.577782] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
>>> [43905.580315] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
>>> [43905.582850] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
>>> [43905.585438] </TASK>
>>> [43905.586528] irq event stamp: 14045
>>> [43905.587828] hardirqs last enabled at (14055): [<ffffffff8121bc02>] __up_console_sem+0x52/0x60
>>> [43905.590861] hardirqs last disabled at (14066): [<ffffffff8121bbe7>] __up_console_sem+0x37/0x60
>>> [43905.593856] softirqs last enabled at (13920): [<ffffffff82231b5a>] __do_softirq+0x2ea/0x3e1
>>> [43905.596813] softirqs last disabled at (13909): [<ffffffff8119573f>] irq_exit_rcu+0xdf/0x140
>>> [43905.599766] ---[ end trace 0000000000000000 ]---
>>> [43905.601450] XFS (loop7): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_create_tmpfile+0x1c6/00
>>> [43905.606100] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Tainted: G W 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
>>> [43905.609797] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
>>> [43905.614562] Call Trace:
>>> [43905.616112] <TASK>
>>> [43905.617245] dump_stack_lvl+0x66/0x80
>>> [43905.619054] xfs_trans_cancel+0x138/0x1f0
>>> [43905.620898] xfs_create_tmpfile+0x1c6/0x2e0
>>> [43905.623140] xfs_generic_create+0x100/0x350
>>> [43905.625483] xfs_vn_tmpfile+0x1f/0x40
>>> [43905.627372] vfs_tmpfile+0x10e/0x1b0
>>> [43905.629413] path_openat+0x157/0x200
>>> [43905.631204] do_filp_open+0xad/0x150
>>> [43905.633050] ? alloc_fd+0x12d/0x220
>>> [43905.634844] ? alloc_fd+0x12d/0x220
>>> [43905.636602] ? lock_release+0x7f/0x130
>>> [43905.638479] ? do_raw_spin_unlock+0x4f/0xa0
>>> [43905.640726] ? _raw_spin_unlock+0x2d/0x50
>>> [43905.642916] ? alloc_fd+0x12d/0x220
>>> [43905.644375] do_sys_openat2+0x9b/0x160
>>> [43905.645763] __x64_sys_openat+0x58/0xa0
>>> [43905.647145] do_syscall_64+0x3f/0x90
>>> [43905.648685] entry_SYSCALL_64_after_hwframe+0x72/0xdc
>>> [43905.650430] RIP: 0033:0x7ffff7d0ca45
>>> [43905.651731] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
>>> [43905.657637] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
>>> [43905.660141] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
>>> [43905.662525] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
>>> [43905.665086] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
>>> [43905.667455] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
>>> [43905.669830] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
>>> [43905.672193] </TASK>
>>> [43905.689666] XFS (loop7): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x151/0x1f0 (fs/xfs/xfs_trans.c:1098). Shu.
>>> [43905.694215] XFS (loop7): Please unmount the filesystem and rectify the problem(s)
>>>
>>>
>>> -ritesh
>>>
>>>
>>>>
>>>> --D
>>>>
>>>>> Although the xfs_repair -n does show a similar log of unlinked inode
>>>>> with the metadump you provided.
>>>>>
>>>>> root@ubuntu:~# xfs_repair -n -o force_geometry /dev/loop7
>>>>> Phase 1 - find and verify superblock...
>>>>> Phase 2 - using internal log
>>>>> - zero log...
>>>>> - scan filesystem freespace and inode maps...
>>>>> agi unlinked bucket 3 is 6979 in ag 0 (inode=6979)
>>>>> agi unlinked bucket 4 is 6980 in ag 0 (inode=6980)
>>>>> - found root inode chunk
>>>>> Phase 3 - for each AG...
>>>>> - scan (but don't clear) agi unlinked lists...
>>>>> - process known inodes and perform inode discovery...
>>>>> - agno = 0
>>>>> - process newly discovered inodes...
>>>>> Phase 4 - check for duplicate blocks...
>>>>> - setting up duplicate extent list...
>>>>> - check for inodes claiming duplicate blocks...
>>>>> - agno = 0
>>>>> No modify flag set, skipping phase 5
>>>>> Phase 6 - check inode connectivity...
>>>>> - traversing filesystem ...
>>>>> - traversal finished ...
>>>>> - moving disconnected inodes to lost+found ...
>>>>> disconnected inode 6979, would move to lost+found
>>>>> disconnected inode 6980, would move to lost+found
>>>>> Phase 7 - verify link counts...
>>>>> would have reset inode 6979 nlinks from 5555 to 1
>>>>> would have reset inode 6980 nlinks from 0 to 1
>>>>> No modify flag set, skipping filesystem flush and exiting.
>>>>>
>>>>> Thanks again for the help. Once I have more info I will update the
>>>>> thread!
>>>>>
>>>>> -ritesh
>
>
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-06-05 13:27 ` Thorsten Leemhuis
@ 2023-06-05 21:57 ` Darrick J. Wong
2023-06-06 2:46 ` Dave Chinner
0 siblings, 1 reply; 28+ messages in thread
From: Darrick J. Wong @ 2023-06-05 21:57 UTC (permalink / raw)
To: Thorsten Leemhuis
Cc: Linux regressions mailing list, Ritesh Harjani (IBM),
shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On Mon, Jun 05, 2023 at 03:27:43PM +0200, Thorsten Leemhuis wrote:
> /me waves friendly
>
> On 18.04.23 06:56, Darrick J. Wong wrote:
> > On Mon, Apr 17, 2023 at 01:16:53PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> >> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> >> for once, to make this easily accessible to everyone.
> >>
> >> Has any progress been made to fix below regression? It doesn't look like
> >> it from here, hence I wondered if it fall through the cracks. Or is
> >> there some good reason why this is safe to ignore?
> >
> > Still working on thinking up a reasonable strategy to reload the incore
> > iunlink list if we trip over this. Online repair now knows how to do
> > this[1], but I haven't had time to figure out if this will work
> > generally. [...]
>
> I still have this issue on my list of tracked regressions, hence please
> allow me to ask: was there any progress to resolve this? Doesn't look
> like it, but from my point it's easy to miss something.
Yeah -- Dave put "xfs: collect errors from inodegc for unlinked inode
recovery" in for-next yesterday, and I posted a draft of online repair
for the unlinked lists that corrects most of the other problems that we
found in the process of digging into this problem:
https://lore.kernel.org/linux-xfs/168506068642.3738067.3524976114588613479.stgit@frogsfrogsfrogs/T/#m861e4b1259d9b16b9970e46dfcfdae004a5dd634
But that's looking at things from the ground up, which isn't terribly
insightful as to what's going on, as you've noted. :)
> BTW, in case this was not yet addressed: if you have a few seconds,
> could you please (just briefly!) explain why it seems to take quite a
> while to resolve this? A "not booting" regressions sounds like something
> that I'm pretty sure Linus normally wants to see addressed rather sooner
> than later. But that apparently is not the case here. I know that XFS
> devs normally take regressions seriously, hence I assume there are good
> reasons for it. But I'd like to roughly understand them (is this a
> extremely corner case issue others are unlike to run into or something
> like that?), as I don't want Linus on my back with questions like "why
> didn't you put more pressure on the XFS maintainers" or "you should have
> told me about this".
First things first -- Ritesh reported problems wherein a freshly mounted
filesystem would fail soon after because of some issue or other with the
unlinked inode list. He could reproduce this problem, but (AFAIK) he's
the only user who's actually reported this. It's not like *everyone*
with XFS cannot boot anymore, it's just this system. Given the sparsity
of any other reports with similar symptoms, I do not judge this to be
a hair-on-fire situation.
(Contrast this to the extent busy deadlock problem that Wengang Wang is
trying to solve, which (a) is hitting many customer systems and (b)
regularly. Criteria like (a) make things like that a higher severity
problem IMHO.)
So the first 'why' question to ask here is why did we fail? Ritesh
reported that the fs mounted cleanly, started a workload that unlinked
an inode, and then failed because the incore state wasn't what was
expected.
The second Q is why wasn't the incore state what we expected? The
reason for that is that XFS recently reworked the incore unlinked inode
data structures from a singly-linked per-AG inumber forward list and an
incore rhashtable reverse list into a doubly-linked list between
xfs_inode objects, but this new code requires that any unlinked inode
mentioned anywhere /must/ be active in memory and on the incore list.
The third Q is why are there (ondisk) unlinked inodes that are not
represented incore? Aside from processing unlinked lists at the end of
dirty log recovery, XFS doesn't have a means to reload the incore list.
The kernel driver has assumed for decades that the iunlink processing
happens iff the log was dirty -- if everything is working, then unlinked
inodes always come off the list, either before clean unmount, or during
log recovery if unclean unmount.
The fourth Q is why was that assumption violated? Dave worked out
(after some thought) that it is possible for a partially corrupt inode
to end up on the iunlink list. At some point background inode gc will
try to clear it and bail out early due to the partial corruption. If
that case, the inode stays on the iunlink list even after the incore
inode is reclaimed. If the filesystem unmounts cleanly, the conditions
are now ripe for "clean mount with unreclaimed ghost unlinked inodes".
The fifth Q is why didn't anyone notice? The inode inactivation code
(aka xfs_inactive*) seems to drop errno returns, probably because the
upper level functions are background threads and hence cannot return
failures to any userspace program. This is sloppy legacy code, which
means we need to be even more careful cleaning it up.
Five questions is plenty deep, now we have a /lot/ of things to think
about.
Dave's patch addresses #5 by plumbing error returns up the stack so that
frontend processes that push the background gc threads can receive
errors and throw them out to userspace. I suspect that we ought to go
further and xfs_force_shutdown() any time the inode gc hits an error,
which (I think) addresses #4.
#2 and #3 are harder to address, because the incore state is not what we
expect. The solution sounds pretty simple -- reload the incore state
fully as needed. However, there are subtleties here -- since the
structure is a linked list, is it necessary to reload the entire chain
to ensure correct operation, or can we do it as needed to avoid tripping
over null (incore) pointers? How many ghost iunlinked inodes are there,
even? One? One thousand? One million?
So I built a new xfs_db command to simulate this exact situation -- take
a clean filesystem, allocate some inodes, and dump them all on the
unlinked list. Apologies, I thought I'd sent that to the list, but
apparently I have not. That code is here:
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfsprogs-dev.git/commit/?h=djwong-wtf&id=b4ce8b839834357ac791490ea1691e176630a452
With a simulator, I can assess different approaches to fixing the
problem, and add some functional tests for online repair.
It's not clear if we really /can/ fully restore the incore iunlink list
with runtime code. At the point where a transaction needs to deal with
the iunlink list to add (or remove) inode X, we've already locked all
the resources we thought we needed for X. If we start loading inodes
X-1 and X+1 to fix the list, we developers now have to remember *that*
possibility when reviewing runtime code changes.
Remember I said I could simulate one million iunlinked inodes? If we
load a lot of inodes, then memory pressure becomes a real problem here.
If memory pressure leads to reclaim and the thread dealing with X is
already part of a reclaim process (or something else waiting for
reclaim) now we have a deadlock vector, which must be avoided. XFS
(like all the other Linux filesystems except bcachefs) cannot back out
of a transaction; xfs_trans_cancel will lead to immediate shutdown.
One could only fix up (say) the nearest neighbors, but now we have to
sprinkle the list reconstruction code all over the iunlink processing.
IOWs, this turns into a nasty game of whackamole, when there's a better
solution to be had.
Online repair is better positioned to deal with these scenarios because
it can break up the repair work into small discrete units, and grab all
the resources it needs prior to starting one of the discrete units.
True, that requires someone to run xfs_scrub, but so it goes...
The problem with putting this in online repair is that Dave (AFAIK)
feels very strongly that every bug report needs to be triaged
immediately, and that takes priority over reviewing new code such as
online repair. That's the right thing to do, but every time someone
sends in some automated fuzzer report, it slows down online repair
review. This is why I'm burned out and cranky as hell about script
kiddies dumping zerodays on the list and doing no work to help us fix
the problems.
--D
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
>
> #regzbot poke
>
> >> On 20.03.23 06:20, Ritesh Harjani (IBM) wrote:
> >>> "Darrick J. Wong" <djwong@kernel.org> writes:
> >>>
> >>>> On Sat, Mar 18, 2023 at 10:20:28PM +0530, Ritesh Harjani wrote:
> >>>>> "Darrick J. Wong" <djwong@kernel.org> writes:
> >>>>>
> >>>>>> On Wed, Mar 15, 2023 at 10:20:37PM -0700, Darrick J. Wong wrote:
> >>>>>>> On Thu, Mar 16, 2023 at 10:16:02AM +0530, Ritesh Harjani wrote:
> >>>>>>>> "Darrick J. Wong" <djwong@kernel.org> writes:
> >>>>>>>>
> >>>>>>>> Hi Darrick,
> >>>>>>>>
> >>>>>>>> Thanks for your analysis and quick help on this.
> >>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Hi Darrick,
> >>>>>>>>>>
> >>>>>>>>>> Please find the information collected from the system. We added some
> >>>>>>>>>> debug logs and looks like it is exactly what is happening which you
> >>>>>>>>>> pointed out.
> >>>>>>>>>>
> >>>>>>>>>> We added a debug kernel patch to get more info from the system which
> >>>>>>>>>> you had requested [1]
> >>>>>>>>>>
> >>>>>>>>>> 1. We first breaked into emergency shell where root fs is first getting
> >>>>>>>>>> mounted on /sysroot as "ro" filesystem. Here are the logs.
> >>>>>>>>>>
> >>>>>>>>>> [ OK ] Started File System Check on /dev/mapper/rhel_ltcden3--lp1-root.
> >>>>>>>>>> Mounting /sysroot...
> >>>>>>>>>> [ 7.203990] SGI XFS with ACLs, security attributes, quota, no debug enabled
> >>>>>>>>>> [ 7.205835] XFS (dm-0): Mounting V5 Filesystem 7b801289-75a7-4d39-8cd3-24526e9e9da7
> >>>>>>>>>> [ ***] A start job is running for /sysroot (15s / 1min 35s)[ 17.439377] XFS (dm-0): Starting recovery (logdev: internal)
> >>>>>>>>>> [ *** ] A start job is running for /sysroot (16s / 1min 35s)[ 17.771158] xfs_log_mount_finish: Recovery needed is set
> >>>>>>>>>> [ 17.771172] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:0
> >>>>>>>>>> [ 17.771179] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:1
> >>>>>>>>>> [ 17.771184] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:2
> >>>>>>>>>> [ 17.771190] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:3
> >>>>>>>>>> [ 17.771196] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:4
> >>>>>>>>>> [ 17.771201] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:5
> >>>>>>>>>> [ 17.801033] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:6
> >>>>>>>>>> [ 17.801041] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:7
> >>>>>>>>>> [ 17.801046] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:8
> >>>>>>>>>> [ 17.801052] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:9
> >>>>>>>>>> [ 17.801057] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:10
> >>>>>>>>>> [ 17.801063] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:11
> >>>>>>>>>> [ 17.801068] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:12
> >>>>>>>>>> [ 17.801272] xlog_recover_iunlink_bucket: bucket: 13, agino: 3064909, ino: 3064909, iget ret: 0, previno:18446744073709551615, prev_agino:4294967295
> >>>>>>>>>>
> >>>>>>>>>> <previno, prev_agino> is just <-1 %ull and -1 %u> in above. That's why
> >>>>>>>>>> the huge value.
> >>>>>>>>>
> >>>>>>>>> Ok, so log recovery finds 3064909 and clears it...
> >>>>>>>>>
> >>>>>>>>>> [ 17.801281] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:13
> >>>>>>>>>> [ 17.801287] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:0, bucket:14
> >>>>>>>>>
> >>>>>>>>> <snip the rest of these...>
> >>>>>>>>>
> >>>>>>>>>> [ 17.844910] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:62
> >>>>>>>>>> [ 17.844916] xlog_recover_iunlink_ag: ran xlog_recover_iunlink_bucket for agi:3, bucket:63
> >>>>>>>>>> [ 17.886079] XFS (dm-0): Ending recovery (logdev: internal)
> >>>>>>>>>> [ OK ] Mounted /sysroot.
> >>>>>>>>>> [ OK ] Reached target Initrd Root File System.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> 2. Then these are the logs from xfs_repair -n /dev/dm-0
> >>>>>>>>>> Here you will notice the same agi 3064909 in bucket 13 (from phase-2) which got also
> >>>>>>>>>> printed in above xlog_recover_iunlink_ag() function.
> >>>>>>>>>>
> >>>>>>>>>> switch_root:/# xfs_repair -n /dev/dm-0
> >>>>>>>>>> Phase 1 - find and verify superblock...
> >>>>>>>>>> Phase 2 - using internal log
> >>>>>>>>>> - zero log...
> >>>>>>>>>> - scan filesystem freespace and inode maps...
> >>>>>>>>>> agi unlinked bucket 13 is 3064909 in ag 0 (inode=3064909)
> >>>>>>>>>
> >>>>>>>>> ...yet here we find that 3064909 is still on the unlinked list?
> >>>>>>>>>
> >>>>>>>>> Just to confirm -- you ran xfs_repair -n after the successful recovery
> >>>>>>>>> above, right?
> >>>>>>>>>
> >>>>>>>> Yes, that's right.
> >>>>>>>>
> >>>>>>>>>> - found root inode chunk
> >>>>>>>>>> Phase 3 - for each AG...
> >>>>>>>>>> - scan (but don't clear) agi unlinked lists...
> >>>>>>>>>> - process known inodes and perform inode discovery...
> >>>>>>>>>> - agno = 0
> >>>>>>>>>> - agno = 1
> >>>>>>>>>> - agno = 2
> >>>>>>>>>> - agno = 3
> >>>>>>>>>> - process newly discovered inodes...
> >>>>>>>>>> Phase 4 - check for duplicate blocks...
> >>>>>>>>>> - setting up duplicate extent list...
> >>>>>>>>>> - check for inodes claiming duplicate blocks...
> >>>>>>>>>> - agno = 0
> >>>>>>>>>> - agno = 2
> >>>>>>>>>> - agno = 1
> >>>>>>>>>> - agno = 3
> >>>>>>>>>> No modify flag set, skipping phase 5
> >>>>>>>>>> Phase 6 - check inode connectivity...
> >>>>>>>>>> - traversing filesystem ...
> >>>>>>>>>> - traversal finished ...
> >>>>>>>>>> - moving disconnected inodes to lost+found ...
> >>>>>>>>>> Phase 7 - verify link counts...
> >>>>>>>>>> would have reset inode 3064909 nlinks from 4294967291 to 2
> >>>>>>>>>
> >>>>>>>>> Oh now that's interesting. Inode on unlinked list with grossly nonzero
> >>>>>>>>> (but probably underflowed) link count. That might explain why iunlink
> >>>>>>>>> recovery ignores the inode. Is inode 3064909 reachable via the
> >>>>>>>>> directory tree?
> >>>>>>>>>
> >>>>>>>>> Would you mind sending me a metadump to play with? metadump -ago would
> >>>>>>>>> be best, if filenames/xattrnames aren't sensitive customer data.
> >>>>>>>>
> >>>>>>>> Sorry about the delay.
> >>>>>>>> I am checking for any permissions part internally.
> >>>>>>>> Meanwhile - I can help out if you would like me to try anything.
> >>>>>>>
> >>>>>>> Ok. I'll try creating a filesystem with a weirdly high refcount
> >>>>>>> unlinked inode and I guess you can try it to see if you get the same
> >>>>>>> symptoms. I've finished with my parent pointers work for the time
> >>>>>>> being, so I might have some time tomorrow (after I kick the tires on
> >>>>>>> SETFSUUID) to simulate this and see if I can adapt the AGI repair code
> >>>>>>> to deal with this.
> >>>>>>
> >>>>>> If you uncompress and mdrestore the attached file to a blockdev, mount
> >>>>>> it, and run some creat() exerciser, do you get the same symptoms? I've
> >>>>>> figured out how to make online fsck deal with it. :)
> >>>>>>
> >>>>>> A possible solution for runtime would be to make it so that
> >>>>>> xfs_iunlink_lookup could iget the inode if it's not in cache at all.
> >>>>>>
> >>>>>
> >>>>> Hello Darrick,
> >>>>>
> >>>>> I did xfs_mdrestore the metadump you provided on a loop mounted
> >>>>> blockdev. I ran fsstress on the root dir of the mounted filesystem,
> >>>>> but I was unable to hit the issue.
> >>>>>
> >>>>> I tried the same with the original FS metadump as well and I am unable
> >>>>> to hit the issue while running fsstress on the filesystem.
> >>>>>
> >>>>> I am thinking of identifying which file unlink operation was in progress
> >>>>> when we see the issue during mounting. Maybe that will help in
> >>>>> recreating the issue.
> >>>>
> >>>> Yeah, creating a bunch of O_TMPFILE files will exercise the unlinked
> >>>> lists, possibly enough to trip over the affected agi bucket. See
> >>>> t_open_tmpfiles.c in the fstests repo.
> >>>
> >>>
> >>> Hello Darrick,
> >>>
> >>> Yes, I am tripping over the issue very easily when I run t_open_tmpfiles
> >>> testcase for the metadump you shared. (Not hitting with the original dump
> >>> though. Will try to fetch more information on whay is that).
> >>>
> >>> Here is the call stack with your metadump when we try to run
> >>> t_open_tmpfiles test case.
> >>> Its the same warning message which we were hitting too in the original
> >>> case too.
> >>>
> >>> xfs_iunlink_lookup()
> >>> <...>
> >>> /*
> >>> * Inode not in memory or in RCU freeing limbo should not happen.
> >>> * Warn about this and let the caller handle the failure.
> >>> */
> >>> if (WARN_ON_ONCE(!ip || !ip->i_ino)) {
> >>> rcu_read_unlock();
> >>> return NULL;
> >>> }
> >>> <...>
> >>>
> >>> [43873.070585] xfs filesystem being mounted at /mnt1/scratch supports timestamps until 2038 (0x7fffffff)
> >>> root@ubuntu:~# [43905.483065] ------------[ cut here ]------------
> >>> [43905.485250] WARNING: CPU: 0 PID: 2379 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x14c/0x1e0
> >>> [43905.488325] Modules linked in:
> >>> [43905.489594] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Not tainted 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
> >>> [43905.492828] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
> >>> [43905.496604] RIP: 0010:xfs_iunlink_lookup+0x14c/0x1e0
> >>> [43905.498341] Code: 0f 85 6e ff ff ff 48 c7 c2 a8 95 be 82 be 22 03 00 00 48 c7 c7 30 23 b7 82 c6 05 c8 71 84 01 01 e8 e9 d3 91 ff e9 6
> >>> [43905.504324] RSP: 0018:ffffc9000405fb98 EFLAGS: 00010246
> >>> [43905.506224] RAX: 0000000000000000 RBX: 0000000000001b43 RCX: 0000000000000000
> >>> [43905.508624] RDX: ffff8891f1edf488 RSI: ffff8891f1edf4c8 RDI: 0000000000001b43
> >>> [43905.511087] RBP: 0000000000001b43 R08: 0000000000000000 R09: ffff88931446ba80
> >>> [43905.514465] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
> >>> [43905.517947] R13: ffff889313f67840 R14: ffff8892c0155b00 R15: ffff8889dc9b2900
> >>> [43905.521519] FS: 00007ffff7fb2740(0000) GS:ffff889dc7600000(0000) knlGS:0000000000000000
> >>> [43905.525570] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> >>> [43905.528402] CR2: 0000555555556060 CR3: 00000011b4790006 CR4: 0000000000170ef0
> >>> [43905.532008] Call Trace:
> >>> [43905.533399] <TASK>
> >>> [43905.534473] xfs_iunlink_insert_inode+0x7a/0x100
> >>> [43905.536663] xfs_iunlink+0xa4/0x190
> >>> [43905.537962] xfs_create_tmpfile+0x277/0x2e0
> >>> [43905.539654] xfs_generic_create+0x100/0x350
> >>> [43905.541303] xfs_vn_tmpfile+0x1f/0x40
> >>> [43905.542920] vfs_tmpfile+0x10e/0x1b0
> >>> [43905.544307] path_openat+0x157/0x200
> >>> [43905.545813] do_filp_open+0xad/0x150
> >>> [43905.547213] ? alloc_fd+0x12d/0x220
> >>> [43905.548646] ? alloc_fd+0x12d/0x220
> >>> [43905.550014] ? lock_release+0x7f/0x130
> >>> [43905.551435] ? do_raw_spin_unlock+0x4f/0xa0
> >>> [43905.553045] ? _raw_spin_unlock+0x2d/0x50
> >>> [43905.554554] ? alloc_fd+0x12d/0x220
> >>> [43905.556264] do_sys_openat2+0x9b/0x160
> >>> [43905.557680] __x64_sys_openat+0x58/0xa0
> >>> [43905.559065] do_syscall_64+0x3f/0x90
> >>> [43905.560589] entry_SYSCALL_64_after_hwframe+0x72/0xdc
> >>> [43905.562377] RIP: 0033:0x7ffff7d0ca45
> >>> [43905.563970] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
> >>> [43905.570038] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
> >>> [43905.572747] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
> >>> [43905.575246] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
> >>> [43905.577782] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
> >>> [43905.580315] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
> >>> [43905.582850] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
> >>> [43905.585438] </TASK>
> >>> [43905.586528] irq event stamp: 14045
> >>> [43905.587828] hardirqs last enabled at (14055): [<ffffffff8121bc02>] __up_console_sem+0x52/0x60
> >>> [43905.590861] hardirqs last disabled at (14066): [<ffffffff8121bbe7>] __up_console_sem+0x37/0x60
> >>> [43905.593856] softirqs last enabled at (13920): [<ffffffff82231b5a>] __do_softirq+0x2ea/0x3e1
> >>> [43905.596813] softirqs last disabled at (13909): [<ffffffff8119573f>] irq_exit_rcu+0xdf/0x140
> >>> [43905.599766] ---[ end trace 0000000000000000 ]---
> >>> [43905.601450] XFS (loop7): Internal error xfs_trans_cancel at line 1097 of file fs/xfs/xfs_trans.c. Caller xfs_create_tmpfile+0x1c6/00
> >>> [43905.606100] CPU: 0 PID: 2379 Comm: t_open_tmpfiles Tainted: G W 6.3.0-rc2-xfstests-00051-gc1940a43e595 #57
> >>> [43905.609797] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
> >>> [43905.614562] Call Trace:
> >>> [43905.616112] <TASK>
> >>> [43905.617245] dump_stack_lvl+0x66/0x80
> >>> [43905.619054] xfs_trans_cancel+0x138/0x1f0
> >>> [43905.620898] xfs_create_tmpfile+0x1c6/0x2e0
> >>> [43905.623140] xfs_generic_create+0x100/0x350
> >>> [43905.625483] xfs_vn_tmpfile+0x1f/0x40
> >>> [43905.627372] vfs_tmpfile+0x10e/0x1b0
> >>> [43905.629413] path_openat+0x157/0x200
> >>> [43905.631204] do_filp_open+0xad/0x150
> >>> [43905.633050] ? alloc_fd+0x12d/0x220
> >>> [43905.634844] ? alloc_fd+0x12d/0x220
> >>> [43905.636602] ? lock_release+0x7f/0x130
> >>> [43905.638479] ? do_raw_spin_unlock+0x4f/0xa0
> >>> [43905.640726] ? _raw_spin_unlock+0x2d/0x50
> >>> [43905.642916] ? alloc_fd+0x12d/0x220
> >>> [43905.644375] do_sys_openat2+0x9b/0x160
> >>> [43905.645763] __x64_sys_openat+0x58/0xa0
> >>> [43905.647145] do_syscall_64+0x3f/0x90
> >>> [43905.648685] entry_SYSCALL_64_after_hwframe+0x72/0xdc
> >>> [43905.650430] RIP: 0033:0x7ffff7d0ca45
> >>> [43905.651731] Code: 75 53 89 f0 25 00 00 41 00 3d 00 00 41 00 74 45 80 3d a6 1b 0f 00 00 74 69 89 da 48 89 ee bf 9c ff ff ff b8 01 01 5
> >>> [43905.657637] RSP: 002b:00007fffffffe2c0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
> >>> [43905.660141] RAX: ffffffffffffffda RBX: 0000000000410002 RCX: 00007ffff7d0ca45
> >>> [43905.662525] RDX: 0000000000410002 RSI: 0000555555556057 RDI: 00000000ffffff9c
> >>> [43905.665086] RBP: 0000555555556057 R08: 000000000000ab7f R09: 00007ffff7fc1080
> >>> [43905.667455] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000000
> >>> [43905.669830] R13: 00007fffffffe4a0 R14: 0000555555557d68 R15: 00007ffff7ffd020
> >>> [43905.672193] </TASK>
> >>> [43905.689666] XFS (loop7): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x151/0x1f0 (fs/xfs/xfs_trans.c:1098). Shu.
> >>> [43905.694215] XFS (loop7): Please unmount the filesystem and rectify the problem(s)
> >>>
> >>>
> >>> -ritesh
> >>>
> >>>
> >>>>
> >>>> --D
> >>>>
> >>>>> Although the xfs_repair -n does show a similar log of unlinked inode
> >>>>> with the metadump you provided.
> >>>>>
> >>>>> root@ubuntu:~# xfs_repair -n -o force_geometry /dev/loop7
> >>>>> Phase 1 - find and verify superblock...
> >>>>> Phase 2 - using internal log
> >>>>> - zero log...
> >>>>> - scan filesystem freespace and inode maps...
> >>>>> agi unlinked bucket 3 is 6979 in ag 0 (inode=6979)
> >>>>> agi unlinked bucket 4 is 6980 in ag 0 (inode=6980)
> >>>>> - found root inode chunk
> >>>>> Phase 3 - for each AG...
> >>>>> - scan (but don't clear) agi unlinked lists...
> >>>>> - process known inodes and perform inode discovery...
> >>>>> - agno = 0
> >>>>> - process newly discovered inodes...
> >>>>> Phase 4 - check for duplicate blocks...
> >>>>> - setting up duplicate extent list...
> >>>>> - check for inodes claiming duplicate blocks...
> >>>>> - agno = 0
> >>>>> No modify flag set, skipping phase 5
> >>>>> Phase 6 - check inode connectivity...
> >>>>> - traversing filesystem ...
> >>>>> - traversal finished ...
> >>>>> - moving disconnected inodes to lost+found ...
> >>>>> disconnected inode 6979, would move to lost+found
> >>>>> disconnected inode 6980, would move to lost+found
> >>>>> Phase 7 - verify link counts...
> >>>>> would have reset inode 6979 nlinks from 5555 to 1
> >>>>> would have reset inode 6980 nlinks from 0 to 1
> >>>>> No modify flag set, skipping filesystem flush and exiting.
> >>>>>
> >>>>> Thanks again for the help. Once I have more info I will update the
> >>>>> thread!
> >>>>>
> >>>>> -ritesh
> >
> >
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-06-05 21:57 ` Darrick J. Wong
@ 2023-06-06 2:46 ` Dave Chinner
2023-06-06 3:22 ` Darrick J. Wong
2023-06-06 11:23 ` Thorsten Leemhuis
0 siblings, 2 replies; 28+ messages in thread
From: Dave Chinner @ 2023-06-06 2:46 UTC (permalink / raw)
To: Darrick J. Wong
Cc: Thorsten Leemhuis, Linux regressions mailing list,
Ritesh Harjani (IBM),
shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On Mon, Jun 05, 2023 at 02:57:45PM -0700, Darrick J. Wong wrote:
> On Mon, Jun 05, 2023 at 03:27:43PM +0200, Thorsten Leemhuis wrote:
> > /me waves friendly
> >
> > On 18.04.23 06:56, Darrick J. Wong wrote:
> > > On Mon, Apr 17, 2023 at 01:16:53PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> > >> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> > >> for once, to make this easily accessible to everyone.
> > >>
> > >> Has any progress been made to fix below regression? It doesn't look like
> > >> it from here, hence I wondered if it fall through the cracks. Or is
> > >> there some good reason why this is safe to ignore?
> > >
> > > Still working on thinking up a reasonable strategy to reload the incore
> > > iunlink list if we trip over this. Online repair now knows how to do
> > > this[1], but I haven't had time to figure out if this will work
> > > generally. [...]
> >
> > I still have this issue on my list of tracked regressions, hence please
> > allow me to ask: was there any progress to resolve this? Doesn't look
> > like it, but from my point it's easy to miss something.
>
> Yeah -- Dave put "xfs: collect errors from inodegc for unlinked inode
> recovery" in for-next yesterday, and I posted a draft of online repair
> for the unlinked lists that corrects most of the other problems that we
> found in the process of digging into this problem:
> https://lore.kernel.org/linux-xfs/168506068642.3738067.3524976114588613479.stgit@frogsfrogsfrogs/T/#m861e4b1259d9b16b9970e46dfcfdae004a5dd634
>
> But that's looking at things from the ground up, which isn't terribly
> insightful as to what's going on, as you've noted. :)
>
> > BTW, in case this was not yet addressed: if you have a few seconds,
> > could you please (just briefly!) explain why it seems to take quite a
> > while to resolve this? A "not booting" regressions sounds like something
> > that I'm pretty sure Linus normally wants to see addressed rather sooner
> > than later. But that apparently is not the case here. I know that XFS
> > devs normally take regressions seriously, hence I assume there are good
> > reasons for it. But I'd like to roughly understand them (is this a
> > extremely corner case issue others are unlike to run into or something
> > like that?), as I don't want Linus on my back with questions like "why
> > didn't you put more pressure on the XFS maintainers" or "you should have
> > told me about this".
>
> First things first -- Ritesh reported problems wherein a freshly mounted
> filesystem would fail soon after because of some issue or other with the
> unlinked inode list. He could reproduce this problem, but (AFAIK) he's
> the only user who's actually reported this. It's not like *everyone*
> with XFS cannot boot anymore, it's just this system. Given the sparsity
> of any other reports with similar symptoms, I do not judge this to be
> a hair-on-fire situation.
>
> (Contrast this to the extent busy deadlock problem that Wengang Wang is
> trying to solve, which (a) is hitting many customer systems and (b)
> regularly. Criteria like (a) make things like that a higher severity
> problem IMHO.)
Contrast this to the regression from 6.3-rc1 that caused actual user
data loss and filesystem corruption after 6.3 was released.
https://bugzilla.redhat.com/show_bug.cgi?id=2208553
That's so much more important than any problem seen in a test
environment it's not funny.
We'd already fixed this regression that caused it in 6.4-rc1 - the
original bug report (a livelock in data writeback) happened 2 days
before 6.3 released. It took me 3 days from report to having a fix
out for review (remember that timeframe).
At the time we didn't recognise the wider corruption risk the
failure we found exposed us to, so we didn't push it to stable
immediately. Hence when users started tripping over corruption and I
triaged it down to misdirected data write from -somewhere-. Eric
then found a reproducer and bisected to a range of XFS changes, and
I then realised what the problem was....
Stuff like this takes days of effort and multiple people to get to
the bottom of, and -everything else- gets ignored while we work
through the corruption problem.
Thorsten, I'm betting that you didn't even know about this
regression - it's been reported, tracked, triaged and fixed
completely outside the scope and visibility of the "kernel
regression tracker". Which clearly shows that we don't actually need
some special kernel regression tracker infrastructure to do our jobs
properly, nor do we need a nanny to make sure we actually are
prioritising things correctly....
....
> Dave's patch addresses #5 by plumbing error returns up the stack so that
> frontend processes that push the background gc threads can receive
> errors and throw them out to userspace.
Right, the inodegc regression fix simply restored the previous
status quo. Nothing more, nothing less, exactly what we want
regression fixes to do. But it took some time for me to get to
because there were much higher priority events occurring....
....
> The problem with putting this in online repair is that Dave (AFAIK)
> feels very strongly that every bug report needs to be triaged
> immediately, and that takes priority over reviewing new code such as
> online repair.
My rationale is that we can ignore it once we know the scope of the
issue, but until we know that information the risk of being
unprepared for sudden escalation is rather high and that's even
worse for stress and burnout levels.
The fedora corruption bug I mention above is a canonical example of
why triaging bug reports immediately is important - the original bug
report was clearly somethign that needed to be fixed straight away,
regardless of the fact we didn't know it could cause misdirected
writes at the time.
Once we got far enough into the fedora bug report triage, I simply
pointed the distro at the commit for them to test, and they did
everything else. Once confirmation that it fixed the problem came
in, I sent it immediately to the stable kernel maintainers.
IOWs, if I had not paid attention to the original bug report, it
would have taken me several more days to find the problem and fix it
(remember it took me ~3 days from report to fix originally). Users
would have been exposed to the corruption bug for much longer than
they were, and that doesn't make a bad situation any better.
And don't get me started on syzkaller and "security researchers"
raising inappropriate CVEs....
So, yeah, immediate triage is pretty much required at this point for
all bug reports because the downstream impacts of ignoring them is
only causing more stress and burnout risk for lots more people. The
number of downstream people pulled into (and still dealing with the
fallout of) that recent, completely unnecessary CVE fire drill was
just ... crazy.
We can choose to ignore triaged bug reports if they aren't important
enough to deal with immediately (like this unlinked inode list
issue), but we can make the decision (and justify it) based on the
knowledge we have rather instead of claiming ignorance. We're
supposed to be professional engineers, yes?
> That's the right thing to do, but every time someone
> sends in some automated fuzzer report, it slows down online repair
> review. This is why I'm burned out and cranky as hell about script
> kiddies dumping zerodays on the list and doing no work to help us fix
> the problems.
Reality sucks, and I hate it too. We get handed all the shit
sandwiches and everyone seems to expect that we will simply to eat
them up without complaining. But it's not like we didn't expect it -
upstream Linux development has always been a great big shit sandwich
and it's not going to be changing any time soon....
-Dave.
--
Dave Chinner
david@fromorbit.com
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-06-06 2:46 ` Dave Chinner
@ 2023-06-06 3:22 ` Darrick J. Wong
2023-06-06 11:23 ` Thorsten Leemhuis
1 sibling, 0 replies; 28+ messages in thread
From: Darrick J. Wong @ 2023-06-06 3:22 UTC (permalink / raw)
To: Dave Chinner
Cc: Thorsten Leemhuis, Linux regressions mailing list,
Ritesh Harjani (IBM),
shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On Tue, Jun 06, 2023 at 12:46:15PM +1000, Dave Chinner wrote:
> On Mon, Jun 05, 2023 at 02:57:45PM -0700, Darrick J. Wong wrote:
> > On Mon, Jun 05, 2023 at 03:27:43PM +0200, Thorsten Leemhuis wrote:
> > > /me waves friendly
> > >
> > > On 18.04.23 06:56, Darrick J. Wong wrote:
> > > > On Mon, Apr 17, 2023 at 01:16:53PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> > > >> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> > > >> for once, to make this easily accessible to everyone.
> > > >>
> > > >> Has any progress been made to fix below regression? It doesn't look like
> > > >> it from here, hence I wondered if it fall through the cracks. Or is
> > > >> there some good reason why this is safe to ignore?
> > > >
> > > > Still working on thinking up a reasonable strategy to reload the incore
> > > > iunlink list if we trip over this. Online repair now knows how to do
> > > > this[1], but I haven't had time to figure out if this will work
> > > > generally. [...]
> > >
> > > I still have this issue on my list of tracked regressions, hence please
> > > allow me to ask: was there any progress to resolve this? Doesn't look
> > > like it, but from my point it's easy to miss something.
> >
> > Yeah -- Dave put "xfs: collect errors from inodegc for unlinked inode
> > recovery" in for-next yesterday, and I posted a draft of online repair
> > for the unlinked lists that corrects most of the other problems that we
> > found in the process of digging into this problem:
> > https://lore.kernel.org/linux-xfs/168506068642.3738067.3524976114588613479.stgit@frogsfrogsfrogs/T/#m861e4b1259d9b16b9970e46dfcfdae004a5dd634
> >
> > But that's looking at things from the ground up, which isn't terribly
> > insightful as to what's going on, as you've noted. :)
> >
> > > BTW, in case this was not yet addressed: if you have a few seconds,
> > > could you please (just briefly!) explain why it seems to take quite a
> > > while to resolve this? A "not booting" regressions sounds like something
> > > that I'm pretty sure Linus normally wants to see addressed rather sooner
> > > than later. But that apparently is not the case here. I know that XFS
> > > devs normally take regressions seriously, hence I assume there are good
> > > reasons for it. But I'd like to roughly understand them (is this a
> > > extremely corner case issue others are unlike to run into or something
> > > like that?), as I don't want Linus on my back with questions like "why
> > > didn't you put more pressure on the XFS maintainers" or "you should have
> > > told me about this".
> >
> > First things first -- Ritesh reported problems wherein a freshly mounted
> > filesystem would fail soon after because of some issue or other with the
> > unlinked inode list. He could reproduce this problem, but (AFAIK) he's
> > the only user who's actually reported this. It's not like *everyone*
> > with XFS cannot boot anymore, it's just this system. Given the sparsity
> > of any other reports with similar symptoms, I do not judge this to be
> > a hair-on-fire situation.
> >
> > (Contrast this to the extent busy deadlock problem that Wengang Wang is
> > trying to solve, which (a) is hitting many customer systems and (b)
> > regularly. Criteria like (a) make things like that a higher severity
> > problem IMHO.)
>
> Contrast this to the regression from 6.3-rc1 that caused actual user
> data loss and filesystem corruption after 6.3 was released.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2208553
>
> That's so much more important than any problem seen in a test
> environment it's not funny.
Oh yeah, I'd forgotten about that one, probably because I was out on
vacation for nearly all of that.
Thank you Dave & Eric for fixing this quickly.
> We'd already fixed this regression that caused it in 6.4-rc1 - the
> original bug report (a livelock in data writeback) happened 2 days
> before 6.3 released. It took me 3 days from report to having a fix
> out for review (remember that timeframe).
>
> At the time we didn't recognise the wider corruption risk the
> failure we found exposed us to, so we didn't push it to stable
> immediately. Hence when users started tripping over corruption and I
> triaged it down to misdirected data write from -somewhere-. Eric
> then found a reproducer and bisected to a range of XFS changes, and
> I then realised what the problem was....
>
> Stuff like this takes days of effort and multiple people to get to
> the bottom of, and -everything else- gets ignored while we work
> through the corruption problem.
>
> Thorsten, I'm betting that you didn't even know about this
> regression - it's been reported, tracked, triaged and fixed
> completely outside the scope and visibility of the "kernel
> regression tracker". Which clearly shows that we don't actually need
> some special kernel regression tracker infrastructure to do our jobs
> properly, nor do we need a nanny to make sure we actually are
> prioritising things correctly....
I mostly disagree -- nag emails are a bit annoying when I'm under
stress, yes, but OTOH I would not (and am not) saying no to another set
of eyes who some day might see something we don't see, and nudge us.
Like you did here. Or someday you might be the first to spot (say) some
cross-fs problem that isn't so obvious to the rest of us who are
concentrating on a single subsys/fs/whatever.
You can choose not to nag Dave, but please keep sending me stuff. :)
I'd rather have you write something and say no than have you not write
something and then we never hear about it.
> ....
>
> > Dave's patch addresses #5 by plumbing error returns up the stack so that
> > frontend processes that push the background gc threads can receive
> > errors and throw them out to userspace.
>
> Right, the inodegc regression fix simply restored the previous
> status quo. Nothing more, nothing less, exactly what we want
> regression fixes to do. But it took some time for me to get to
> because there were much higher priority events occurring....
>
> ....
>
> > The problem with putting this in online repair is that Dave (AFAIK)
> > feels very strongly that every bug report needs to be triaged
> > immediately, and that takes priority over reviewing new code such as
> > online repair.
>
> My rationale is that we can ignore it once we know the scope of the
> issue, but until we know that information the risk of being
> unprepared for sudden escalation is rather high and that's even
> worse for stress and burnout levels.
Yeah, too bad a lot of xfs bugs are mismatches in thinking between
subcomponent authors & require deep analysis. Occasionally we get
"lucky" and it's closer to the surface like the 6.3 corruption thing.
Other times it's broken stuff hiding deep.
> The fedora corruption bug I mention above is a canonical example of
> why triaging bug reports immediately is important - the original bug
> report was clearly somethign that needed to be fixed straight away,
> regardless of the fact we didn't know it could cause misdirected
> writes at the time.
>
> Once we got far enough into the fedora bug report triage, I simply
> pointed the distro at the commit for them to test, and they did
> everything else. Once confirmation that it fixed the problem came
> in, I sent it immediately to the stable kernel maintainers.
>
> IOWs, if I had not paid attention to the original bug report, it
> would have taken me several more days to find the problem and fix it
> (remember it took me ~3 days from report to fix originally). Users
> would have been exposed to the corruption bug for much longer than
> they were, and that doesn't make a bad situation any better.
>
> And don't get me started on syzkaller and "security researchers"
> raising inappropriate CVEs....
I won't. We're severely understaffed, and that problem just got
worse.
> So, yeah, immediate triage is pretty much required at this point for
> all bug reports because the downstream impacts of ignoring them is
> only causing more stress and burnout risk for lots more people. The
> number of downstream people pulled into (and still dealing with the
> fallout of) that recent, completely unnecessary CVE fire drill was
> just ... crazy.
I saw the 39 rhbz sub-bugs from that one. Wow. What an abuse of
process to make you all endure that.
> We can choose to ignore triaged bug reports if they aren't important
> enough to deal with immediately (like this unlinked inode list
> issue), but we can make the decision (and justify it) based on the
> knowledge we have rather instead of claiming ignorance. We're
> supposed to be professional engineers, yes?
I was only here to collect dogecoin. :P
> > That's the right thing to do, but every time someone
> > sends in some automated fuzzer report, it slows down online repair
> > review. This is why I'm burned out and cranky as hell about script
> > kiddies dumping zerodays on the list and doing no work to help us fix
> > the problems.
>
> Reality sucks, and I hate it too. We get handed all the shit
> sandwiches and everyone seems to expect that we will simply to eat
> them up without complaining. But it's not like we didn't expect it -
> upstream Linux development has always been a great big shit sandwich
> and it's not going to be changing any time soon....
<sob>
--D
> -Dave.
> --
> Dave Chinner
> david@fromorbit.com
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: xfs: system fails to boot up due to Internal error xfs_trans_cancel
2023-06-06 2:46 ` Dave Chinner
2023-06-06 3:22 ` Darrick J. Wong
@ 2023-06-06 11:23 ` Thorsten Leemhuis
1 sibling, 0 replies; 28+ messages in thread
From: Thorsten Leemhuis @ 2023-06-06 11:23 UTC (permalink / raw)
To: Dave Chinner, Darrick J. Wong
Cc: Linux regressions mailing list, Ritesh Harjani (IBM),
shrikanth hegde, dchinner, linux-xfs, Srikar Dronamraju, ojaswin
On 06.06.23 04:46, Dave Chinner wrote:
> On Mon, Jun 05, 2023 at 02:57:45PM -0700, Darrick J. Wong wrote:
>> On Mon, Jun 05, 2023 at 03:27:43PM +0200, Thorsten Leemhuis wrote:
>>> /me waves friendly
>>>
>>> On 18.04.23 06:56, Darrick J. Wong wrote:
>>>> On Mon, Apr 17, 2023 at 01:16:53PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
>>>>> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
>>>>> for once, to make this easily accessible to everyone.
>>>>>
>>>>> Has any progress been made to fix below regression? It doesn't look like
>>>>> it from here, hence I wondered if it fall through the cracks. Or is
>>>>> there some good reason why this is safe to ignore?
>>>>
>>>> Still working on thinking up a reasonable strategy to reload the incore
>>>> iunlink list if we trip over this. Online repair now knows how to do
>>>> this[1], but I haven't had time to figure out if this will work
>>>> generally. [...]
>>>
>>> I still have this issue on my list of tracked regressions, hence please
>>> allow me to ask: was there any progress to resolve this? Doesn't look
>>> like it, but from my point it's easy to miss something.
>>
>> Yeah
BTW, many thx for your detailed answer.
>> -- Dave put "xfs: collect errors from inodegc for unlinked inode
>> recovery" in for-next yesterday, and I posted a draft of online repair
>> for the unlinked lists that corrects most of the other problems that we
>> found in the process of digging into this problem:
>> https://lore.kernel.org/linux-xfs/168506068642.3738067.3524976114588613479.stgit@frogsfrogsfrogs/T/#m861e4b1259d9b16b9970e46dfcfdae004a5dd634
>>
>> But that's looking at things from the ground up, which isn't terribly
>> insightful as to what's going on, as you've noted. :)
Let me just mark this regression as resolved in the tracking then; this
is, well, clearly not your typical every day regression and at the same
time something your clearly work on resolving, hence not really worth
tracking, as there are bigger fish to fry.
#regzbot inconclusive: pretty special regression; fix for part of it now
in -next, work ongoing to solve other parts (see discussion)
>>> BTW, in case this was not yet addressed: if you have a few seconds,
>>> could you please (just briefly!) explain why it seems to take quite a
>>> while to resolve this? A "not booting" regressions sounds like something
>>> that I'm pretty sure Linus normally wants to see addressed rather sooner
>>> than later. But that apparently is not the case here. I know that XFS
>>> devs normally take regressions seriously, hence I assume there are good
>>> reasons for it. But I'd like to roughly understand them (is this a
>>> extremely corner case issue others are unlike to run into or something
>>> like that?), as I don't want Linus on my back with questions like "why
>>> didn't you put more pressure on the XFS maintainers" or "you should have
>>> told me about this".
>>
>> First things first -- Ritesh reported problems wherein a freshly mounted
>> filesystem would fail soon after because of some issue or other with the
>> unlinked inode list. He could reproduce this problem, but (AFAIK) he's
>> the only user who's actually reported this. It's not like *everyone*
>> with XFS cannot boot anymore, it's just this system. Given the sparsity
>> of any other reports with similar symptoms, I do not judge this to be
>> a hair-on-fire situation.
Definitely; don't worry, I noticed that, otherwise I'd have made more
noise early. :-D
>> (Contrast this to the extent busy deadlock problem that Wengang Wang is
>> trying to solve, which (a) is hitting many customer systems and (b)
>> regularly. Criteria like (a) make things like that a higher severity
>> problem IMHO.)
>
> Contrast this to the regression from 6.3-rc1 that caused actual user
> data loss and filesystem corruption after 6.3 was released.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2208553
>
> That's so much more important than any problem seen in a test
> environment it's not funny.
>
> We'd already fixed this regression that caused it in 6.4-rc1 - the
> original bug report (a livelock in data writeback) happened 2 days
> before 6.3 released. It took me 3 days from report to having a fix
> out for review (remember that timeframe).
>
> At the time we didn't recognise the wider corruption risk the
> failure we found exposed us to, so we didn't push it to stable
> immediately. Hence when users started tripping over corruption and I
> triaged it down to misdirected data write from -somewhere-. Eric
> then found a reproducer and bisected to a range of XFS changes, and
> I then realised what the problem was....
>
> Stuff like this takes days of effort and multiple people to get to
> the bottom of, and -everything else- gets ignored while we work
> through the corruption problem.
Yeah, and many other developers are good as this as well; that's why I
don't even add some regressions to the tracking I notice. And I'm also
well aware that I only notice some regressions once Linus mainlines a fix.
But nevertheless my tracking helps in quite a few cases, as developers
sometimes are humans and let things fall through the cracks. And there
always have and still are developers and subsystems are not as good as
XFS and don't handle regressions like Linus wants them to be handled. I
also help reporters to reach the right developers and improve their bug
reports (e.g. by telling them to bisect and things like that). Guess all
that is why Linus and Greg apparently seem happy about my work.
That being said: there still a lot of room for improvements, but it's a
start.
> Thorsten, I'm betting that you didn't even know about this
> regression -
Then you lost your bet. ;) I can even prove that I saw the "[PATCH,
STABLE 6.3.x] xfs: fix livelock in delayed allocation at ENOSPC" mail
https://fosstodon.org/@kernellogger/110446215848501171
But I'm pretty sure I was aware of it earlier already and decided to not
interfere, as you clearly were working on it with the required priority
(thx for that, btw).
> it's been reported, tracked, triaged and fixed
> completely outside the scope and visibility of the "kernel
> regression tracker". Which clearly shows that we don't actually need
> some special kernel regression tracker infrastructure to do our jobs
> properly, nor do we need a nanny to make sure we actually are
> prioritising things correctly....
> ....
I'm not getting into that discussion. Convince Linus and Greg that my
work is not worth it at all; if it hear it from them I'll stop.
Ciao, Thorsten
^ permalink raw reply [flat|nested] 28+ messages in thread
end of thread, other threads:[~2023-06-06 11:23 UTC | newest]
Thread overview: 28+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-17 11:15 xfs: system fails to boot up due to Internal error xfs_trans_cancel shrikanth hegde
2023-02-17 11:25 ` shrikanth hegde
2023-02-17 11:30 ` shrikanth hegde
2023-02-17 15:03 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-02-17 16:53 ` Darrick J. Wong
2023-02-17 20:25 ` Dave Chinner
2023-02-18 7:17 ` shrikanth hegde
2023-02-22 16:41 ` Darrick J. Wong
2023-02-24 8:04 ` shrikanth hegde
2023-02-24 21:18 ` Darrick J. Wong
2023-03-09 14:26 ` Ritesh Harjani
2023-03-09 17:27 ` Darrick J. Wong
2023-03-16 4:46 ` Ritesh Harjani
2023-03-16 5:20 ` Darrick J. Wong
2023-03-17 20:44 ` Darrick J. Wong
2023-03-18 16:50 ` Ritesh Harjani
2023-03-18 19:20 ` Darrick J. Wong
2023-03-20 5:20 ` Ritesh Harjani
2023-04-17 11:16 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-18 4:56 ` Darrick J. Wong
2023-04-21 13:04 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-05 13:27 ` Thorsten Leemhuis
2023-06-05 21:57 ` Darrick J. Wong
2023-06-06 2:46 ` Dave Chinner
2023-06-06 3:22 ` Darrick J. Wong
2023-06-06 11:23 ` Thorsten Leemhuis
2023-03-10 0:29 ` Dave Chinner
2023-03-16 4:48 ` Ritesh Harjani
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).