From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jesper Juhl <jj@chaosbits.net>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Len Brown <lenb@kernel.org>, Lin Ming <ming.m.lin@intel.com>,
Bob Moore <robert.moore@intel.com>
Subject: Re: [PATCH] ACPICA: Don't leak next_walk_state in acpi_ds_call_control_method()
Date: Thu, 25 Oct 2012 00:15:20 +0200 [thread overview]
Message-ID: <2295104.eQ6lcDpNzT@vostro.rjw.lan> (raw)
In-Reply-To: <alpine.LNX.2.00.1210212233180.26319@swampdragon.chaosbits.net>
On Sunday 21 of October 2012 22:35:46 Jesper Juhl wrote:
> If acpi_ds_create_walk_state() succeeds, but the call to
> ACPI_ALLOCATE_ZEROED() fails, then we'll return from the function
> without properly freeing 'next_walk_state'.
>
> Signed-off-by: Jesper Juhl <jj@chaosbits.net>
This has to go through ACPICA upstream, but we'll get it from there eventually.
Thanks,
Rafael
> ---
> drivers/acpi/acpica/dsmethod.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/acpi/acpica/dsmethod.c b/drivers/acpi/acpica/dsmethod.c
> index aa9a5d4..ade59a3 100644
> --- a/drivers/acpi/acpica/dsmethod.c
> +++ b/drivers/acpi/acpica/dsmethod.c
> @@ -378,7 +378,8 @@ acpi_ds_call_control_method(struct acpi_thread_state *thread,
> */
> info = ACPI_ALLOCATE_ZEROED(sizeof(struct acpi_evaluate_info));
> if (!info) {
> - return_ACPI_STATUS(AE_NO_MEMORY);
> + status = AE_NO_MEMORY;
> + goto cleanup;
> }
>
> info->parameters = &this_walk_state->operands[0];
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2012-10-24 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 20:35 [PATCH] ACPICA: Don't leak next_walk_state in acpi_ds_call_control_method() Jesper Juhl
2012-10-24 22:15 ` Rafael J. Wysocki [this message]
2008-11-25 13:42 ` Jesper Juhl
2012-10-28 21:08 ` Rafael J. Wysocki
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=2295104.eQ6lcDpNzT@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=jj@chaosbits.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).