Christian, thank you for your response on this, (apologize for the
delay in acknowledging it).
It seems MSFT has published a bunch of details since I last went
through the documentation. Now there is a new notification type
TRANSACTION_NOTIFY_COMMIT_COMPLETE, for a legacy filter driver is that
state as good as TRANSACTION_NOTIFY_COMMIT_FINALIZE.
Can we use this notification value to determine that the driver can
begin scanning files?
On Wed, Sep 12, 2012 at 5:53 AM, wrote:
> In a legacy filter you have to basically write a full-blown resource manager, as was done for Filter Manager to support minifilters. There’s no comprehensive documentation on how to do that.
>
> MM doesn’t do isolation. TxF is implemented in NTFS. If a transacted reader is present then there can’t be a non-transacted writer present (any transacted opener gets STATUS_TRANSACTIONAL_CONFLICT if a non-transacted writer is already present; opening a non-transacted writer when a transacted reader is present results in STATUS_SHARING_VIOLATION). Isolation only occurs when there is a transacted writer present.
> –
> Christian [MSFT]
> This posting is provided “AS IS” with no warranties, and confers no rights.
>
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule of debugging and file system seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Re-sending this.
On Mon, Aug 5, 2013 at 4:13 PM, Amritanshu wrote:
> Christian, thank you for your response on this, (apologize for the
> delay in acknowledging it).
>
> It seems MSFT has published a bunch of details since I last went
> through the documentation. Now there is a new notification type
> TRANSACTION_NOTIFY_COMMIT_COMPLETE, for a legacy filter driver is that
> state as good as TRANSACTION_NOTIFY_COMMIT_FINALIZE.
>
> Can we use this notification value to determine that the driver can
> begin scanning files?
>
> On Wed, Sep 12, 2012 at 5:53 AM, wrote:
>> In a legacy filter you have to basically write a full-blown resource manager, as was done for Filter Manager to support minifilters. There’s no comprehensive documentation on how to do that.
>>
>> MM doesn’t do isolation. TxF is implemented in NTFS. If a transacted reader is present then there can’t be a non-transacted writer present (any transacted opener gets STATUS_TRANSACTIONAL_CONFLICT if a non-transacted writer is already present; opening a non-transacted writer when a transacted reader is present results in STATUS_SHARING_VIOLATION). Isolation only occurs when there is a transacted writer present.
>> –
>> Christian [MSFT]
>> This posting is provided “AS IS” with no warranties, and confers no rights.
>>
>>
>> —
>> NTFSD is sponsored by OSR
>>
>> For our schedule of debugging and file system seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer