Re: linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel

2017-03-21 Thread Dmitry Safonov
On 03/21/2017 03:50 PM, Dmitry Safonov wrote: On 03/21/2017 03:49 PM, Thomas Gleixner wrote: On Tue, 21 Mar 2017, Adam Borowski wrote: On Tue, Mar 21, 2017 at 07:45:39AM +0100, Ingo Molnar wrote: * Andrei Vagin wrote: # first bad commit: [45fc8757d1d2128e342b4e7ef39adedf7752faac] x86: Make

Re: linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel

2017-03-21 Thread Andy Lutomirski
On Tue, Mar 21, 2017 at 8:59 AM, Dmitry Safonov wrote: > On 03/21/2017 03:50 PM, Dmitry Safonov wrote: >> >> On 03/21/2017 03:49 PM, Thomas Gleixner wrote: >>> >>> On Tue, 21 Mar 2017, Adam Borowski wrote: On Tue, Mar 21, 2017 at 07:45:39AM +0100, Ingo Molnar wrote: > > * Andrei

Re: linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel

2017-03-21 Thread Dmitry Safonov
On 03/21/2017 03:49 PM, Thomas Gleixner wrote: On Tue, 21 Mar 2017, Adam Borowski wrote: On Tue, Mar 21, 2017 at 07:45:39AM +0100, Ingo Molnar wrote: * Andrei Vagin wrote: # first bad commit: [45fc8757d1d2128e342b4e7ef39adedf7752faac] x86: Make the GDT remapping read-only on 64-bit Just wo

Re: linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel

2017-03-21 Thread Thomas Gleixner
On Tue, 21 Mar 2017, Adam Borowski wrote: > On Tue, Mar 21, 2017 at 07:45:39AM +0100, Ingo Molnar wrote: > > * Andrei Vagin wrote: > > > > > # first bad commit: [45fc8757d1d2128e342b4e7ef39adedf7752faac] x86: > > > Make the GDT remapping read-only on 64-bit > > > > Just wondering, does the follo

Re: linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel

2017-03-21 Thread Adam Borowski
On Tue, Mar 21, 2017 at 07:45:39AM +0100, Ingo Molnar wrote: > * Andrei Vagin 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: Forcibl

Re: linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel

2017-03-20 Thread Ingo Molnar
* Andrei Vagin wrote: > Here is my bisect log: > [avagin@laptop linux-next]$ git bisect log > # bad: [f921b263d9602fb7873710c2df70671f2ffcf658] Add linux-next > specific files for 20170320 > # good: [4495c08e84729385774601b5146d51d9e5849f81] Linux 4.11-rc2 > git bisect start 'HEAD' 'v4.11-rc2' >

Re: linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel

2017-03-20 Thread Andrei Vagin
Here is my bisect log: [avagin@laptop linux-next]$ git bisect log # bad: [f921b263d9602fb7873710c2df70671f2ffcf658] Add linux-next specific files for 20170320 # good: [4495c08e84729385774601b5146d51d9e5849f81] Linux 4.11-rc2 git bisect start 'HEAD' 'v4.11-rc2' # good: [adeec71e7b8a11ff44103cfa4e1c6

Re: linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel

2017-03-20 Thread Adam Borowski
On Mon, Mar 20, 2017 at 04:57:39PM -0700, Andrei Vagin wrote: > We run CRIU tests on linux-next. And today we found that when we start > x32 processes, a kernel bug is triggered: > > [root@fc24 ~]# uname -a > Linux fc24 4.11.0-rc2-next-20170320 #159 SMP Mon Mar 20 16:53:58 PDT > 2017 x86_64 x86_64

linux-next: x86: Unalbe to run x32 processes on the x86_64 kernel

2017-03-20 Thread Andrei Vagin
Hello, We run CRIU tests on linux-next. And today we found that when we start x32 processes, a kernel bug is triggered: [root@fc24 ~]# uname -a Linux fc24 4.11.0-rc2-next-20170320 #159 SMP Mon Mar 20 16:53:58 PDT 2017 x86_64 x86_64 x86_64 GNU/Linux [root@fc24 ~]# cat t.c int main() { return 0; }