mac$ mkdir -p /Volumes/smb/a/b/c
from a Mac against a Samba share, for some reason the Mac client freezes and has to be rebooted.
Looking at a network trace it seems for some reason we're returning the same File-ID from a/b/ and /a/b/c/.
Macs rely on unique ids to build an in-memory filesystem db indexed by id, so returning the same id for two different paths is expected to cause fatal consequences.
A quick analysis of our code doesn't reveal any apparent bug that could cause this, so a more detailed analysis is required.
As a workaround setting
fruit:zero_file_id = yes
should prevent the issue.
This should be fixed in later releases.