Bug 14909 - mkdir -p from macOS client causes client to freeze
Summary: mkdir -p from macOS client causes client to freeze
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: unspecified
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-17 10:56 UTC by Ralph Böhme
Modified: 2021-11-17 10:56 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralph Böhme 2021-11-17 10:56:05 UTC
When running

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

[global]
fruit:zero_file_id = yes

should prevent the issue.