Driver Crashes in Low Resource Simulation

NTFSD
1

Hi,

We are facing the serous problem when the minifilter driver runs in Low Resource Simulation.

  1. Run Driver Verify and enabled all the test cases except Low Resource Simulation - the driver is working properly.

  2. The driver bugchecked when Low resource Simulation is enabled.

Any information is very helpful to us. Thanks

Thanks and Regards,
Srinivasa Raghavan.

2

You’re going to need to debug your problem. Here’s a hint: Low resource
simulation returns NULL instead of a valid memory address from memory
allocations at random intervals, so you should look for places where you
are not checking the return from memory allocation routines.

After you figure out where you aren’t catching the allocation failure, you
have to decide whether you should gracefully fail, or whether you should
pre-allocate those resources you need so you can make forward progress
using those pre-allocated resources in the case that you’ve had an
allocation failure.

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@patni.com
Sent: Wednesday, January 03, 2007 3:25 AM
To: “Windows File Systems Devs Interest List”
Subject: [ntfsd] Driver Crashes in Low Resource Simulation

Hi,

We are facing the serous problem when the minifilter driver runs in Low
Resource Simulation.

1) Run Driver Verify and enabled all the test cases except Low Resource
Simulation - the driver is working properly.

2) The driver bugchecked when Low resource Simulation is enabled.

Any information is very helpful to us. Thanks

Thanks and Regards,
Srinivasa Raghavan.

3

And, this is just a wild guess I’m throwing out there, if you actually look at the dump (with correct symbols of course, but hey everyone knows that) you may actually determine where a bad pointer is used and what it is. That’ll save you time for this crash but you still need to check all other pointers too.

jerry
wrote in message news:xxxxx@ntfsd…

You’re going to need to debug your problem. Here’s a hint: Low resource simulation returns NULL instead of a valid memory address from memory allocations at random intervals, so you should look for places where you are not checking the return from memory allocation routines.

After you figure out where you aren’t catching the allocation failure, you have to decide whether you should gracefully fail, or whether you should pre-allocate those resources you need so you can make forward progress using those pre-allocated resources in the case that you’ve had an allocation failure.

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842

------------------------------------------------------------------------------
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@patni.com
Sent: Wednesday, January 03, 2007 3:25 AM
To: “Windows File Systems Devs Interest List”
Subject: [ntfsd] Driver Crashes in Low Resource Simulation

Hi,

We are facing the serous problem when the minifilter driver runs in Low Resource Simulation.

1) Run Driver Verify and enabled all the test cases except Low Resource Simulation - the driver is working properly.

2) The driver bugchecked when Low resource Simulation is enabled.

Any information is very helpful to us. Thanks

Thanks and Regards,
Srinivasa Raghavan.

4

Srinivasa

Right now you have a bug check to debug; windbg is your friend of course;
good luck!
You need to design, code and test for allocation failure from day one.

Cheers
Lyndon

wrote in message news:xxxxx@ntfsd…
> Hi,
>
> We are facing the serous problem when the minifilter driver runs in Low
> Resource Simulation.
>
> 1) Run Driver Verify and enabled all the test cases except Low Resource
> Simulation - the driver is working properly.
>
> 2) The driver bugchecked when Low resource Simulation is enabled.
>
> Any information is very helpful to us. Thanks
>
> Thanks and Regards,
> Srinivasa Raghavan.
>

5

You’re forgetting to handle some memory allocation failure properly.

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

wrote in message news:xxxxx@ntfsd…
> Hi,
>
> We are facing the serous problem when the minifilter driver runs in Low
Resource Simulation.
>
> 1) Run Driver Verify and enabled all the test cases except Low Resource
Simulation - the driver is working properly.
>
> 2) The driver bugchecked when Low resource Simulation is enabled.
>
> Any information is very helpful to us. Thanks
>
> Thanks and Regards,
> Srinivasa Raghavan.
>

6

BTW, PREfast issues a warning when you are not checking for memory allocation failure as well as in case of many other annoying bugs.

7

bad pointer problems mostly!