![]() ![]() > can anyone shed some light on the issue? > (what are the deviceObject and realDevice fields according to the WDK?) > that was created by the file system driver to the physical device object > according to the WDK, the purpose of the VPB is to connect the volume > using the connecting VPB, to the file system object). ![]() > for a file on a volume, IRP is sent to the volume device object, and then > the file system object that mounted the volume. > connect the volume device object that was created by the volume manager to > according to the Windows Internals book, the purpose of the VPB is to > points to the file system object that mounted the volume, and realDevice > one that creates volume device objects. > parameter block (VPB) for the corresponding storage device object and sets > The file system mounts the volume by associating the VDO with the volume > newly created VDO forms the base of the file system volume stack for the > DEVICE_OBJECT plus an optional file-system-defined device extension. > creates a volume device object (VDO) for the volume. > "When a file system receives the volume mount request for a new volume, it > seems that there are contradictions between the WDK documentation and the > The Volume Parameter Block purpose and fields are not clear to me. NTFS call this device object (refer to the FASTFAT source for an example). That the WDK docs are using this naming convention since that's what FAT and Object that the volume manager creates to represent the volume. System's volume device object." This would be distinct from the device The WDK docs are calling the DeviceObject field of the VPB the, "file > that is a back pointer to the volume device object. > points to the file system object >that mounted the volume, and realDevice > there is the VPB structure that has two pointers - deviceObject that > whereas the Windows Internals book explains that the volume manager is the (what are the deviceObject and realDevice fields according to the WDK?) That was created by the file system driver to the physical device object in the device stack. (if an applications asks for a file on a volume, IRP is sent to the volume device object, and then using the connecting VPB, to the file system object).Īccording to the WDK, the purpose of the VPB is to connect the volume device object inside the volume device object there is the VPB structure that has two pointers - deviceObject that points to the file system object that mounted the volume, and realDevice that is a back pointer to the volume device object.Īccording to the Windows Internals book, the purpose of the VPB is to connect the volume device object that was created by the volume manager to the file system object that mounted the volume. Whereas the Windows Internals book explains that the volume manager is the one that creates volume device objects. The file system mounts the volume by associating the VDO with the volume parameter block (VPB) for the corresponding storage device object and sets the VPB_MOUNTED flag on the VPB." ![]() The newly created VDO forms the base of the file system volume stack for the new (or remounted) volume. The VDO consists of a DEVICE_OBJECT plus an optional file-system-defined device extension. "When a file system receives the volume mount request for a new volume, it creates a volume device object (VDO) for the volume. It seems that there are contradictions between the WDK documentation and the Windows Internals book (5th edition). The Volume Parameter Block purpose and fields are not clear to me. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |