interpretation of relatedfileobject file name

OSR_Community_User · August 30, 2002, 9:35am

Hi,

I need to know how exactly to interpret the relatedfileobject field within
the fileobject passed to
my driver. I assume that the field is used to store context when the
driver is called with a path
name that is relative to a container.If the filename in the fileobject
does not have
a leading slash '' then the relatedfileobject field is supposed to
contain the name of the directory
path above it.

I have noticed the following (abnormal ?) behaviour. I have noticed that
at times the filename in
the relatedfileobject field does not have a leading slash itself or the
filename is empty ( i.e the
length is 0 ). In either case merely adding a slash in front of the
related file name seems to solve
the problem.

Am I understanding this correctly? How am I supposed to construct / parse
the file path in this case?

Regards,

Royston Mascarenhas
MicroWorld Technologies Inc.

Tel: 91-22-826 570(1-5) Extn: 210

There is *always* one more bug - Lubarsky’s law of Cybernetic Entomology

OSR_Community_User · August 30, 2002, 10:44am

The FileName field of the FILE_OBJECT is only valid during the IRP_MJ_CREATE for that file object. Hence, the FileName field of RelatedFileObject is invalid. You should use the name your filter has already determined for that related file object during its preceding IRP_MJ_CREATE.

-----Original Message-----
From: Royston Mascarenhas [mailto:xxxxx@mwti.net]
Sent: Friday, August 30, 2002 8:37 AM
To: File Systems Developers
Subject: [ntfsd] interpretation of relatedfileobject file name

Hi,