AW: FSCTL_MARK_HANDLE and FltWriteFile question

Thanks for your comments.

> Did you make sure you opened the file for unbuffered I/O ?
No, we use buffered IO. This is for performance reasons. I will try
unbuffered I/O.

> Secondly, if just using the FO in km does not work why not just either
open the file again
> using FltCreateFile or ZwCreate file and mark that handle as well and use
a handle in km as well.
I will also try this. However this requires some changes. The only reference
we in the filter is the handle. We also need to pass a filename or file ID.

-----Urspr?ngliche Nachricht-----
Von: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] Im Auftrag von
xxxxx@kasardia.com
Gesendet: Montag, 23. Januar 2017 09:59
An: Windows File Systems Devs Interest List
Betreff: RE:[ntfsd] FSCTL_MARK_HANDLE and FltWriteFile question

Well then I have another tip. Did you make sure you opened the file for
unbuffered I/O ?
Secondly, if just using the FO in km does not work why not just either open
the file again using FltCreateFile or ZwCreate file and mark that handle as
well and use a handle in km as well.


NTFSD is sponsored by OSR

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
drivers!
Details at http:

To unsubscribe, visit the List Server section of OSR Online at
http:</http:></http:>

Using unbuffered I/O to write the data did the trick!

Looks like writing the buffers back to disk in km does take care of the
marked handle. I am wondering why this works OK when using buffered I/O in
user mode?