ACPICA: events/evxfregn: don't release the ContextMutex that was never acquired

BugLink: https://bugs.launchpad.net/bugs/2102181

[ Upstream commit c53d96a4481f42a1635b96d2c1acbb0a126bfd54 ]

This bug was first introduced in c27f3d011b, where the author of the
patch probably meant to do DeleteMutex instead of ReleaseMutex. The
mutex leak was noticed later on and fixed in e4dfe10837, but the bogus
MutexRelease line was never removed, so do it now.

Link: https://github.com/acpica/acpica/pull/982
Fixes: c27f3d011b ("ACPICA: Fix race in generic_serial_bus (I2C) and GPIO op_region parameter handling")
Signed-off-by: Daniil Tatianin <d-tatianin@yandex-team.ru>
Link: https://patch.msgid.link/20241122082954.658356-1-d-tatianin@yandex-team.ru
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Signed-off-by: Koichiro Den <koichiro.den@canonical.com>
Signed-off-by: Mehmet Basaran <mehmet.basaran@canonical.com>

This commit is contained in:

Daniil Tatianin

2025-03-13 13:21:44 +09:00

committed by

Mehmet Basaran

parent 1bfaa2978d

commit e88351c222

1 changed files with 0 additions and 2 deletions

									
										drivers/acpi/acpica/evxfregn.c
									
		-2
	
												View File
												
				@@ -232,8 +232,6 @@ acpi_remove_address_space_handler(acpi_handle device,

							/* Now we can delete the handler object */

							acpi_os_release_mutex(handler_obj->address_space.

									      context_mutex);

							acpi_ut_remove_reference(handler_obj);

							goto unlock_and_exit;

						}