fast io try/except

NTFSD
1

must the filter fast io calls to lower driver’s fastio be wrapped in the
try/except.

BOOLEAN FastIoUnlockSingle(…)
{
retval = FALSE;
try{
if (VALID_FAST_IO(…)){
retval =
DevExt->FS->DriverObject->FastIoDispatch->FastIoUnlockSingle(…);
}
}
except(EXCEPTION_EXECUTE_HANDLER){
}

return retval;
}

In the above example, driver doesn’t access the buffers. it just calls
the fastio of lower driver. will the try/except be still required.

2

This is not needed. It should have been a simple matter to refer to the
filespy sample from the ifs kit to answer this question quicker :wink:

“Mani” wrote in message news:xxxxx@ntfsd…
> must the filter fast io calls to lower driver’s fastio be wrapped in the
> try/except.
>
> BOOLEAN FastIoUnlockSingle(…)
> {
> retval = FALSE;
> try{
> if (VALID_FAST_IO(…)){
> retval =
> DevExt->FS->DriverObject->FastIoDispatch->FastIoUnlockSingle(…);
> }
> }
> except(EXCEPTION_EXECUTE_HANDLER){
> }
>
> return retval;
> }
>
> In the above example, driver doesn’t access the buffers. it just calls
> the fastio of lower driver. will the try/except be still required.
>
>
>

3

Not necessary. Nobody does this I think.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From: “Mani”
Newsgroups: ntfsd
To: “Windows File Systems Devs Interest List”
Sent: Friday, April 21, 2006 1:22 PM
Subject: [ntfsd] fast io try/except

> must the filter fast io calls to lower driver’s fastio be wrapped in the
> try/except.
>
> BOOLEAN FastIoUnlockSingle(…)
> {
> retval = FALSE;
> try{
> if (VALID_FAST_IO(…)){
> retval =
> DevExt->FS->DriverObject->FastIoDispatch->FastIoUnlockSingle(…);
> }
> }
> except(EXCEPTION_EXECUTE_HANDLER){
> }
>
> return retval;
> }
>
> In the above example, driver doesn’t access the buffers. it just calls
> the fastio of lower driver. will the try/except be still required.
>
>
>
> —
> Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

4

I hope you are right that nobody does this; stack is enough of a problem
anyway !!

“Maxim S. Shatskih” wrote in message
news:xxxxx@ntfsd…
> Not necessary. Nobody does this I think.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
> ----- Original Message -----
> From: “Mani”
> Newsgroups: ntfsd
> To: “Windows File Systems Devs Interest List”
> Sent: Friday, April 21, 2006 1:22 PM
> Subject: [ntfsd] fast io try/except
>
>
>> must the filter fast io calls to lower driver’s fastio be wrapped in the
>> try/except.
>>
>> BOOLEAN FastIoUnlockSingle(…)
>> {
>> retval = FALSE;
>> try{
>> if (VALID_FAST_IO(…)){
>> retval =
>> DevExt->FS->DriverObject->FastIoDispatch->FastIoUnlockSingle(…);
>> }
>> }
>> except(EXCEPTION_EXECUTE_HANDLER){
>> }
>>
>> return retval;
>> }
>>
>> In the above example, driver doesn’t access the buffers. it just calls
>> the fastio of lower driver. will the try/except be still required.
>>
>>
>>
>> —
>> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>>
>> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>