From: Thomas Gleixner <tglx@linutronix.de>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Ingo Molnar <mingo@kernel.org>, Andrei Vagin <avagin@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Dmitry Safonov <dsafonov@virtuozzo.com>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Andy Lutomirski <luto@kernel.org>,
Thomas Garnier <thgarnie@google.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel
Date: Tue, 21 Mar 2017 13:49:12 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703211339200.3617@nanos> (raw)
In-Reply-To: <20170321075934.o4sccpawzn4rmtvh@angband.pl>
On Tue, 21 Mar 2017, Adam Borowski wrote:
> On Tue, Mar 21, 2017 at 07:45:39AM +0100, Ingo Molnar wrote:
> > * Andrei Vagin <avagin@gmail.com> wrote:
> >
> > > # first bad commit: [45fc8757d1d2128e342b4e7ef39adedf7752faac] x86:
> > > Make the GDT remapping read-only on 64-bit
> >
> > Just wondering, does the following commit fix it:
> >
> > 5b781c7e317f x86/tls: Forcibly set the accessed bit in TLS segments
>
> It does fix i386 but not x32.
>
> By "x32" I mean CONFIG_X86_X32, by "i386" CONFIG_IA32_EMULATION, contrary to
> Andrei's first report. The naming of the new ABI wasn't too fortunate...
The X32 issue is unrelated to the GDT mapping.
What happens is that the mmap rework from Dmitry switched X32 to use 64bit
mappings, which is wrong. X32 has 64bit instructions and syscalls and 32bit
address space.
Dmitry, can you please have a look and fix that up? For reproduction just
compile helloworld.c with gcc -mx32.
Thanks,
tglx
next prev parent reply other threads:[~2017-03-21 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 23:57 linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel Andrei Vagin
2017-03-21 1:32 ` Adam Borowski
2017-03-21 5:17 ` Andrei Vagin
2017-03-21 6:45 ` Ingo Molnar
2017-03-21 7:59 ` Adam Borowski
2017-03-21 12:49 ` Thomas Gleixner [this message]
2017-03-21 12:50 ` Dmitry Safonov
2017-03-21 15:59 ` Dmitry Safonov
2017-03-21 16:28 ` Andy Lutomirski
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=alpine.DEB.2.20.1703211339200.3617@nanos \
--to=tglx@linutronix.de \
--cc=avagin@gmail.com \
--cc=dsafonov@virtuozzo.com \
--cc=gorcunov@openvz.org \
--cc=hpa@zytor.com \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=thgarnie@google.com \
/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