Re: [tip:x86/boot] x86/mm: Enable KASLR for physical mapping memory regions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/boot] x86/mm: Enable KASLR for physical mapping memory regions
- From: Borislav Petkov <bp@xxxxxxxxx>
- Date: Tue, 16 Aug 2016 15:42:05 +0200
- Cc: Baoquan He <bhe@xxxxxxxxxx>, Yinghai Lu <yinghai@xxxxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, Thomas Garnier <thgarnie@xxxxxxxxxx>, Andy Lutomirski <luto@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Alexander Kuleshov <kuleshovmail@xxxxxxxxx>, Josh Poimboeuf <jpoimboe@xxxxxxxxxx>, borntraeger@xxxxxxxxxx, sds@xxxxxxxxxxxxx, kirill.shutemov@xxxxxxxxxxxxxxx, jroedel@xxxxxxx, Kees Cook <keescook@xxxxxxxxxxxx>, "Williams, Dan J" <dan.j.williams@xxxxxxxxx>, Mark Salter <msalter@xxxxxxxxxx>, Borislav Petkov <bp@xxxxxxx>, Jonathan Corbet <corbet@xxxxxxx>, matt@xxxxxxxxxxxxxxxxxxx, guangrong.xiao@xxxxxxxxxxxxxxx, aneesh.kumar@xxxxxxxxxxxxxxxxxx, Ingo Molnar <mingo@xxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>, toshi.kani@xxxxxxx, alpopov@xxxxxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, Denys Vlasenko <dvlasenk@xxxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, dyoung@xxxxxxxxxx, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Dmitry Vyukov <dvyukov@xxxxxxxxxx>, lv.zheng@xxxxxxxxx, schwidefsky@xxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <CAMzpN2ixxOEonfgDdFRkB8P9Zb6eiFJF4Vx_HRMgWhm-7wK1hg@mail.gmail.com>
- References: <1466556426-32664-7-git-send-email-keescook@chromium.org> <tip-021182e52fe01c1f7b126f97fd6ba048dc4234fd@git.kernel.org> <CAMzpN2h-CV2e1F_8u5GYkwaFkzoERfi9a83DEO7OeKEJB0RYTg@mail.gmail.com> <20160814232657.GA10704@x1.redhat.com> <CAMzpN2ixxOEonfgDdFRkB8P9Zb6eiFJF4Vx_HRMgWhm-7wK1hg@mail.gmail.com>
- User-agent: Mutt/1.6.0 (2016-04-01)
On Tue, Aug 16, 2016 at 07:31:20AM -0400, Brian Gerst wrote:
> That didn't provide any useful information. However, when I boot with
> "nosmp", I do get an oops in load_microcode_amd(). I can't capture
> the oops message (no serial console), but it's being called from
> save_microcode_in_initrd_amd().
That is possible. KASLR already broke microcode loading on Intel. :-\
I'll try to reproduce and fix this at some point but am away currently
so don't hold your breath. Does "dis_ucode_ldr" on the kernel cmdline
get you any further?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
