[Bug 2084533] Re: openzfs reports stacktrace on the current stable kernel

*** This bug is a duplicate of bug 2082060 ***
https://bugs.launchpad.net/bugs/2082060

** This bug has been marked a duplicate of bug 2082060
memcpy: detected field-spanning write (size 8) of single field "lr + 1"

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084533

Title:
openzfs reports stacktrace on the current stable kernel

Status in linux package in Ubuntu:
New

Bug description:
I installed 24.10 with openzfs, now at every boot, kernel reports:

```
[ 17.262734] systemd-journald[1002]: Received client request to flush runtime journal.
[ 17.263248] ------------[ cut here ]------------
[ 17.263251] memcpy: detected field-spanning write (size 28) of single field "xattrstart" at /build/linux-3RcvoW/linux-6.11.0/debian/build/build-generic/____________________________________________________________________________dkms/build/zfs/2.2.6/build/module/zfs/zfs_log.c:817 (size 0)
[ 17.263264] WARNING: CPU: 4 PID: 1087 at /build/linux-3RcvoW/linux-6.11.0/debian/build/build-generic/____________________________________________________________________________dkms/build/zfs/2.2.6/build/module/zfs/zfs_log.c:817 zfs_log_setsaxattr+0x140/0x150 [zfs]
[ 17.263408] Modules linked in: msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 zfs(PO) spl(O) hid_logitech_hidpp hid_logitech_dj usbhid uas usb_storage crct10dif_pclmul crc32_pclmul polyval_clmulni hid_multitouch polyval_generic hid_generic ghash_clmulni_intel nvme ucsi_acpi sha256_ssse3 i2c_hid_acpi xhci_pci nvme_core typec_ucsi video thunderbolt sha1_ssse3 i2c_hid xhci_pci_renesas nvme_auth typec wmi hid aesni_intel crypto_simd cryptd
[ 17.263431] CPU: 4 UID: 0 PID: 1087 Comm: systemd-random- Tainted: P O 6.11.0-8-generic #8-Ubuntu
[ 17.263435] Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
[ 17.263435] Hardware name: ASUSTeK COMPUTER INC. ASUS Vivobook S 16 M5606WA_M5606WA/M5606WA, BIOS M5606WA.304 08/05/2024
[ 17.263437] RIP: 0010:zfs_log_setsaxattr+0x140/0x150 [zfs]
[ 17.263537] Code: ff ff ff 31 c9 48 c7 c2 c0 64 d1 c0 4c 89 f6 4c 89 55 c0 48 c7 c7 68 5e d1 c0 4c 89 4d d0 c6 05 4a 50 13 00 01 e8 40 e8 5d cb <0f> 0b 4c 8b 55 c0 4c 8b 4d d0 e9 30 ff ff ff 90 90 90 90 90 90 90
[ 17.263540] RSP: 0018:ffff9dc280daf888 EFLAGS: 00010246
[ 17.263542] RAX: 0000000000000000 RBX: ffff90a863c39a70 RCX: 0000000000000000
[ 17.263543] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 17.263544] RBP: ffff9dc280daf8d0 R08: 0000000000000000 R09: 0000000000000000
[ 17.263544] R10: 0000000000000000 R11: 0000000000000000 R12: ffff90a85528e000
[ 17.263545] R13: ffff90a849c82780 R14: 000000000000001c R15: 0000000000000000
[ 17.263546] FS: 000078ecf406a940(0000) GS:ffff90af7e000000(0000) knlGS:0000000000000000
[ 17.263547] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 17.263548] CR2: 000078ecf4542e80 CR3: 00000001084d0000 CR4: 0000000000f50ef0
[ 17.263549] PKRU: 55555554
[ 17.263550] Call Trace:
[ 17.263552] <TASK>
[ 17.263555] ? show_trace_log_lvl+0x1be/0x310
[ 17.263559] ? show_trace_log_lvl+0x1be/0x310
[ 17.263560] ? zfs_sa_set_xattr+0x34a/0x3b0 [zfs]
[ 17.263642] ? show_regs.part.0+0x22/0x30
[ 17.263644] ? show_regs.cold+0x8/0x10
[ 17.263646] ? zfs_log_setsaxattr+0x140/0x150 [zfs]
[ 17.263726] ? __warn.cold+0xa7/0x101
[ 17.263728] ? zfs_log_setsaxattr+0x140/0x150 [zfs]
[ 17.263800] ? report_bug+0x114/0x160
[ 17.263802] ? handle_bug+0x51/0xa0
[ 17.263805] ? exc_invalid_op+0x18/0x80
[ 17.263806] ? asm_exc_invalid_op+0x1b/0x20
[ 17.263810] ? zfs_log_setsaxattr+0x140/0x150 [zfs]
[ 17.263875] ? zfs_log_setsaxattr+0x140/0x150 [zfs]
[ 17.263939] zfs_sa_set_xattr+0x34a/0x3b0 [zfs]
[ 17.264007] zpl_xattr_set_sa+0x102/0x200 [zfs]
[ 17.264092] zpl_xattr_set+0x21c/0x290 [zfs]
[ 17.264177] __zpl_xattr_user_set+0x128/0x170 [zfs]
[ 17.264247] zpl_xattr_user_set+0x22/0x40 [zfs]
[ 17.264340] __vfs_removexattr+0x81/0xd0
[ 17.264343] __vfs_removexattr_locked+0xe5/0x1a0
[ 17.264345] vfs_removexattr+0x59/0x110
[ 17.264346] __do_sys_fremovexattr+0x130/0x1c0
[ 17.264349] __x64_sys_fremovexattr+0x15/0x20
[ 17.264350] x64_sys_call+0x1fc7/0x22b0
[ 17.264353] do_syscall_64+0x7e/0x170
[ 17.264354] ? handle_pte_fault+0x12a/0x1c0
[ 17.264357] ? __handle_mm_fault+0x3d5/0x7a0
[ 17.264358] ? __count_memcg_events+0x86/0x160
[ 17.264361] ? count_memcg_events.constprop.0+0x2a/0x50
[ 17.264363] ? handle_mm_fault+0x1bb/0x2d0
[ 17.264364] ? do_user_addr_fault+0x5e9/0x7e0
[ 17.264367] ? irqentry_exit_to_user_mode+0x43/0x250
[ 17.264369] ? irqentry_exit+0x43/0x50
[ 17.264370] ? exc_page_fault+0x96/0x1c0
[ 17.264372] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 17.264375] RIP: 0033:0x78ecf3f285cb
[ 17.264377] Code: 73 01 c3 48 8b 0d 55 88 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 c7 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 25 88 0e 00 f7 d8 64 89 01 48
[ 17.264378] RSP: 002b:00007ffc1a423fa8 EFLAGS: 00000246 ORIG_RAX: 00000000000000c7
[ 17.264380] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 000078ecf3f285cb
[ 17.264381] RDX: 000000000000001a RSI: 000059876b52a08b RDI: 0000000000000005
[ 17.264381] RBP: 00007ffc1a4240e0 R08: 00000000000000c0 R09: 0000000000000001
[ 17.264382] R10: 0000598788986fd0 R11: 0000000000000246 R12: 0000000000000005
[ 17.264383] R13: 0000000000000001 R14: 000059876b52a08b R15: 0000000000000001
[ 17.264384] </TASK>
[ 17.264385] ---[ end trace 0000000000000000 ]---
[ 17.376119] ccp 0000:63:00.2: enabling device (0000 -> 0002)
[ 17.378582] ccp 0000:63:00.2: tee enabled
[ 17.378590] ccp 0000:63:00.2: psp enabled
```

This is reported multiple times. I'm not sure how serious the problem
is, but I'm afraid about my filesystem now.

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: linux-image-generic 6.11.0-8.8
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 15 12:22:54 2024
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: ASUSTeK COMPUTER INC. ASUS Vivobook S 16 M5606WA_M5606WA
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sl8xoz@/vmlinuz-6.11.0-8-generic root=ZFS=rpool/ROOT/ubuntu_sl8xoz ro quiet splash init_on_alloc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-6.11.0-8-generic N/A
linux-backports-modules-6.11.0-8-generic N/A
linux-firmware 20240913.gita34e7a5f-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2024
dmi.bios.release: 5.35
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: M5606WA.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M5606WA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.2
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrM5606WA.304:bd08/05/2024:br5.35:efr3.2:svnASUSTeKCOMPUTERINC.:pnASUSVivobookS16M5606WA_M5606WA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5606WA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUS Vivobook S 16
dmi.product.name: ASUS Vivobook S 16 M5606WA_M5606WA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084533/+subscriptions