process does not exit when accessing dokan drive

[hbzhang3]

Check List

• [Y] I checked my issue doesn't exist yet
• [Y] My issue is valid with mirror default sample and not specific to my user-mode driver implementation
• [Y] I can always reproduce the issue with the provided description below.
• [Y] I have updated Dokany to the latest version and have reboot my computer after.
• [] I tested one of the last snapshot from appveyor CI

Describe the bug
it looks like something is wrong with cancelling IRP when process exits

To Reproduce
Steps to reproduce the behavior:

1. make sure dokan device name is \Device\Volume{d6cc17c5-1734-4085-bce7-964f1e9f5de9}, otherwise modify windowsproject1 source codes accordingly
2. run attached windowsproject1.exe, which creates 10 child processes, each child process tries to open a non-existing file on dokan drive repeatedly for 2 seconds, then exits and restarts.
3. after 2 or 3 minutes, terminate parent windowsproject1.exe process.

Expected: all child processes are terminated successfully
Actual: some child processes stay in process list and do not exit, procexp shows these processes have one thread running and cannot be terminated

Logs
N/A

Environment:

• Windows version: Windows 11 25H2
• Processor architecture: AMD x64
• Dokany version: 2.3.1.1000
• Library type (Dokany/FUSE):

Additional context
windowsproject1 source codes and executable:
https://1drv.ms/u/c/01cff2ee4af3350f/IQCRZVqJNMK_Q6LCi3UNX7vRAW7ODznisgQQuYbIZBCOHYk?e=djUY9T
claude code fix:
https://1drv.ms/u/c/01cff2ee4af3350f/IQDfyvyw_EK4TLY88ABs3omwAdGNXa5A5hORRFeLbqkEPCI?e=CzMXgm

[Liryna]

Hey @hbzhang3

Thank you for sharing the code to reproduce and a possible fix! Could you please open a pull request to allow the CI to test it? That would be highly appreciated

[hbzhang3]

im not sure if cc fix is all good, pls review and push fix from your side. credit to cc :)

[Liryna]

cc was good 👍 but we can improve the patch by reordering how the context was set with the cancel. See f8a542a
Are you able to rebuild the driver on your side and confirm it fixes your case ?

[hbzhang3]

i verified your fix, it solves the problem.