From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: tigran@veritas.com, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] fix x86 microcode driver handling of multiple matching revisions
Date: Thu, 4 May 2006 10:09:40 -0700 [thread overview]
Message-ID: <20060504100940.A2571@unix-os.sc.intel.com> (raw)
In-Reply-To: <444F9D34.76E4.0078.0@novell.com>; from jbeulich@novell.com on Wed, Apr 26, 2006 at 04:17:56PM +0200
On Wed, Apr 26, 2006 at 04:17:56PM +0200, Jan Beulich wrote:
> @@ -197,21 +202,33 @@ static inline void mark_microcode_update
> pr_debug(" Checksum 0x%x\n", cksum);
>
> if (mc_header->rev < uci->rev) {
> - printk(KERN_ERR "microcode: CPU%d not 'upgrading' to earlier revision"
> - " 0x%x (current=0x%x)\n", cpu_num, mc_header->rev, uci->rev);
> - goto out;
> + if (uci->err == MC_NOTFOUND) {
> + uci->err = MC_IGNORED;
> + uci->cksum = mc_header->rev;
> + } else if (uci->err == MC_IGNORED && uci->cksum < mc_header->rev)
> + uci->cksum = mc_header->rev;
> } else if (mc_header->rev == uci->rev) {
> - /* notify the caller of success on this cpu */
> - uci->err = MC_SUCCESS;
> - goto out;
> + if (uci->err < MC_MARKED) {
> + /* notify the caller of success on this cpu */
> + uci->err = MC_SUCCESS;
> + }
> + } else if (uci->err != MC_ALLOCATED || mc_header->rev > uci->mc->hdr.rev) {
> + pr_debug("microcode: CPU%d found a matching microcode update with "
> + " revision 0x%x (current=0x%x)\n", cpu_num, mc_header->rev, uci->rev);
> + uci->cksum = cksum;
> + uci->pf = pf; /* keep the original mc pf for cksum calculation */
> + uci->err = MC_MARKED; /* found the match */
> + for_each_online_cpu(cpu_num) {
> + if (ucode_cpu_info[cpu_num].mc == uci->mc) {
> + uci->mc = NULL;
> + break;
> + }
Isn't there a memory leak here? Shouldn't this be
for_each_online_cpu(cpu) {
if (cpu == cpu_num)
continue;
if (ucode_cpu_info[cpu].mc == uci->mc) {
uci->mc = NULL;
break;
}
}
thanks,
suresh
> + }
> + if (uci->mc != NULL) {
> + vfree(uci->mc);
> + uci->mc = NULL;
> + }
next prev parent reply other threads:[~2006-05-04 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 14:17 [PATCH] fix x86 microcode driver handling of multiple matching revisions Jan Beulich
2006-05-04 7:28 ` Tigran Aivazian
2006-05-04 8:00 ` Jan Beulich
2006-05-05 7:55 ` Tigran Aivazian
2006-05-04 17:09 ` Siddha, Suresh B [this message]
2006-05-05 6:50 ` Jan Beulich
2006-05-05 11:26 ` [PATCH, updated] " Jan Beulich
2006-05-06 20:26 ` Tigran Aivazian
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=20060504100940.A2571@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@osdl.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.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 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.