From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Sven Joachim <svenjoac@gmx.de>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Jiri Slaby <jslaby@suse.cz>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] objtool: fix build of 64-bit kernel with 32-bit userspace
Date: Mon, 27 Nov 2017 13:27:43 -0600 [thread overview]
Message-ID: <20171127192743.fjhgwq6ayohcnsaz@treble> (raw)
In-Reply-To: <87r2sjzkxr.fsf@turtle.gmx.de>
On Mon, Nov 27, 2017 at 06:32:48PM +0100, Sven Joachim wrote:
> On 2017-11-07 11:55 -0600, Josh Poimboeuf wrote:
>
> > [ Adding Ingo to cc because I believe it was his suggestion to hide the
> > guess unwinder behind CONFIG_EXPERT. ]
> >
> > On Mon, Nov 06, 2017 at 06:27:53PM -0500, Mikulas Patocka wrote:
> >> This patch fixes building of 64-bit kernel on 32-bit userspace (I tested
> >> it on RHEL-6-i686 and Debian-Sid-x32).
> >
> > Thanks, I'll review the patch.
>
> Any news on that? After upgrading to 4.15-rc1 and running
> "make oldconfig" I found out that the kernel would no longer build
> unless I selected CONFIG_UNWINDER_FRAME_POINTER=y.
>
> ,----
> | $ uname -m
> | x86_64
> | $ dpkg --print-architecture
> | i386
> `----
Sorry, I was traveling last week and I'm still getting caught up. I'll
take a look at it this week.
--
Josh
prev parent reply other threads:[~2017-11-27 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 23:27 [PATCH] objtool: fix build of 64-bit kernel with 32-bit userspace Mikulas Patocka
2017-11-07 17:55 ` Josh Poimboeuf
2017-11-07 21:25 ` Mikulas Patocka
2017-11-08 8:07 ` Peter Zijlstra
2017-11-27 17:32 ` Sven Joachim
2017-11-27 19:27 ` Josh Poimboeuf [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=20171127192743.fjhgwq6ayohcnsaz@treble \
--to=jpoimboe@redhat.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mpatocka@redhat.com \
--cc=peterz@infradead.org \
--cc=svenjoac@gmx.de \
--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 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.