Roland Mainz

Same crash happens with a clean environment with just "calc" as application: ``` C:\Users\roland_mainz>drstrace -- calc

This bug is fixed since https://github.com/kofemann/ms-nfs41-client/commit/bc2898507a0e0533396982af0e8983ba4d764631

DrMemory reports TWO different syscalls for |recv()|: 1. NtDeviceIoControlFile AFD_RECV_INFO 2. NtDeviceIoControlFile AFD_RECV_INFO.BufferArray Example from our test system: ---- snip ---- ``` ~~6068~~ Error #266: UNINITIALIZED READ: reading 4 byte(s)...

Possible workaround: `$ drmemory -lib_blocklist_frames 1 -check_uninit_blocklist 'MSWSOCK,WS2_32' `

Stack trace from WinDBG: ---- snip ---- ``` (340.fc0): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected...

Yes, this is a bug. The workaround (as documented in https://github.com/kofemann/ms-nfs41-client/commit/2f9bef8c36e7268221aa94a83223b70eec952a70) is to mount the filesystem with the "writethru" option, e.g. $ /sbin/nfs_mount -o rw,writethru 'j' derfwpc5131:/export/home/rmainz #

> +1. I don't see any way open sourcing them would leak technologies used in the Windows kernel. Who came up with that rumor ? There are other opensource MiniRDR-based...

Is it possible to modify the libnfs-tools so they try NFSv4 first, or have an env var to set this ?

BTW specifying version=4 does not work: ``` $ nfs-ls nfs://derfwnb4966_ipv4//bigdisk Failed to mount nfs share : mount/mnt call failed with "Server responded: Program version mismatch" $ nfs-ls "nfs://derfwnb4966_ipv4//bigdisk?version=4" Failed to...

> Thanks for letting me know about this, I'll have a look. The VFS doesn't do the translation for us? That's surprising. No, the VFS layer is not going to...