BPIO_RESULTS - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ntddstor.h
typedef struct _BPIO_RESULTS {
LONG OpStatus;
USHORT FailingDriverNameLen;
WCHAR FailingDriverName[32];
USHORT FailureReasonLen;
WCHAR FailureReason[128];
} BPIO_RESULTS, *PBPIO_RESULTS;
View the official Windows Driver Kit DDI referenceNo description available.
The BPIO_RESULTS structure defines BypassIO operation-specific outputs for BPIO_OP_ENABLE and BPIO_OP_QUERY operations when a driver is failing the operation.
OpStatusReceives a NTSTATUS code available to the caller that identifies why the failing driver cannot support BypassIO. This field should only be set by the first driver to fail the enable/query request.
FailingDriverNameLenReceives the length of the string stored in FailingDriverName, in characters.
FailingDriverNameReceives a string that specifies the name of the driver that failed the request. For diagnostic reasons, a driver must store its name when it fails a BPIO_OP_ENABLE or BPIO_OP_QUERY operation. The name must match the actual name of the driver that is used by the system; for example, ntfs.sys. This string is not guaranteed to be NULL-terminated.
FailureReasonLenReceives the length of the string stored in FailingReason, in characters.
FailureReasonReceives a unique, descriptive string describing why the driver vetoed the enable/query request. This string is used for diagnostic reasons, and should be in English so that it does not need to be localized. This string is not guaranteed to be NULL-terminated.
See BypassIO for storage drivers for more information.
IOCTL_STORAGE_MANAGE_BYPASS_IO