6 Feb
2025
6 Feb
'25
12:36 p.m.
On Thu Feb 6 12:31:02 2025 +0000, Alfred Agrell wrote:
Nope, needs to be duplicated. https://docs.kernel.org/next/userspace-api/ntsync.html#char-device
Each file description opened on the device represents a unique
instance intended to back an individual NT virtual machine. Objects created by one ntsync instance may only be used with other objects created by the same instance.
I see, well one more reason to introduce it first and cache it in clients then because otherwise it's incorrect until it is kept referenced.
And if it needs to stay alive for all prefix lifetime, instead of relying on clients leaking their handle, the object should probably be created on wineserver startup and be made permanent.