linux-kernel - Re: [PATCH 1/1] x86/microcode: vsnprintf() might be unavailable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1433263793.26331.42.camel@linux.intel.com>
Date:	Tue, 02 Jun 2015 19:49:53 +0300
From:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:	Borislav Petkov <bp@...e.de>
Cc:	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] x86/microcode: vsnprintf() might be unavailable

On Tue, 2015-06-02 at 18:24 +0200, Borislav Petkov wrote:
> On Tue, Jun 02, 2015 at 05:56:43PM +0300, Andy Shevchenko wrote:
> > On Intel CPUs with x32 kernels we call load_builtin_intel_microcode() from
> > head_32.S on quite earlier stage. At that point sprintf() might be out of scope
> > to be called.
> 
> Hrrm, I don't get that. How can sprintf() be out of scope?

Initial paging setup is involved? I just sent a small update to previous
patch. Please, look at it.

> 
> Testing on 32-bit was successful here. How is x32 different?

Hmm… which Intel CPUs you run on?

Ah, one more thing we run our kernel from kexec (I hope it's not a case,
but who knows). 

> 
> Thanks.
> 


-- 
Andy Shevchenko <andriy.shevchenko@...el.com>
Intel Finland Oy

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/