-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[6.11] dmesg reports memcpy: detected field-spanning write cases for zfs_log module #16621
Comments
For posterity, defect is present in OpenSUSE Tumbleweed, Kernel 6.11.3, ZFS 2.2.6-1 |
Thanks for the updates. No need to keep posting them from here, it's not a defect, rather a false positive in the kernel memory checker. Already "fixed" on master, and that fix will be included in future releases that officially support 6.11 (2.2.7, 2.3.0) (per @behlendorf's comment above). Thanks! |
ok, that's reassuring :) FYI: still happens with pretty recent master (~ December 15th) CC: @robn , @behlendorf
|
System information
Describe the problem you're observing
Dmesg reports memcpy: detected field-spanning write cases for zfs_log module:
[ 19.571536] memcpy: detected field-spanning write (size 12) of single field "(char *)(lr + 1)" at /var/lib/dkms/zfs/2.2.6/build/module/zfs/zfs_log.c:514 (size 0)
[ 19.677272] memcpy: detected field-spanning write (size 20) of single field "(char *)(lr + 1) + snamesize" at /var/lib/dkms/zfs/2.2.6/build/module/zfs/zfs_log.c:515 (size 0)
[ 40.160309] memcpy: detected field-spanning write (size 16) of single field "lr + 1" at /var/lib/dkms/zfs/2.2.6/build/module/zfs/zfs_log.c:425 (size 0)
[ 46.463976] memcpy: detected field-spanning write (size 9) of single field "lr + 1" at /var/lib/dkms/zfs/2.2.6/build/module/zfs/zfs_log.c:461 (size 0)
Describe how to reproduce the problem
I have just installed kernel 6.11.2, zfs modules were built without error but when I rebooted I noted these call traces:
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: