memcpy: detected field-spanning write (size 20) of single field "xattrstart"

Bug #2101782 reported by Andreas Hasenack
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux-raspi (Ubuntu)
Confirmed
Undecided
Unassigned
linux-signed-hwe-6.11 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I created a zfs-encrypted pool at /dev/sda (a 16Gb pendrive), to use it as storage for lxd on this raspberry pi5 with 8Gb of RAM.

Creating the pool worked just fine, as did making it a storage for lxd. I then launched a test container, and it hung.

ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.11.0-1004-raspi 6.11.0-1004.4
ProcVersionSignature: Ubuntu 6.11.0-1004.4-raspi 6.11.0
Uname: Linux 6.11.0-1004-raspi aarch64
NonfreeKernelModules: zfs
AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.11.0-1004-raspi.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.32.0-0ubuntu2
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/mmcblk0p1)
Date: Sun Mar 9 13:29:39 2025
ImageMediaBuild: 20250308
Lspci-vt: -[0000:00]---00.0-[01]----00.0 Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge
PciMultimedia:

ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=screen-256color
 XDG_RUNTIME_DIR=<set>
ProcFB:

ProcKernelCmdLine: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe smsc95xx.macaddr=D8:3A:DD:F1:00:89 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc
RelatedPackageVersions:
 linux-restricted-modules-6.11.0-1004-raspi N/A
 linux-backports-modules-6.11.0-1004-raspi N/A
 linux-firmware 20250204.git0fd450ee-0ubuntu1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux-raspi
StagingDrivers: rpivid_hevc
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:

Revision history for this message
Andreas Hasenack (ahasenack) wrote :
Revision history for this message
Manuel Diewald (diewald) wrote (last edit ):

Hi Andreas,
we have an initial version of the plucky raspi kernel available in our bootstrap ppa (6.14.0-1003.3). Could you maybe check if it resolves the problem? The kernel that currently comes with plucky is an old oracular kernel. https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

This kernel seems better so far, no backtraces yet, thanks! Hope it can make it into plucky still!

$ uname -a
Linux pi5 6.14.0-1003-raspi #3-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 28 17:54:42 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

Jürg Häfliger (juergh)
tags: added: kern-12822
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-raspi (Ubuntu):
status: New → Confirmed
Revision history for this message
Manfred Herrmann (herrmann-manfred) wrote :
Download full text (5.1 KiB)

New Ubuntu 24.04.2 Installation on Lenovo T490 / Samsung SSD 990 EVO plus (latest firmware)
Install-Method ... auto/ZFS default/no encryption

tpt490 kernel: memcpy: detected field-spanning write (size 28) of single field "xattrstart" at /build/linux-hwe-6.11-56AUoP/linux-hwe-6.11-6.11.0/debian/build/build-generic/>
Apr 05 13:24:25 tpt490 kernel: WARNING: CPU: 0 PID: 800 at /build/linux-hwe-6.11-56AUoP/linux-hwe-6.11-6.11.0/debian/build/build-generic/____________________________________________________>
Apr 05 13:24:25 tpt490 kernel: Modules linked in: parport_pc ppdev lp parport nvme_fabrics nvme_keyring efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 zfs(PO) spl(O) mmc_block sn>
Apr 05 13:24:25 tpt490 kernel: CPU: 0 UID: 0 PID: 800 Comm: systemd-random- Tainted: P O 6.11.0-21-generic #21~24.04.1-Ubuntu
Apr 05 13:24:25 tpt490 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Apr 05 13:24:25 tpt490 kernel: Hardware name: LENOVO 20N2004EGE/20N2004EGE, BIOS N2IETA5W (1.83 ) 06/20/2024
Apr 05 13:24:25 tpt490 kernel: RIP: 0010:zfs_log_setsaxattr+0x13b/0x150 [zfs]
Apr 05 13:24:25 tpt490 kernel: Code: 01 0f 85 69 ff ff ff 31 c9 48 c7 c2 d0 68 e3 c0 4c 89 c6 4c 89 45 c8 48 c7 c7 78 62 e3 c0 c6 05 5f 51 13 00 01 e8 c5 9b ec df <0f> 0b 4c 8b 45 c8 e9 3b >
Apr 05 13:24:25 tpt490 kernel: RSP: 0018:ffffb8b2c17f7940 EFLAGS: 00010246
Apr 05 13:24:25 tpt490 kernel: RAX: 0000000000000000 RBX: ffff918150f18000 RCX: 0000000000000000
Apr 05 13:24:25 tpt490 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Apr 05 13:24:25 tpt490 kernel: RBP: ffffb8b2c17f7980 R08: 0000000000000000 R09: 0000000000000000
Apr 05 13:24:25 tpt490 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff91814bae9ed8
Apr 05 13:24:25 tpt490 kernel: R13: ffff918157543000 R14: ffff9181414df6c0 R15: ffff9181403bf0e0
Apr 05 13:24:25 tpt490 kernel: FS: 0000741bd5a65440(0000) GS:ffff918a96400000(0000) knlGS:0000000000000000
Apr 05 13:24:25 tpt490 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 05 13:24:25 tpt490 kernel: CR2: 0000741bd6a30590 CR3: 000000010ad88005 CR4: 00000000003706f0
Apr 05 13:24:25 tpt490 kernel: Call Trace:
Apr 05 13:24:25 tpt490 kernel: <TASK>
Apr 05 13:24:25 tpt490 kernel: ? show_regs+0x6c/0x80
Apr 05 13:24:25 tpt490 kernel: ? __warn+0x88/0x140
Apr 05 13:24:25 tpt490 kernel: ? zfs_log_setsaxattr+0x13b/0x150 [zfs]
Apr 05 13:24:25 tpt490 kernel: ? report_bug+0x182/0x1b0
Apr 05 13:24:25 tpt490 kernel: ? handle_bug+0x6e/0xb0
Apr 05 13:24:25 tpt490 kernel: ? exc_invalid_op+0x18/0x80
Apr 05 13:24:25 tpt490 kernel: ? asm_exc_invalid_op+0x1b/0x20
Apr 05 13:24:25 tpt490 kernel: ? zfs_log_setsaxattr+0x13b/0x150 [zfs]
Apr 05 13:24:25 tpt490 kernel: ? txg_rele_to_quiesce+0x33/0x40 [zfs]
Apr 05 13:24:25 tpt490 kernel: zfs_sa_set_xattr+0x366/0x3d0 [zfs]
Apr 05 13:24:25 tpt490 kernel: zpl_xattr_set_sa+0x100/0x1f0 [zfs]
Apr 05 13:24:25 tpt490 kernel: zpl_xattr_set+0x23b/0x280 [zfs]
Apr 05 13:24:25 tpt490 kernel: __zpl_xattr_user_set+0x128/0x170 [zfs]
Apr 05 13:24:25 tpt490 kernel: zpl_xattr_user_set+0x22/0x40 [zfs]
Apr 05 13:24:25 tpt490 kernel: __vfs_removexattr+0x81/0xd0
Apr 05 13:24:25 tpt490 k...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-signed-hwe-6.11 (Ubuntu):
status: New → Confirmed
Jürg Häfliger (juergh)
tags: added: kernel-daily-bug
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.