Verifier bug check code explanation?

Does anyone have a less vague explanation for driver verifier bug check
code 00c9/P1=4, than the documentation’s “Invalid device object passed to
IoCallDriver”??

The device (in P2) is not “invalid” - in fact it is the NTFS device.
Everything works fine if I don’t use the verifier. But this one (I believe
falsely reported) error means that I can’t benefit from any other help that
the driver verifier can give me.

If I had a better explanation of why it could think it is “invalid”, I
might be able to set things in the IRP (or elsewhere) to persuade the
driver verifier that the call to IoCallDriver is OK. Any ideas??

Brian Collins, iOra


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Could you execute the following command in the debugger:

dt _DEVICE_OBJECT

-----Original Message-----
From: xxxxx@iOra.com [mailto:xxxxx@iOra.com]
Sent: Wednesday, June 27, 2001 1:42 AM
To: File Systems Developers
Subject: [ntfsd] Verifier bug check code explanation?

Does anyone have a less vague explanation for driver verifier bug check
code 00c9/P1=4, than the documentation’s “Invalid device object passed
to
IoCallDriver”??

The device (in P2) is not “invalid” - in fact it is the NTFS device.
Everything works fine if I don’t use the verifier. But this one (I
believe
falsely reported) error means that I can’t benefit from any other help
that
the driver verifier can give me.

If I had a better explanation of why it could think it is “invalid”, I
might be able to set things in the IRP (or elsewhere) to persuade the
driver verifier that the call to IoCallDriver is OK. Any ideas??

Brian Collins, iOra


You are currently subscribed to ntfsd as: xxxxx@MICROSOFT.com To
unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Could you execute the following command in the debugger:

dt _DEVICE_OBJECT 88888888

Where 88888888 is the device in P2. - Eric

-----Original Message-----
From: xxxxx@iOra.com [mailto:xxxxx@iOra.com]
Sent: Wednesday, June 27, 2001 1:42 AM
To: File Systems Developers
Subject: [ntfsd] Verifier bug check code explanation?

Does anyone have a less vague explanation for driver verifier bug check
code 00c9/P1=4, than the documentation’s “Invalid device object passed
to
IoCallDriver”??

The device (in P2) is not “invalid” - in fact it is the NTFS device.
Everything works fine if I don’t use the verifier. But this one (I
believe
falsely reported) error means that I can’t benefit from any other help
that
the driver verifier can give me.

If I had a better explanation of why it could think it is “invalid”, I
might be able to set things in the IRP (or elsewhere) to persuade the
driver verifier that the call to IoCallDriver is OK. Any ideas??

Brian Collins, iOra


You are currently subscribed to ntfsd as: xxxxx@MICROSOFT.com To
unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Thanks Eric,

As discussed in separate e-mail, the DeviceObject *was* invalid - the
reference count had gone negative. This was purely as a result of my
mis-handling of the FileObject->DeviceObject references. The problem that
this would have caused would have been a slow leakage of undeletable
devices (0xFFFFFFFF files is a lot of files to close before the device will
go away!).

The driver verifier is a REALY USEFUL tool, so the main reaon for wanting
to fix this was so that I would not hide any other more serious potential
faults.

Thanks again

Brian


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com