From: John Garry <john.garry@huawei.com>
To: "Kaneda, Erik" <erik.kaneda@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
chenxiang <chenxiang66@hisilicon.com>
Subject: Re: [bug report] Memory leak from acpi_ev_install_space_handler()
Date: Wed, 19 May 2021 09:20:45 +0100 [thread overview]
Message-ID: <3ab18796-f8b5-9498-a31a-5dfd21059ebb@huawei.com> (raw)
In-Reply-To: <MWHPR11MB1599342DCB12AEA5B7DD0D54F02C9@MWHPR11MB1599.namprd11.prod.outlook.com>
On 18/05/2021 22:48, Kaneda, Erik wrote:
> Hi John,
>
>> I don't mind looking further if requested.
> Someone else reported this as well.
I noticed. By chance, it was my close colleague Xiang Chen.
Could you try the patch below? I think it might help fix this issue..
It looks like the same problem, and you provided the same solution, so
we can look to test it.
Thanks
>
> Thanks,
> Erik
>
> diff --git a/drivers/acpi/acpica/utdelete.c b/drivers/acpi/acpica/utdelete.c
> index 624a26794d55..e5ba9795ec69 100644
> --- a/drivers/acpi/acpica/utdelete.c
> +++ b/drivers/acpi/acpica/utdelete.c
> @@ -285,6 +285,14 @@ static void acpi_ut_delete_internal_obj(union acpi_operand_object *object)
> }
> break;
>
> + case ACPI_TYPE_LOCAL_ADDRESS_HANDLER:
> +
> + ACPI_DEBUG_PRINT((ACPI_DB_ALLOCATIONS,
> + "***** Address handler %p\n", object));
> +
> + acpi_os_delete_mutex(object->address_space.context_mutex);
> + break;
> +
> default:
>
> break;
>
prev parent reply other threads:[~2021-05-19 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 15:48 John Garry
2021-04-06 16:40 ` Rafael J. Wysocki
2021-04-06 16:48 ` John Garry
2021-05-18 21:48 ` Kaneda, Erik
2021-05-19 8:20 ` John Garry [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ab18796-f8b5-9498-a31a-5dfd21059ebb@huawei.com \
--to=john.garry@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=erik.kaneda@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®