Error for file name in create callback

NTFSD
1

Hello,

In my mini filter pre-create callback, I call FltGetFileNameInformation to
get the name of the thing being opened. I use arguments
FLT_FILE_NAME_NORMALIZED and FLT_FILE_NAME_QUERY_ALWAYS_ALLOW_CACHE_LOOKUP.

From time to time, I get NTSTATUS of STATUS_OBJECT_NAME_NOT_FOUND and
STATUS_OBJECT_PATH_NOT_FOUND. On first glance, this doesn’t seem like a
problem.

Using notepad.exe, I tried to open files using paths and names that I know
don’t exist. Notepad agrees with me.

What’s odd is I didn’t get the above errors which tells me they don’t mean
what I think they mean. Checked help and didn’t see anything interesting.

Can anyone define some circumstance that might produce this error?

Thanks,
Mickey.

2

Too many negatives. :wink:

You didn’t get the error saying the file didn’t exist? Something else?
What *did* you get?

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mickey Lane
Sent: Tuesday, July 05, 2005 5:09 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Error for file name in create callback

Hello,

In my mini filter pre-create callback, I call FltGetFileNameInformation to
get the name of the thing being opened. I use arguments
FLT_FILE_NAME_NORMALIZED and FLT_FILE_NAME_QUERY_ALWAYS_ALLOW_CACHE_LOOKUP.

From time to time, I get NTSTATUS of STATUS_OBJECT_NAME_NOT_FOUND and
STATUS_OBJECT_PATH_NOT_FOUND. On first glance, this doesn’t seem like a
problem.

Using notepad.exe, I tried to open files using paths and names that I know
don’t exist. Notepad agrees with me.

What’s odd is I didn’t get the above errors which tells me they don’t mean
what I think they mean. Checked help and didn’t see anything interesting.

Can anyone define some circumstance that might produce this error?

Thanks,
Mickey.

Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

Too many negatives indeed…

I was filtering one drive (F:) and running my little test against another
(C:).

After doing it right, it works exactly like you’d expect it to.

Sorry for the wasted time…

Mickey.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Cross
Sent: Tuesday, July 05, 2005 5:13 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Error for file name in create callback

Too many negatives. :wink:

You didn’t get the error saying the file didn’t exist? Something else? What
*did* you get?

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mickey Lane
Sent: Tuesday, July 05, 2005 5:09 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Error for file name in create callback

Hello,

In my mini filter pre-create callback, I call FltGetFileNameInformation to
get the name of the thing being opened. I use arguments
FLT_FILE_NAME_NORMALIZED and FLT_FILE_NAME_QUERY_ALWAYS_ALLOW_CACHE_LOOKUP.

From time to time, I get NTSTATUS of STATUS_OBJECT_NAME_NOT_FOUND and
STATUS_OBJECT_PATH_NOT_FOUND. On first glance, this doesn’t seem like a
problem.

Using notepad.exe, I tried to open files using paths and names that I know
don’t exist. Notepad agrees with me.

What’s odd is I didn’t get the above errors which tells me they don’t mean
what I think they mean. Checked help and didn’t see anything interesting.

Can anyone define some circumstance that might produce this error?

Thanks,
Mickey.