Comment 6 for bug 1977491

I realized I made the stupid error of not using smbpasswd to instantiate my samba user on my fresh 22.04 install, so I ran another test and got some useful output. Attached is a zip of /var/logs/samba on 22.04, running your patch.

[This is a fresh install of 22.04, but the directories that Samba is sharing are on a separate drive from the OS, thus remain unchanged from what Samba on the two previous Ubuntu versions were able to share successfully.]

I was running atop at the time, to see what was going on. And, as soon as my Mac tried to mount the share after successfully login into the samba server, I saw a bunch of smb processes start as though smbd was forking out of control.

My smb.conf is pretty stock, using probably 98% of the default configuration as installed by the package. With the notable exception of the following:
aio read size = 1
aio write size = 1
block size = 4096
fruit:aapl = yes
fruit:copyfile = yes
fruit:encoding = native
fruit:metadata = stream
fruit:resource = stream
mdns name = mdns
min receivefile size = 1
strict allocate = yes
server multi channel support = yes
use sendfile = yes
vfs objects = catia fruit streams_xattr btrfs io_uring
kernel share modes = no
posix locking = no

The volume with the data I'm sharing is on btrfs, purposely created with nodesize= 65536 [eg 64KB], so that it can handle more xattr bits.

Finally, I'm using the same smb.conf that worked absolutely flawlessly with Samba in Ubuntu 21.10 and 20.04 before that. And, I've combed through the lines I've added, line by line to make sure that all of the configuration options I've selected are still supported in Samba 4.15.x, which is shipped in Ubuntu 22.04.