From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: andrew.cooper3@citrix.com, jbeulich@suse.com, keir@xen.org
Cc: coverity@xenproject.org, xen-devel@lists.xen.org
Subject: Re: [PATCH 1/2] x86, amd_ucode: Fix coverity issues found in cpu_request_microcode()
Date: Wed, 30 Jul 2014 11:15:12 -0500 [thread overview]
Message-ID: <53D91A10.9010105@amd.com> (raw)
In-Reply-To: <1406736775-13247-1-git-send-email-aravind.gopalakrishnan@amd.com>
On 7/30/2014 11:12 AM, Aravind Gopalakrishnan wrote:
> This patch fixes issues found in CID 1229147(dead code) and
> CID 1229148: possible resource leak of mc_amd due to goto out
> statements.
>
> Reported-by: Andrew Cooper<andrew.cooper3@citrix.com>
> Signed-off-by: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
> ---
> xen/arch/x86/microcode_amd.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/xen/arch/x86/microcode_amd.c b/xen/arch/x86/microcode_amd.c
> index 14728a2..a2bdd20 100644
> --- a/xen/arch/x86/microcode_amd.c
> +++ b/xen/arch/x86/microcode_amd.c
> @@ -384,9 +384,12 @@ static int cpu_request_microcode(int cpu, const void *buf, size_t bufsize)
> while ( offset < bufsize )
> {
> error = install_equiv_cpu_table(mc_amd, buf, &offset);
> + if ( error ) {
Darn. I just noticed this. Will modify this.
I'll wait to see if there are more suggestions before I send a V2 for this.
- Aravind.
next prev parent reply other threads:[~2014-07-30 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 16:12 [PATCH 1/2] x86, amd_ucode: Fix coverity issues found in cpu_request_microcode() Aravind Gopalakrishnan
2014-07-30 16:15 ` Aravind Gopalakrishnan [this message]
2014-07-30 16:25 ` Andrew Cooper
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=53D91A10.9010105@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=coverity@xenproject.org \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.