mirror of
https://github.com/reactos/reactos.git
synced 2026-05-23 15:50:29 +08:00
ffc96d26ec
Dedicated to the hard work of Joachim Henze! xD This reverts part of commit043a98dd(see also commitb2aeafca). Contrary to what I assumed in commit043a98dd(and was also assumed in the older commitb2aeafca), we cannot use the singled-linked lists to queue and dequeue the PnP device-install events, because: - the events must be treated from the oldest to the newest ones, for consistency, otherwise this creates problems, as shown by e.g. CORE-16103; - the system singled-linked lists only offer access to the top of the list (like a stack) instead of to both the top and the bottom of the list, as would be required for a queue. Using the SLISTs would mean that only the newest-received events would be treated first, while the oldest (which were the first received) events would be treated last, and this is wrong. Therefore one must use e.g. the standard doubly-linked list. Also, using locked operations (insertion & removal) on the list of device-install events is necessary, because these operations are done concurrently by two different threads: PnpEventThread() and DeviceInstallThread(). Since the interlocked linked list functions are not available in user-mode, we need to use instead locking access through e.g. a mutex.