Feature request can skip this form. Bug report must complete it. Check List must be 100% match or it will be automatically closed without further discussion. Please remove this line.
[ ] My issue is valid with mirror default sample and not specific to my user-mode driver implementation
[v] I can always reproduce the issue with the provided description below.
[v] I have updated Dokany to the latest version and have reboot my computer after.
[ ] I tested one of the last snapshot from appveyor CI
Description
Using the Mirror sample, I made a drive expressing the file system of WAS with HTTP protocol.
However, while testing the opening of the .log file, I found that notepad sometimes fails to open the file. Looking at the process monitor, it was confirmed that the error occurs when the FileInformationClass argument of QueryInformation is passed to FileRemoteProtocolInformation(55). In the log, it was also recorded as unknown type = 55 in this case. To take a closer look, I checked the source fileinfo.c and found that there is no processing routine for FileRemoteProtocolInformation class. The related log is attached.
Logs
Please attach in separate files: mirror output, library logs and kernel logs.
In case of BSOD, please attach minidump or dump analyze output.
onexzero
commented
2 years ago
Feature request can skip this form. Bug report must complete it.
Check Listmust be 100% match or it will be automatically closed without further discussion. Please remove this line.Environment
Check List
Description
Using the Mirror sample, I made a drive expressing the file system of WAS with HTTP protocol. However, while testing the opening of the .log file, I found that notepad sometimes fails to open the file. Looking at the process monitor, it was confirmed that the error occurs when the FileInformationClass argument of QueryInformation is passed to FileRemoteProtocolInformation(55). In the log, it was also recorded as unknown type = 55 in this case. To take a closer look, I checked the source fileinfo.c and found that there is no processing routine for FileRemoteProtocolInformation class. The related log is attached.
Logs
Please attach in separate files: mirror output, library logs and kernel logs. In case of BSOD, please attach minidump or dump analyze output.