[英]How can I safely terminate a worker thread in the middle of a WaitForMultipleObjects call from the main thread?
嗨,我正在使用 C++ 和 Qt 框架來執行 Windows 程序。 我使用 Qt 線程,但這種情況也可能與其他線程 API 有關。 我使用 Win API 中的ReadDirectoryChangesW和WaitForMultipleObjects指定一個工作線程來監視目錄更改。 我希望能夠從主線程優雅地取消工作線程。 我已經閱讀了有關帶有句柄和 OVERLAPPED 參數的CancelIOEx的信息,但是這些數據類型都是指針。 是否有一些安全的方法可以將這些指針從工作線程安全地傳遞到主線程? 有沒有更好的做事方式?
這是這里的一些代碼,但使用 WaitForSingleObject 而不是 WaitForMultipleObjects,將從工作線程調用 function。 我可以從鏈接中發布此代碼嗎? 另請參閱此處以獲取有關 Windows 開發中心之外的 ReadDirectoryChangesW 的寶貴信息。
謝謝!
void WatchDirectory(LPCWSTR path)
{
char buf[2048];
DWORD nRet;
BOOL result=TRUE;
char filename[MAX_PATH];
DirInfo[0].hDir = CreateFile (path, GENERIC_READ|FILE_LIST_DIRECTORY,
FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE,
NULL, OPEN_EXISTING, FILE_FLAG_BACKUP_SEMANTICS|FILE_FLAG_OVERLAPPED,
NULL);
if(DirInfo[0].hDir == INVALID_HANDLE_VALUE)
{
return; //cannot open folder
}
lstrcpy( DirInfo[0].lpszDirName, path);
OVERLAPPED PollingOverlap;
FILE_NOTIFY_INFORMATION* pNotify;
int offset;
PollingOverlap.OffsetHigh = 0;
PollingOverlap.hEvent = CreateEvent(NULL,TRUE,FALSE,NULL);
while(result)
{
result = ReadDirectoryChangesW(
DirInfo[0].hDir,// handle to the directory to be watched
&buf,// pointer to the buffer to receive the read results
sizeof(buf),// length of lpBuffer
TRUE,// flag for monitoring directory or directory tree
FILE_NOTIFY_CHANGE_FILE_NAME |
FILE_NOTIFY_CHANGE_DIR_NAME |
FILE_NOTIFY_CHANGE_SIZE,
//FILE_NOTIFY_CHANGE_LAST_WRITE |
//FILE_NOTIFY_CHANGE_LAST_ACCESS |
//FILE_NOTIFY_CHANGE_CREATION,
&nRet,// number of bytes returned
&PollingOverlap,// pointer to structure needed for overlapped I/O
NULL);
WaitForSingleObject(PollingOverlap.hEvent,INFINITE);
offset = 0;
int rename = 0;
char oldName[260];
char newName[260];
do
{
pNotify = (FILE_NOTIFY_INFORMATION*)((char*)buf + offset);
strcpy(filename, "");
int filenamelen = WideCharToMultiByte(CP_ACP, 0, pNotify->FileName, pNotify->FileNameLength/2, filename, sizeof(filename), NULL, NULL);
filename[pNotify->FileNameLength/2] = '';
switch(pNotify->Action)
{
case FILE_ACTION_ADDED:
printf("\nThe file is added to the directory: [%s] \n", filename);
break;
case FILE_ACTION_REMOVED:
printf("\nThe file is removed from the directory: [%s] \n", filename);
break;
case FILE_ACTION_MODIFIED:
printf("\nThe file is modified. This can be a change in the time stamp or attributes: [%s]\n", filename);
break;
case FILE_ACTION_RENAMED_OLD_NAME:
printf("\nThe file was renamed and this is the old name: [%s]\n", filename);
break;
case FILE_ACTION_RENAMED_NEW_NAME:
printf("\nThe file was renamed and this is the new name: [%s]\n", filename);
break;
default:
printf("\nDefault error.\n");
break;
}
offset += pNotify->NextEntryOffset;
}while(pNotify->NextEntryOffset); //(offset != 0);
}
CloseHandle( DirInfo[0].hDir );
}
主線程可以創建OVERLAPPED
結構並將其提供給線程使用,而不是相反。 但是,無論哪種方式,嘗試從主線程取消 I/O 都將是一種競爭條件。 由於您的工作線程必須在每個目錄事件之后對ReadDirectoryChangesEx()
進行新調用,因此當主線程希望工作線程終止時,它可能在對ReadDirectoryChangesEx()
的調用之間,因此在沒有 I/ 時調用CancelIoEx()
O in progress 將是一個空操作。
相反,除了要為 I/O 創建的事件 object 之外,還要創建另一個事件 object供主線程和工作線程共享。 使用WaitForMultipleObjects()
讓工作線程同時等待兩個事件,然后主線程可以在希望工作線程終止時發出共享事件的信號。
WaitForMultipleObjects()
將告訴工作線程哪個事件發出信號。 如果共享事件發出信號,工作線程可以在退出之前通過CancelIo/Ex()
取消其正在進行的 I/O。
// shared with both threads...
HANDLE hTermEvent = CreateEvent(NULL, TRUE, FALSE, NULL);
// in main thread...
HANDLE hWorkerThread = CreateThread(...);
...
SetEvent(hTermEvent);
WaitForSingleObject(hWorkerThread, INFINITE);
// called by worker thread...
void WatchDirectory(LPCWSTR path)
{
DWORD buf[512];
DWORD nRet, dwRet;
char filename[MAX_PATH];
DirInfo[0].hDir = CreateFile(path, GENERIC_READ | FILE_LIST_DIRECTORY,
FILE_SHARE_READ | FILE_SHARE_WRITE | FILE_SHARE_DELETE,
NULL, OPEN_EXISTING, FILE_FLAG_BACKUP_SEMANTICS | FILE_FLAG_OVERLAPPED,
NULL);
if (DirInfo[0].hDir == INVALID_HANDLE_VALUE)
{
return; //cannot open folder
}
lstrcpy(DirInfo[0].lpszDirName, path);
OVERLAPPED PollingOverlap = {};
PollingOverlap.hEvent = CreateEvent(NULL, TRUE, FALSE, NULL);
if (!PollingOverlap.hEvent)
{
return; //cannot create I/O event to wait on
}
FILE_NOTIFY_INFORMATION* pNotify;
int offset;
do
{
if (!ReadDirectoryChangesW(
DirInfo[0].hDir,// handle to the directory to be watched
&buf,// pointer to the buffer to receive the read results
sizeof(buf),// length of lpBuffer
TRUE,// flag for monitoring directory or directory tree
FILE_NOTIFY_CHANGE_FILE_NAME |
FILE_NOTIFY_CHANGE_DIR_NAME |
FILE_NOTIFY_CHANGE_SIZE,
//FILE_NOTIFY_CHANGE_LAST_WRITE |
//FILE_NOTIFY_CHANGE_LAST_ACCESS |
//FILE_NOTIFY_CHANGE_CREATION,
&nRet,// number of bytes returned
&PollingOverlap,// pointer to structure needed for overlapped I/O
NULL))
{
break; // can't wait for an event
}
HANDLE events[] = {hTermEvent, PollingOverlap.hEvent};
dwRet = WaitForMultipleObjects(2, events, FALSE, INFINITE);
if (dwRet != (WAIT_OBJECT_0 + 1))
{
CancelIo(DirInfo[0].hDir);
GetOverlappedResult(DirInfo[0].hDir, &PollingOverlap, &nRet, TRUE);
break; // terminate requested, or wait failed
}
if (!GetOverlappedResult(DirInfo[0].hDir, &PollingOverlap, &nRet, TRUE))
{
break; // read failed
}
if (nRet == 0)
{
continue; // overflow, current event data discarded
}
offset = 0;
int rename = 0;
char oldName[MAX_PATH];
char newName[MAX_PATH];
do
{
pNotify = (FILE_NOTIFY_INFORMATION*) (buf + offset);
int filenamelen = WideCharToMultiByte(CP_ACP, 0, pNotify->FileName, pNotify->FileNameLength/2, filename, sizeof(filename), NULL, NULL);
switch (pNotify->Action)
{
case FILE_ACTION_ADDED:
printf("\nThe file is added to the directory: [%.*s] \n", filenamelen, filename);
break;
case FILE_ACTION_REMOVED:
printf("\nThe file is removed from the directory: [%.*s] \n", filenamelen, filename);
break;
case FILE_ACTION_MODIFIED:
printf("\nThe file is modified. This can be a change in the time stamp or attributes: [%.*s]\n", filenamelen, filename);
break;
case FILE_ACTION_RENAMED_OLD_NAME:
printf("\nThe file was renamed and this is the old name: [%.*s]\n", filenamelen, filename);
break;
case FILE_ACTION_RENAMED_NEW_NAME:
printf("\nThe file was renamed and this is the new name: [%.*s]\n", filenamelen, filename);
break;
default:
printf("\nDefault error.\n");
break;
}
offset += pNotify->NextEntryOffset;
}
while (pNotify->NextEntryOffset);
}
while (true);
CloseHandle(PollingOverlap.hEvent);
CloseHandle(DirInfo[0].hDir);
}
終止線程永遠不安全。 這導致資源泄漏的程度如何。 和 main - 您永遠無法知道線程在何時終止。 例如,它可以在堆分配/釋放臨界區內。 並在此時終止它會導致下一次堆操作死鎖(因為它的臨界區永遠不會釋放)。
但是存在許多正確的解決方案,如何停止 I/O。 當然可以使用評論中已經描述的2個特殊事件,但我認為這不是最好的解決方案
1)我們可以在文件句柄上使用CancelIoEx
。 當然僅僅調用CancelIoEx
是不夠的——因為此時在專用線程中可能沒有 I/O 活動。 還需要使用特殊標志( _bQuit
)來取消任務,但這還不夠。 需要在關鍵部分檢查/設置此標志或使用ReadDirectoryChangesW/CancelIoEx
進行故障保護
在專用線程中
AcquireSRWLockExclusive(this);
if (!_bQuit) // (1)
{
ReadDirectoryChangesW(*); // (4)
}
ReleaseSRWLockExclusive(this);
並停止
AcquireSRWLockExclusive(this);
_bQuit = true; // (2)
CancelIoEx(*); (3)
ReleaseSRWLockExclusive(this);
沒有關鍵部分或損壞保護將可能按下一個順序執行:
if (!_bQuit) // (1)
_bQuit = true; // (2)
CancelIoEx(*); (3)
ReadDirectoryChangesW(*); // (4)
可能是工作線程首先檢查標志 _bQuit 並且它仍然為假的情況。 然后主線程設置標志並調用CancelIoEx
這將無效,因為文件上沒有 I/O。 只有這樣工作的線程調用ReadDirectoryChangesW
才會被取消。 但是通過使用臨界區(廣義上),我們使這成為不可能。 所以可能只有 2 個訂單:或
if (!_bQuit) ReadDirectoryChangesW(*); // (1)
_bQuit = true; CancelIoEx(*); // (2)
在這種情況下, ReadDirectoryChangesW
將被CancelIoEx
取消
或者
_bQuit = true; CancelIoEx(*); // (1)
if (!_bQuit) ReadDirectoryChangesW(*); // (2)
在這種情況下,工作線程視圖_bQuit
標志設置,而不是調用ReadDirectoryChangesW
更多。
在完整的代碼中,這看起來像:
inline ULONG BOOL_TO_ERROR(BOOL f)
{
return f ? NOERROR : GetLastError();
}
struct WatchFolder : SRWLOCK
{
HANDLE _hThread, _hFile;
BOOLEAN _bQuit;
WatchFolder() : _hThread(0), _hFile(0), _bQuit(false)
{
InitializeSRWLock(this);
}
~WatchFolder()
{
if (_hThread) {
WaitForSingleObject(_hThread, INFINITE);
CloseHandle(_hThread);
}
if (_hFile) CloseHandle(_hFile);
}
static ULONG CALLBACK _WatchDirectory(PVOID This)
{
reinterpret_cast<WatchFolder*>(This)->WatchDirectory();
return 0;
}
void WatchDirectory()
{
OVERLAPPED ov {};
if (ov.hEvent = CreateEvent(0, 0, 0, 0))
{
union {
FILE_NOTIFY_INFORMATION fni;
char buf[0x800];// must be aligned as FILE_NOTIFY_INFORMATION
};
for(;;)
{
AcquireSRWLockExclusive(this);
ULONG dwError = _bQuit ? ERROR_OPERATION_ABORTED : BOOL_TO_ERROR(
ReadDirectoryChangesW(_hFile, buf, sizeof(buf), TRUE, FILE_NOTIFY_VALID_MASK, 0, &ov, 0));
ReleaseSRWLockExclusive(this);
ULONG NumberOfBytesTransferred = 0;
if (dwError == NOERROR)
{
dwError = BOOL_TO_ERROR(GetOverlappedResult(_hFile, &ov, &NumberOfBytesTransferred, TRUE));
}
if (dwError || !NumberOfBytesTransferred)
{
if (dwError != ERROR_OPERATION_ABORTED)
{
__nop();
}
break;
}
FILE_NOTIFY_INFORMATION* pNotify = &fni;
ULONG NextEntryOffset = 0;
do
{
(PBYTE&)pNotify += NextEntryOffset;
DbgPrint("%x %.*S\n", pNotify->Action, pNotify->FileNameLength / sizeof(WCHAR), pNotify->FileName);
} while (NextEntryOffset = pNotify->NextEntryOffset);
}
CloseHandle(ov.hEvent);
}
}
ULONG Start(PCWSTR szFile)
{
HANDLE hFile = CreateFileW(szFile, FILE_GENERIC_READ, FILE_SHARE_VALID_FLAGS,
NULL, OPEN_EXISTING, FILE_FLAG_BACKUP_SEMANTICS|FILE_FLAG_OVERLAPPED, NULL);
ULONG dwError;
if (hFile != INVALID_HANDLE_VALUE)
{
if (_hThread = CreateThread(0, 0, _WatchDirectory, this, 0, 0))
{
_hFile = hFile;
return NOERROR;
}
dwError = GetLastError();
CloseHandle(hFile);
}
else
{
dwError = GetLastError();
}
return dwError;
}
void Stop()
{
AcquireSRWLockExclusive(this);
_bQuit = true, CancelIoEx(_hFile, 0);
ReleaseSRWLockExclusive(this);
}
};
void test()
{
WatchFolder wf;
if (wf.Start(L"somepath") == NOERROR)
{
MessageBoxW(0,0,0,0);
wf.Stop();
}
}
2) 另一種方法是簡單地調用CloseHandle(_hFile)
而不是CancelIoEx(_hFile, 0);
. 當句柄(最后一個,但假設您只有一個句柄)關閉時 - 系統結束完成ReadDirectoryChangesW
狀態STATUS_NOTIFY_CLEANUP
。 代碼將與CancelIoEx
非常相似,只是現在終止時的錯誤將是ERROR_NOTIFY_CLEANUP
而不是ERROR_OPERATION_ABORTED
。 但如果使用GetOverlappedResult[Ex]
存在問題 - 此 api 在實施中有錯誤 - 它丟失了所有正狀態值。 它只是丟失了STATUS_NOTIFY_CLEANUP
(但我們當然可以在OVERLAPPED
的Internal
字段中查看它。代碼可以是下一個:
AcquireSRWLockExclusive(this);
ULONG dwError = _bQuit ? ERROR_NOTIFY_CLEANUP : BOOL_TO_ERROR(
ReadDirectoryChangesW(_hFile, buf, sizeof(buf), TRUE, FILE_NOTIFY_VALID_MASK, 0, &ov, 0));
ReleaseSRWLockExclusive(this);
ULONG NumberOfBytesTransferred = 0;
if (dwError == NOERROR)
{
dwError = BOOL_TO_ERROR(GetOverlappedResult(_hFile, &ov, &NumberOfBytesTransferred, TRUE));
// fix for error in GetOverlappedResult
if (dwError == NOERROR && ov.Internal) dwError = RtlNtStatusToDosError((NTSTATUS)ov.Internal);
}
if (dwError || !NumberOfBytesTransferred)
{
if (dwError != ERROR_NOTIFY_CLEANUP)
{
__nop();
}
break;
}
並停止
AcquireSRWLockExclusive(this);
_bQuit = true, CloseHandle(_hFile), _hFile = 0;
ReleaseSRWLockExclusive(this);
3) 否則一個選項在GetOverlappedResultEx
內使用警報等待並插入 apc(或向工作線程發出警報)。 在這種情況下,我們不需要使用關鍵部分/或損壞保護 - 因為無論是在調用ReadDirectoryChangesW
之前還是之后插入 apc(或警報) - 它無論如何都會中斷等待。
ULONG dwError = _bQuit ? STATUS_USER_APC : BOOL_TO_ERROR(
ReadDirectoryChangesW(_hFile, buf, sizeof(buf), TRUE, FILE_NOTIFY_VALID_MASK, 0, &ov, 0));
ULONG NumberOfBytesTransferred = 0;
if (dwError == NOERROR)
{
dwError = BOOL_TO_ERROR(GetOverlappedResultEx(_hFile, &ov, &NumberOfBytesTransferred, INFINITE, TRUE));
}
if (dwError || !NumberOfBytesTransferred)
{
if (dwError == STATUS_USER_APC)
{
CancelIo(_hFile);
GetOverlappedResult(_hFile, &ov, &NumberOfBytesTransferred, TRUE);
}
break;
}
我們需要停下來
static VOID NTAPI dummyAPC(_In_ ULONG_PTR )
{
}
_bQuit = true;
QueueUserAPC(dummyAPC, _hThread, 0);
當然,改為調用dummyAPC
(不需要)更好地使用警報,但 GetOverlappedResultEx (更確切地說是WaitForSingleObjectEx
)忽略STATUS_ALERT
並在它被STATUS_ALERT
中斷后再次開始等待。 所以需要在這里使用自定義代碼
ULONG
WINAPI
GetOverlappedResult2( _In_ LPOVERLAPPED lpOverlapped,
_Out_ PULONG_PTR lpNumberOfBytesTransferred)
{
while (lpOverlapped->Internal == STATUS_PENDING)
{
if (NTSTATUS status = ZwWaitForSingleObject(lpOverlapped->hEvent, TRUE, 0))
{
return RtlNtStatusToDosError(status);
}
}
KeMemoryBarrier();
*lpNumberOfBytesTransferred = lpOverlapped->InternalHigh;
return RtlNtStatusToDosError((NTSTATUS)lpOverlapped->Internal);
}
並可以使用下一個代碼:
ULONG dwError = _bQuit ? ERROR_ALERTED : BOOL_TO_ERROR(
ReadDirectoryChangesW(_hFile, buf, sizeof(buf), TRUE, FILE_NOTIFY_VALID_MASK, 0, &ov, 0));
ULONG_PTR NumberOfBytesTransferred = 0;
if (dwError == NOERROR)
{
dwError = GetOverlappedResult2(&ov, &NumberOfBytesTransferred);
}
if (dwError || !NumberOfBytesTransferred)
{
if (dwError == ERROR_ALERTED)
{
CancelIo(_hFile);
GetOverlappedResult(_hFile, &ov, (ULONG*)&NumberOfBytesTransferred, TRUE);
}
break;
}
並停止
_bQuit = true;
NtAlertThread(_hThread);
4)但是我選擇的最佳方式 - 不完全使用專用線程,而是使用完整的異步 I/O。 代碼示例
struct WatchFolderCB : SRWLOCK, OVERLAPPED
{
HANDLE _hFile;
LONG _dwRefCount;
union {
FILE_NOTIFY_INFORMATION fni;
char buf[0x800];// must be aligned as FILE_NOTIFY_INFORMATION
};
BOOLEAN _bQuit;
void AddRef()
{
InterlockedIncrementNoFence(&_dwRefCount);
}
void Release()
{
if (!InterlockedDecrement(&_dwRefCount))
{
delete this;
}
}
WatchFolderCB() : _hFile(0), _bQuit(false), _dwRefCount(1)
{
InitializeSRWLock(this);
RtlZeroMemory(static_cast<OVERLAPPED*>(this), sizeof(OVERLAPPED));
}
~WatchFolderCB()
{
if (_hFile) CloseHandle(_hFile);
}
static VOID WINAPI _IoCompletionCallback(
_In_ DWORD dwErrorCode,
_In_ DWORD dwNumberOfBytesTransfered,
_Inout_ LPOVERLAPPED lpOverlapped
)
{
static_cast<WatchFolderCB*>(lpOverlapped)->IoCompletionCallback(
RtlNtStatusToDosError(dwErrorCode), dwNumberOfBytesTransfered);
}
VOID IoCompletionCallback(DWORD dwErrorCode, DWORD NumberOfBytesTransferred)
{
if (dwErrorCode || !NumberOfBytesTransferred)
{
if (dwErrorCode != ERROR_NOTIFY_CLEANUP)
{
__nop();
}
}
else
{
FILE_NOTIFY_INFORMATION* pNotify = &fni;
ULONG NextEntryOffset = 0;
do
{
(PBYTE&)pNotify += NextEntryOffset;
DbgPrint("%x %.*S\n", pNotify->Action, pNotify->FileNameLength / sizeof(WCHAR), pNotify->FileName);
} while (NextEntryOffset = pNotify->NextEntryOffset);
ReadChanges();
}
Release();
}
void ReadChanges()
{
AddRef();
AcquireSRWLockExclusive(this);
ULONG dwError = _bQuit ? ERROR_NOTIFY_CLEANUP : BOOL_TO_ERROR(
ReadDirectoryChangesW(_hFile, buf, sizeof(buf), TRUE, FILE_NOTIFY_VALID_MASK, 0, this, 0));
ReleaseSRWLockExclusive(this);
if (dwError)
{
IoCompletionCallback(dwError, 0);
}
}
ULONG Start(PCWSTR szFile)
{
HANDLE hFile = CreateFileW(szFile, FILE_GENERIC_READ, FILE_SHARE_VALID_FLAGS,
NULL, OPEN_EXISTING, FILE_FLAG_BACKUP_SEMANTICS|FILE_FLAG_OVERLAPPED, NULL);
ULONG dwError;
if (hFile != INVALID_HANDLE_VALUE)
{
if (BindIoCompletionCallback(hFile, _IoCompletionCallback, 0))
{
_hFile = hFile;
ReadChanges();
return NOERROR;
}
dwError = GetLastError();
CloseHandle(hFile);
}
else
{
dwError = GetLastError();
}
return dwError;
}
void Stop()
{
AcquireSRWLockExclusive(this);
_bQuit = true, CloseHandle(_hFile), _hFile = 0;
ReleaseSRWLockExclusive(this);
}
};
void test1()
{
if (WatchFolderCB* p = new WatchFolderCB)
{
if (p->Start(L"*") == NOERROR)
{
MessageBoxW(0,0,0,0);
p->Stop();
}
p->Release();
}
}
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.