[reactos] 05/15: [COMPBATT] Assign a memory allocation tag for the I/O remove lock

[George Bișoc]

https://git.reactos.org/?p=reactos.git;a=commitdiff;h=28bb8c6ff7b82b8216dfa…

commit 28bb8c6ff7b82b8216dfa6bfb052f1d169959062
Author:     George Bișoc <george.bisoc(a)reactos.org>
AuthorDate: Sat Dec 14 21:52:24 2024 +0100
Commit:     George Bișoc <george.bisoc(a)reactos.org>
CommitDate: Wed Jan 8 23:20:07 2025 +0100

    [COMPBATT] Assign a memory allocation tag for the I/O remove lock
    
    IoInitializeRemoveLock expects an allocation tag to be provided when it allocates
debug data in the kernel.
    Passing 0 leads to a bunch of ASSERTs in the kernel as such data is allocated by
ExAllocatePoolWithTag of which a tag has to be supplied, it's not optional.
---
 drivers/bus/acpi/compbatt/comppnp.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/bus/acpi/compbatt/comppnp.c b/drivers/bus/acpi/compbatt/comppnp.c
index 7e8523537ae..31b05030b4f 100644
--- a/drivers/bus/acpi/compbatt/comppnp.c
+++ b/drivers/bus/acpi/compbatt/comppnp.c
@@ -177,7 +177,7 @@ CompBattAddNewBattery(
                     ExReleaseFastMutex(&DeviceExtension->Lock);
 
                     /* Initialize the work item and delete lock */
-                    IoInitializeRemoveLock(&BatteryData->RemoveLock, 0, 0, 0);
+                    IoInitializeRemoveLock(&BatteryData->RemoveLock, COMPBATT_TAG,
0, 0);
                     ExInitializeWorkItem(&BatteryData->WorkItem,
                                          (PVOID)CompBattMonitorIrpCompleteWorker,
                                          BatteryData);