From: Dave Jiang <dave.jiang@intel.com>
To: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, tglx@linutronix.de, hpa@zytor.com
Cc: linux-tip-commits@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: [tip:x86/urgent] x86/boot: Prevent KASLR and memmap collision
Date: Tue, 20 Dec 2016 11:23:51 -0700 [thread overview]
Message-ID: <1f20c79e-af1c-a15d-8076-e888fab81ff0@intel.com> (raw)
In-Reply-To: <20161220083118.GA810@gmail.com>
On 12/20/2016 01:31 AM, Ingo Molnar wrote:
>
> * tip-bot for Dave Jiang <tipbot@zytor.com> wrote:
>
>> Commit-ID: d1a5058c063d9e0aaaf4d360d0f8074ee55ed096
>> Gitweb: http://git.kernel.org/tip/d1a5058c063d9e0aaaf4d360d0f8074ee55ed096
>> Author: Dave Jiang <dave.jiang@intel.com>
>> AuthorDate: Tue, 29 Nov 2016 12:26:40 -0700
>> Committer: Thomas Gleixner <tglx@linutronix.de>
>> CommitDate: Mon, 19 Dec 2016 12:27:52 +0100
>>
>> x86/boot: Prevent KASLR and memmap collision
>
> This commit breaks the 32-bit build (allyesconfig32 and allmodconfig32):
>
> ld: -r and -shared may not be used together
> scripts/Makefile.build:293: recipe for target 'arch/x86/boot/compressed/kaslr.o' failed
> make[2]: *** [arch/x86/boot/compressed/kaslr.o] Error 1
> make[2]: *** Waiting for unfinished jobs....
>
> Thanks,
>
> Ingo
>
Looks like including lib/cmdline.c causes the issue. I'll need to find a
way around it.
prev parent reply other threads:[~2016-12-20 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 19:26 [PATCH v2] x86: fix kaslr and memmap collision Dave Jiang
2016-12-15 22:10 ` Dave Jiang
2016-12-19 11:33 ` [tip:x86/urgent] x86/boot: Prevent KASLR " tip-bot for Dave Jiang
2016-12-20 8:31 ` Ingo Molnar
2016-12-20 18:23 ` Dave Jiang [this message]
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=1f20c79e-af1c-a15d-8076-e888fab81ff0@intel.com \
--to=dave.jiang@intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).