Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: UwbConnector notification handler doesn't handle when driver closes the HANDLE #176

Open
abeltrano opened this issue Mar 28, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@abeltrano
Copy link
Contributor

Describe the bug
When the driver closes a file HANDLE, the UwbConnector continues looping forever trying to issue the DeviceIoControl call.

Steps To Reproduce
Start a session with nocli, then forcibly unload the driver.

Expected behavior
UwbConnector::HandleNotifications should properly handle the return value E_INVALID_HANDLE. At minimum, it must discard the current HANDLE it is using.

Actual behavior
UwbConnector::HandleNotifications loops forever, repeatedly calling DeviceIoControl with an invalid HANDLE.

@abeltrano abeltrano added the bug Something isn't working label Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant