When might we see currentIrpStack->FileObject->DeviceObject==NULL?

NTFSD
1

We’re seeing a bluescreen which suggests that our assumptions aren’t correct… Under what situations might a FILE_OBJECT’s DeviceObject member be NULL?

2

What problem are you seeing? I can’t imagine a valid case for this, sounds
to me like maybe your file object is bogus.

-scott
OSR

wrote in message news:xxxxx@ntfsd…

We’re seeing a bluescreen which suggests that our assumptions aren’t
correct… Under what situations might a FILE_OBJECT’s DeviceObject member
be NULL?

3

On 03/06/2013 07:10 AM, Scott Noone wrote:

What problem are you seeing? I can’t imagine a valid case for this,
sounds to me like maybe your file object is bogus.

Agree this shouldn’t happen.

  1. Which driver allocated the FileObject?
  2. Is FO_STREAM_FILE set?
  3. What is FileObject->Vpb and its DeviceObjects?

This stirs a long repressed memory where if the Vpb is not populated
correctly the result is a FileObject that functions correctly 99.9% of
the time, but isn’t really a correct FileObject.