From: walter harms <wharms@bfs.de>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>, Dan Carpenter <dan.carpenter@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] x86/microcode/intel: Improve microcode patches saving flow
Date: Fri, 25 Aug 2017 12:40:54 +0200 [thread overview]
Message-ID: <599FFEB6.4070707@bfs.de> (raw)
In-Reply-To: <20170825100456.n236w3jebteokfd6@pd.tnic>
Am 25.08.2017 12:04, schrieb Borislav Petkov:
> From: Borislav Petkov <bp@suse.de>
>
> Avoid potentially dereferencing a NULL pointer when saving a microcode
> patch for early loading on the application processors.
>
> While at it, drop the IS_ERR() checking in favor of simpler, NULL-ptr
> checks which are sufficient and rename __alloc_microcode_buf() to
> memdup_patch() to more precisely denote what it does.
>
> No functionality change.
>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> ---
> arch/x86/kernel/cpu/microcode/intel.c | 27 ++++++++++++++-------------
> 1 file changed, 14 insertions(+), 13 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/microcode/intel.c b/arch/x86/kernel/cpu/microcode/intel.c
> index 59edbe9d4ccb..8f7a9bbad514 100644
> --- a/arch/x86/kernel/cpu/microcode/intel.c
> +++ b/arch/x86/kernel/cpu/microcode/intel.c
> @@ -146,18 +146,18 @@ static bool microcode_matches(struct microcode_header_intel *mc_header,
> return false;
> }
>
> -static struct ucode_patch *__alloc_microcode_buf(void *data, unsigned int size)
> +static struct ucode_patch *memdup_patch(void *data, unsigned int size)
> {
> struct ucode_patch *p;
>
> p = kzalloc(sizeof(struct ucode_patch), GFP_KERNEL);
> if (!p)
> - return ERR_PTR(-ENOMEM);
> + return NULL;
>
> p->data = kmemdup(data, size, GFP_KERNEL);
> if (!p->data) {
> kfree(p);
> - return ERR_PTR(-ENOMEM);
> + return NULL;
> }
>
> return p;
> @@ -183,8 +183,8 @@ static void save_microcode_patch(void *data, unsigned int size)
> if (mc_hdr->rev <= mc_saved_hdr->rev)
> continue;
>
> - p = __alloc_microcode_buf(data, size);
> - if (IS_ERR(p))
> + p = memdup_patch(data, size);
> + if (!p)
> pr_err("Error allocating buffer %p\n", data);
> else
> list_replace(&iter->plist, &p->plist);
> @@ -196,24 +196,25 @@ static void save_microcode_patch(void *data, unsigned int size)
> * newly found.
> */
> if (!prev_found) {
> - p = __alloc_microcode_buf(data, size);
> - if (IS_ERR(p))
> + p = memdup_patch(data, size);
> + if (!p)
> pr_err("Error allocating buffer for %p\n", data);
> else
> list_add_tail(&p->plist, µcode_cache);
> }
>
> + if (!p)
> + return;
> +
just a bit nitpicking,
i would expect something like that:
p = memdup_patch(data, size);
if (!p) {
pr_err("Error allocating buffer for %p\n", data);
return;
}
list_add_tail(&p->plist, µcode_cache);
... because this is a normal pattern for OOF conditions and
everyone will ask "Why continue when there is no memory"
just my 2 cents
re,
wh
> /*
> * Save for early loading. On 32-bit, that needs to be a physical
> * address as the APs are running from physical addresses, before
> * paging has been enabled.
> */
> - if (p) {
> - if (IS_ENABLED(CONFIG_X86_32))
> - intel_ucode_patch = (struct microcode_intel *)__pa_nodebug(p->data);
> - else
> - intel_ucode_patch = p->data;
> - }
> + if (IS_ENABLED(CONFIG_X86_32))
> + intel_ucode_patch = (struct microcode_intel *)__pa_nodebug(p->data);
> + else
> + intel_ucode_patch = p->data;
> }
>
> static int microcode_sanity_check(void *mc, int print_err)
next prev parent reply other threads:[~2017-08-25 10:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170822211335.r7wcfcisdlq2xwgz@pd.tnic>
2017-08-24 20:15 ` [PATCH v2] x86/microcode: Silence a static checker warning Dan Carpenter
2017-08-24 20:47 ` Borislav Petkov
2017-08-24 20:55 ` Dan Carpenter
2017-08-24 20:58 ` Borislav Petkov
2017-08-24 21:08 ` Dan Carpenter
2017-08-24 21:12 ` Borislav Petkov
2017-08-25 9:06 ` Borislav Petkov
2017-08-25 9:12 ` Dan Carpenter
2017-08-25 9:14 ` Borislav Petkov
2017-08-25 10:04 ` [PATCH] x86/microcode/intel: Improve microcode patches saving flow Borislav Petkov
2017-08-25 10:40 ` walter harms [this message]
2017-08-25 11:41 ` Borislav Petkov
2017-08-29 9:03 ` [tip:x86/microcode] " tip-bot for Borislav Petkov
2017-08-24 21:02 ` [PATCH v2] x86/microcode: Silence a static checker warning Joe Perches
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=599FFEB6.4070707@bfs.de \
--to=wharms@bfs.de \
--cc=bp@alien8.de \
--cc=dan.carpenter@oracle.com \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox