Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
I am running WHQL on my KMDF driver. In particular the test DF - Fuzz zero length buffer IOCTL Test (Reliability) fails and I see the following text in the wdflogdump (!wdfkd.wdflogdump)
I am not sure (yet) whether the failure of the test is a symptom of the problem being indicated in the logs.
Here is the text in the log.
WDFREQUEST X InputBufferLength length is zero, 0xc0000023(STATUS_BUFFER_TOO_SMALL)
I realize the test is sending randomly generated IOCTLs with zero length input and output buffers.
Any ideas on what the above failure in the log might be saying about the driver?
Thanks,
Aneesh
Upcoming OSR Seminars | ||
---|---|---|
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
Kernel Debugging | 13-17 May 2024 | Live, Online |
Developing Minifilters | 1-5 Apr 2024 | Live, Online |
Internals & Software Drivers | 11-15 Mar 2024 | Live, Online |
Writing WDF Drivers | 26 Feb - 1 Mar 2024 | Live, Online |
Comments
The framework source code is available on github. Your error message is being logged here: https://github.com/microsoft/Windows-Driver-Frameworks/blob/main/src/framework/shared/core/fxrequest.cpp#L1370
This appears to be the standard WDF processing for input buffer length zero IOCTLs, and is unlikely to be the cause of failure, unless somebody broke the test.
Mark, thanks. I did check the source and it was not clear to me why it was being flagged as an error.