Comment 12 for bug 1977491
Revision history for this message
| Mike Silva (mikesilva) wrote Re: Update Samba in 22.04LTS to 4.15.7 so macOS clients can connect and transfer. | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I ran tests against the 22.10 daily for 6/13/22 in a VM, attaching the same drive I use for my Samba shares on the physical server, and reproduced the same behavior as above.
With my smb.conf configured as in comment #6 above, I could log in, but as soon as I tried to use the share by coping 1GB of bits up, the same panic happened. I will attach the log below.
With my smb.conf configured with fruit:resource = xattr, then I could connect, copy, and delete bits without issue.
Again, I haven't done a code deep dive, but very late last night I did a cursory search for recent changes to samba, vfs_fruit, vfs_streams_xattr, vfs_btrfs, and vfs_io_uring that seemed to touch how samba handles xattrs and streams. I did notice that about 4 months ago (don't quote me), there was a push to update vfs_fruit to fix a fairly severe CVE to do with boundary conditions. Perhaps, the fix(es) for that were such that fruit:resouce = xattr is properly handling extended attributes up to the stock Linux kernel max for ext4/btrfs of 64KB, but now fruit:resource = stream is not? Don't quote me on this...just spitballing. :-)