The IRP_MJ_READ request is sent by the I/O Manager or by a file system driver. This request can be sent, for example, when a user-mode application has called a Microsoft Win32 function such as ReadFile, or when a kernel-mode component has called ZwReadFile.
Operation: File System Drivers
The file system driver should extract and decode the file object to determine the parameters and minor function code.
For memory descriptor list (MDL) read requests, the file system should check the minor function code to determine which operation is requested. The following are the valid minor function codes, which can be used only for cached file I/O:
For more information about handling this IRP, study the CDFS and FASTFAT samples that are included in the Windows Driver Kit (WDK).
Operation: File System Filter Drivers
The filter driver should perform any needed processing and, depending on the nature of the filter, either complete or fail the IRP or pass it down to the next-lower driver on the stack.
A file system or filter driver calls IoGetCurrentIrpStackLocation with the given IRP to get a pointer to its own stack location in the IRP, shown in the following list as IrpSp. (The IRP is shown as Irp.) The driver can use the information contained in the following members of the IRP and the IRP stack location in processing a read request:
Pointer to the target device object.
Pointer to a system-supplied buffer to be used as an intermediate system buffer, if the DO_BUFFERED_IO flag is set in DeviceObject->Flags. Otherwise, this member is set to NULL.
Pointer to an IO_STATUS_BLOCK structure that receives the final completion status and information about the requested operation. For more information, see the description of the IoStatusBlock parameter to ZwReadFile.
Address of a memory descriptor list (MDL) describing the pages that contain the data to be read.
Pointer to a caller-supplied output buffer that receives the data that is read from the file.
Pointer to the file object that is associated with DeviceObject. If the FO_SYNCHRONOUS_IO flag is set in IrpSp->FileObject->Flags, the file object was opened for synchronous I/O.
The IrpSp->FileObject parameter contains a pointer to the RelatedFileObject field, which is also a FILE_OBECT structure. The RelatedFileObject field of the FILE_OBJECT structure is not valid during the processing of IRP_MJ_READ and should not be used.
Specifies the operation being requested and contains one of the following:
A LARGE_INTEGER variable that specifies the starting byte offset within the file of the data to be read.
Key value associated with a byte-range lock on the target file.
Length in bytes of the data to be read. If the read operation is successful, the number of bytes read is returned in the Information member of the IO_STATUS_BLOCK structure pointed to by Irp->IoStatus.
File systems round write and read operations at end of file up to a multiple of the sector size of the underlying file storage device. When processing pre-read or pre-write operations, filters that allocate and swap buffers need to round the size of an allocated buffer up to a multiple of the sector size of the associated device. If they do not, the length of data transferred from the underlying file system will exceed the allocated length of the buffer. For more information about swapping buffers, see swapBuffers Minifilter Sample.