AfterFsctl Event

Fires after an IRP_MJ_FILE_SYSTEM_CONTROL request is processed.

Syntax

virtual int FireAfterFsctl(CBFilterAfterFsctlEventParams *e);
typedef struct {
const char *FileName;
int FsControlCode;
const void *InBuffer;
int InBufferLength;
int InBufferValidBytes;
void *OutBuffer;
int OutBufferLength;
int OutBufferValidBytes;
int Status;
int ResultCode; int reserved; } CBFilterAfterFsctlEventParams;
virtual INT FireAfterFsctl(CBFilterAfterFsctlEventParams *e);
typedef struct {
LPCWSTR FileName;
INT FsControlCode;
LPCVOID InBuffer;
INT InBufferLength;
INT InBufferValidBytes;
LPVOID OutBuffer;
INT OutBufferLength;
INT OutBufferValidBytes;
INT Status;
INT ResultCode; INT reserved; } CBFilterAfterFsctlEventParams;

Remarks

This event fires after an IRP_MJ_FILE_SYSTEM_CONTROL (FSCTL) request is processed. Such requests are sent using the Windows API's DeviceIoControl function (user mode), or ZwFsControlFile function (kernel mode); please refer to Microsoft's documentation for more information.

Applications may use this event to modify the output data (if there is any) before the response is returned to the requestor. Applications that choose to do this must:

  1. Copy no more than OutBufferLength bytes into OutBuffer.
  2. Update the OutBufferValidBytes parameter's value afterwards so that it correctly reflects the amount of data in OutBuffer.

Applications only need to handle this event if they've added a standard filter rule that includes the FS_CE_AFTER_FSCTL flag.

The FileName parameter reflects the file, directory, or volume targeted by the request.

The FsControlCode parameter reflects the requested filesystem control code (FSCTL).

The InBuffer parameter points to a memory buffer that contains the data required to perform the operation. The InBufferLength and InBufferValidBytes parameters reflect the capacity of InBuffer and the length of the data it contains (respectively), in bytes; InBufferValidBytes may be less than InBufferLength (unless the request did not include data, in which case both will be 0).

The OutBuffer parameter points to a memory buffer that contains the data returned by the operation. The OutBufferLength and OutBufferValidBytes parameters reflect the capacity of OutBuffer and the length of the data it contains (respectively), in bytes; OutBufferValidBytes may be less than OutBufferLength (unless the operation did not return data, in which case both will be 0).

Please refer to the Buffer Parameters topic for more information on how to work with memory buffer event parameters.

The Status parameter contains an NT status code that indicates the outcome of the operation; 0 indicates success. To convert this value to a Win32 error code, call the NtStatusToWin32Error method. Please note that this event won't fire for failed requests unless the ProcessFailedRequests property is enabled. Applications may change this parameter's value if they want a different NT status code to be returned.

The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource isn't available, security checks failed, etc.), set it to a non-zero value to report an appropriate error. Please refer to the Error Reporting and Handling topic for more information.

This event is fired synchronously; please refer to the Event Types topic for more information.

 
 
Copyright (c) 2020 Callback Technologies, Inc. - All rights reserved.
CBFS Filter 2020 C++ Edition - Version 20.0 [Build 7543]