From: "Chen, Gong" <gong.chen@linux.intel.com>
To: Joshua Hunt <johunt@akamai.com>
Cc: gong.chen@intel.com, linux-acpi@vger.kernel.org,
rjw@rjwysocki.net, lenb@kernel.org, ying.huang@intel.com,
tony.luck@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ACPI, APEI: Fix leaked resources
Date: Wed, 9 Mar 2016 09:11:29 +0800 [thread overview]
Message-ID: <20160309011129.GA19756@gchen-ros.bj.intel.com> (raw)
In-Reply-To: <1457452332-2673-2-git-send-email-johunt@akamai.com>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Tue, Mar 08, 2016 at 10:52:11AM -0500, Joshua Hunt wrote:
> Date: Tue, 8 Mar 2016 10:52:11 -0500
> From: Joshua Hunt <johunt@akamai.com>
> To: gong.chen@intel.com, linux-acpi@vger.kernel.org, rjw@rjwysocki.net,
> lenb@kernel.org, ying.huang@intel.com
> Cc: tony.luck@intel.com, linux-kernel@vger.kernel.org, Joshua Hunt
> <johunt@akamai.com>
> Subject: [PATCH v2 1/2] ACPI, APEI: Fix leaked resources
> X-Mailer: git-send-email 1.7.9.5
>
> We leak the NVS and arch resources (if used), in apei_resources_request.
> They are allocated to make sure we exclude them from the APEI resources,
> but they are never freed at the end of the function. Free them now.
>
> Signed-off-by: Josh Hunt <johunt@akamai.com>
>
Reviewed-by: Chen, Gong <gong.chen@linux.intel.com>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-09 1:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 15:52 [PATCH v2 0/2] ACPI, APEI: Memory leaks Joshua Hunt
2016-03-08 15:52 ` [PATCH v2 1/2] ACPI, APEI: Fix leaked resources Joshua Hunt
2016-03-09 1:11 ` Chen, Gong [this message]
2016-03-08 15:52 ` [PATCH v2 2/2] ACPI, APEI, ERST: Fixed leaked resources in erst_init Joshua Hunt
2016-03-09 1:12 ` Chen, Gong
2016-03-10 22:51 ` [PATCH v2 0/2] ACPI, APEI: Memory leaks Rafael J. Wysocki
2016-03-10 22:55 ` Luck, Tony
2016-03-10 23:17 ` 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=20160309011129.GA19756@gchen-ros.bj.intel.com \
--to=gong.chen@linux.intel.com \
--cc=gong.chen@intel.com \
--cc=johunt@akamai.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.com \
--cc=ying.huang@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