Hello Volker, On Monday 16 September 2024 14:51:49 Volker Lendecke wrote: > Hello Pali, > > Am Sun, Sep 15, 2024 at 07:41:26PM +0200 schrieb Pali Rohár: > > Now I have figured out that even the latest Windows Server 2022 version > > provides interoperability of FIFOs in SFU format with Windows NFS 4.1 > > Server. So if you configure on Windows Server 2022 one share which is > > exported over SMB and also NFS at the same time, and over SMB you create > > SFU-style fifo, then Windows NFS4.1 server recognize it and properly > > reports nfs4type as NFS4FIFO for NFSv4.1 client. > > it might work in this direction. However, in my tests if you create a > fifo over NFS you end up with a NFS-style reparse point, which is much > less prone to misinterpretation. Yes, that is truth. New NFS server versions by default create reparse points with NFS tags for special files. I just pointed out that even new NFS server can recognize old SFU-style of special files, which is useful to know in some situation (e.g. for mix of old and cifs clients together with nfs clients). > So my suggestion would be to use the > way that Microsoft properly documented in > > https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/ff4df658-7f27-476a-8025-4074c0121eec > > for anything that is newly created on all servers that can do reparse > points. For servers that don't support reparse points, WSL might be an > alternative. For me it would be highly confusing to add yet another > representation of unix special files from new code. > > Reading existing special files -- sure, where strictly required for > compat reasons. Creating them? No. Too many options make the test > matrix explode. > > Volker Important is that all my changes and whole discussion is about the non-default cifs mount option '-o sfu' which disables creating reparse points and uses only SFU-style of special files. So this is not a new code but special compatibility case used in scenarios where reparse points are either not supported or cifs client want to use normal files for storing fifos/sockets/... in SFU-style. I fully agree with you that in the default conditions new reparse points should be used and created. And this behavior is not changed or affected by these my patches. But in this compatibility mode, which has to be manually activated by user at cifs mount time by -o sfu option, we should follow what SFU is. Note that when this -o sfu option is not specified then these special system files are not recognized (or created) at all.
