Re: [PATCH v32 0/4] MR6315: plugplay: Rework how PnP notifications are sent over RPC to support DBT_DEVTYP_HANDLE events.

[Vibhav Pant (＠vibhavp)]

On Thu Aug 29 16:19:09 2024 +0000, Elizabeth Figura wrote:
> Actually, I'm a bit confused, because now I'm not sure where RPC does do
> that? I was assuming it was a user-marshalled type which implicitly
> calls DuplicateHandle(), but that's not the case.
> The lack of tests in this patch set is a little disturbing. Is it
> possible to test this behaviour? I don't know under what circumstances
> handle events are sent [and I can't easily find anyone successfully
> using DBT_DEVTYP_HANDLE online]. We do have support for testing PnP
> drivers, though, if that's necessary; see dlls/ntoskrnl.exe/tests/driver_pnp.c.
> @zfigura Testing it is tricky. My plan was to utilize it in the bluetooth driver by directly calling `plugplay_send_event` from the driver code itself, and I'm not sure what the equivalent of that would be in Windows.

@rbernon I'm okay with using reserved as an offset to pass the device path, but we'd still have to pass it for every message for filtering. I didn't want to utilize `reserved` mostly out of caution, if it ever turned out to be that the field did have some undocumented semantics after all.

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/6315#note_80493