Duplicate SMB file_ids leading to Windows client cache poisoning

[Jeremy Allison]

On Fri, Dec 10, 2021 at 06:06:56PM +0100, Ralph Boehme via samba-technical wrote:
>On 12/10/21 17:56, Andrew Walker wrote:
>>That's a good point, but if MacOS SMB client is faking up an inode 
>>number based on a hash of the filename in the zero-id case, isn't it 
>>even more likely to yield a collision at some point?
>
>well, it's somehash(name) combined with the parent-inode number. I 
>know, it's not ideal.
>
>But going back to inode numbers brings us back to:
>
>https://bugzilla.samba.org/show_bug.cgi?id=12715
>
>*scratches head*

OK, seems to me that we need inode numbers by default,
as that's what works with both Windows an Linux clients.

If Mac's need special handling here, then we have the
capability to detect them and switch out the inode
numbers for Mac clients (fruit... :-) :-).