WLK File Filter Driver - Oplocks Test Failure

[ikkoz]

I have been running WLK Test, and I have completed all tests except Oplocks Test.



i selected my file filter driver in "Software Device".

And in "Tests", I selected all playlists.

- Anonymous Pipe
- Antivirus Installable File System Filter Test
- File IO 2 Tests
- HyperVisor Code Integrity Readiness Test
- Installable File System Filter Test
- IntegrityStream test
- Mailslot Basic
- Mapped File IO 2
- Named Pipe Basic
- Named Pipe Kernel Security
- Named Pipe Reject Remote Clients
- Named Pipe State
- Object ID test
- Oplocks Test
- Registry Callback Tests
- ReparsePoints
- ScrubTest
- Syscache Test
- TDI filters and LSPs are not allowed
- Txfs2
- Winsock Core Functional Test

After running all the tests above, I have only failure in Oplocks Test.

I couldn't find any clues in the forum.

When I look in to the details of the test report, I could read following error message.

Runtime 9/23/2016 12:22:24.782 PM _
Runtime Index: 4003582698
Machine: DESKTOP-LTVD96R
Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun600FD5BE-3A82-E611-80BB-08002790B852\enhancedoplocks.exe
Process ID: 3816
Thread ID: 5296
Message 9/23/2016 12:22:24.782 PM EE8.14B0 : INFO : enhancedoplocks.cxx(6132):GLE 87: 09/23/2016::19:22:24.782 HelperThreadBreak_RW_Oplock Launched
Message 9/23/2016 12:22:25.834 PM EE8.704 : VAR[INFO ] 47 : enhancedoplocks.cxx(3779):GLE 2: 09/23/2016::19:22:25.829 After Other_Thread_Caused_Break, Oplock IoStatus=0x0 Broken=1
Message 9/23/2016 12:22:25.844 PM EE8.704 : VAR[INFO ] 47 : enhancedoplocks.cxx(3842):GLE 2: 09/23/2016::19:22:25.829 Our oplock code: ioinformation=0x7
Message 9/23/2016 12:22:25.855 PM EE8.704 : VAR[INFO ] 47 : enhancedoplocks.cxx(3843):GLE 2: 09/23/2016::19:22:25.845 Our oplock actualLevel 0x7, expected 0x8
Message 9/23/2016 12:22:25.865 PM EE8.704 : VAR[INFO ] 47 : enhancedoplocks.cxx(3855):GLE 2: 09/23/2016::19:22:25.861 Sleeping for 1 second to give our peer thread a change to issue I/O
Message 9/23/2016 12:22:26.890 PM EE8.704 : VAR[INFO ] 47 : enhancedoplocks.cxx(3860):GLE 2: 09/23/2016::19:22:26.886 Our acknowledge for the oplock Status=0x103
Message 9/23/2016 12:22:26.900 PM EE8.14B0 : INFO : enhancedoplocks.cxx(6180):GLE 87: 09/23/2016::19:22:26.886 Break_RW_Helper_Create Status =0x0
Error 9/23/2016 12:22:26.910 PM EE8.704 : VAR[SEV2 ] 47 : enhancedoplocks.cxx(3863):GLE 2: 09/23/2016::19:22:26.886 FAILURE: We effectively hold an R oplock [RW->R], not correct.
File: base\fs\test\shared_libs\stresslog\loggersource\logger.cxx Line: 461
Error Type:
Error Code: 0x0
Error Text: Error 0x00000000
Message 9/23/2016 12:22:26.920 PM EE8.14B0 : INFO : enhancedoplocks.cxx(6232):GLE 87: 09/23/2016::19:22:26.901 HelperThreadBreak_RW_Oplock Finished
Message 9/23/2016 12:22:26.934 PM EE8.704 : VAR[INFO ] 47 : enhancedoplocks.cxx(3962):GLE 2: 09/23/2016::19:22:26.932 -----------------------------------------------------------------------
Start Test 9/23/2016 12:22:26.937 PM HelperBreakLegacyL1
Error 9/23/2016 12:22:26.947 PM EE8.704 : +VAR+SEV2 47 : HelperBreakLegacyL1
File: base\fs\test\shared_libs\stresslog\loggersource\logger.hxx Line: 283
Error Type:
Error Code: 0x0
Error Text: Error 0x00000000
End Test 9/23/2016 12:22:26.950 PM HelperBreakLegacyL1
Result: Fail
Repro: enhancedoplocks.exe -path i: -all /logpass /logfile FileOplocks-CNTFS.log
Message 9/23/2016 12:22:26.961 PM EE8.704 : VAR[INFO ] 48 : enhancedoplocks.cxx(3657):GLE 2: 09/23/2016::19:22:26.948 Variation 5 subvariation 4
Message 9/23/2016 12:22:26.971 PM EE8.704 : VAR[INFO ] 48 : enhancedoplocks.cxx(3662):GLE 2: 09/23/2016::19:22:26.964 HelperBreakLegacyL1: BREAK_RW_NONE_BY_WRITE(24581)
Message 9/23/2016 12:22:26.981 PM EE8.704 : VAR[INFO ] 48 : enhancedoplocks.cxx(3677):GLE 2: 09/23/2016::19:22:26.979 File Open Status = 0x0
Message 9/23/2016 12:22:29.998 PM EE8.704 : VAR[INFO ] 48 : enhancedoplocks.cxx(3693):GLE 2: 09/23/2016::19:22:29.994 Oplock Created: Status=0x103, broken=0


Any clues to where to fix?

Continue reading...