File Object Lock with WDK
in [Device Drivers]
|
Prev: American E-commerce Increasingly Outside the Legal Positions
Next: How to get device key (hardware key) path in kernel mode ?
From: Maxim S. Shatskih on 29 Aug 2010 17:22 > I am allowing general file-system targets including COM, LPT, Pipes, etc. COM and LPT are not file systems. -- Maxim S. Shatskih Windows DDK MVP maxim(a)storagecraft.com http://www.storagecraft.com
From: Asaf Shelly on 30 Aug 2010 02:08 "Maxim S. Shatskih" wrote: > > A device designed for handling File Objects is expecting to handle multiple > > users > > ....and serial port is expecting to handle 1 user only. > This is why I found the design bug. Any other driver would delay your upper layer driver only in extreme cases, making it hard to detect or understand
From: Asaf Shelly on 30 Aug 2010 02:10 "Maxim S. Shatskih" wrote: > > Serial is always blocking reads but what if someone is using a driver, for > > example a disk driver, which is not blocking unless the queue is full? > > Disk stack is never ever blocking. > Unless the CD has errors on it..
From: Asaf Shelly on 30 Aug 2010 02:12 > > I am allowing general file-system targets including COM, LPT, Pipes, etc. > > COM and LPT are not file systems. > FS as in "FS" Object Store, not NTFS. Don't blame me that the world is using a File System to access drivers.
From: Maxim S. Shatskih on 30 Aug 2010 05:06
>> Disk stack is never ever blocking. >> > > Unless the CD has errors on it.. This is only on old ATA controllers where CD retries stall the HD hanging off the same PATA cable. -- Maxim S. Shatskih Windows DDK MVP maxim(a)storagecraft.com http://www.storagecraft.com |