The similar problem was discussed in may this year. The result of this
discussion was:
There is an undocumented kernel API that lets you to close the file (i.e.
you do not really want the IRP_MJ_CREATE to open the file),
void IoCancelFileOpen(PDEVICE_OBJECT DeviceObject, PFILE_OBJECT
FileObject);
This seems to be intended for FS filters if they want to fail the CREATE
request already processed successfully by the underlying FSD.
The function sends CLEANUP and CLOSE IRPs to the underlying FSD.
I hope it may help.
mari
-----Original Message-----
From: Rob Linegar [mailto:xxxxx@des.co.uk]
Sent: Thursday, September 28, 2000 3:22 PM
To: File Systems Developers
Subject: [ntfsd] RE: Problems deleting files
Hi Miguel,
I just resolved a similar problem in my filter. (see my post titled
“Problems after preventing access to files” from about a week ago)
The solution was to send down a cleanup then close when aborting open
operations.
Otherwise a reference in the underlying file system will remain.
Rob Linegar
Software Engineer
Data Encryption Systems Limited
-----Original Message-----
From: Miguel Angel Mendez Gil [mailto:xxxxx@seg.inf.cu]
Sent: 28 September 2000 17:10
To: File Systems Developers
Subject: [ntfsd] Problems deleting files
Hello,
I’m developing a File System Filter Driver, I hook the function
IRP_MJ_CREATE in order to processes files when opened or created, and
depending of certain conditions the operation is aborted. The problem is
when I tried to delete a file that match the desired condition, the
operation is aborted too, and I can’t delete the file.
Please help me.
You are currently subscribed to ntfsd as: xxxxx@decros.cz
To unsubscribe send a blank email to $subst(‘Email.Unsub’)