Bit more experimentation on this issue. I tried a very small C program meant to create files with fewer permissions bits set. This succeeded which strengthens the theory of the umask getting ignored.
I haven't seen anything hinting whether this is more a client or server issue. I can speculate perhaps somewhere between 4.9 and 4.15 the NFS client code stepped closer to proper the "proper" 4.2 protocol. If a corresponding NFS server was slow at getting merged, what we're seeing could happen. Alternatively someone was trying to get a Linux NFS v4.2 client to work better with a different NFS v4.2 server, so they fixed Linux's NFS v4.2 client. Yet they failed to test with Linux's v4.2 server. This though is speculation. All I can say is sometime between kernels 4.9 and 4.15, NFS v4.2 got broken. There are hints this is related to handling of umask. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445