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

[Ingo Molnar]

* Andrei Vagin <avagin@xxxxxxxxx> 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'
> # good: [adeec71e7b8a11ff44103cfa4e1c6002c27ae9ac] Merge
> remote-tracking branch 'drm/drm-next'
> git bisect good adeec71e7b8a11ff44103cfa4e1c6002c27ae9ac
> # bad: [e5b1cee1bb9d8a66b28d64db9d8250ae2b0803d2] Merge
> remote-tracking branch 'tty/tty-next'
> git bisect bad e5b1cee1bb9d8a66b28d64db9d8250ae2b0803d2
> # good: [81cde6aecf21113c6bc65bc944587db4cbd3f64d] Merge
> remote-tracking branch 'mmc/next'
> git bisect good 81cde6aecf21113c6bc65bc944587db4cbd3f64d
> # bad: [69d76288005784205678520826a74c28e49a1703] Merge
> remote-tracking branch 'tip/auto-latest'
> git bisect bad 69d76288005784205678520826a74c28e49a1703
> # good: [6d32edf2be6c4e0f08b102e2d3227278ebb477c9] Merge
> remote-tracking branch 'spi/for-next'
> git bisect good 6d32edf2be6c4e0f08b102e2d3227278ebb477c9
> # good: [61f63e383784bd0ab6529cfc95ddc59c713afcc9] Merge tag
> 'perf-core-for-mingo-4.12-20170316' of
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into
> perf/core
> git bisect good 61f63e383784bd0ab6529cfc95ddc59c713afcc9
> # good: [3069c5a046ec92dc552194686c95e27c8c9e919d] Merge branch 'x86/asm'
> git bisect good 3069c5a046ec92dc552194686c95e27c8c9e919d
> # bad: [5b804ec2fd3272385ba7530c3a67d7402fb6d8a0] Merge branch 'x86/mm'
> git bisect bad 5b804ec2fd3272385ba7530c3a67d7402fb6d8a0
> # good: [06c830a48346643e195801460dfe16d96ba4dff5] x86/power: Add
> 5-level paging support
> git bisect good 06c830a48346643e195801460dfe16d96ba4dff5
> # good: [2bbbd194fdca01f694e2ca3fb447a1acf9d19f76] Merge branch 'x86/cpu'
> git bisect good 2bbbd194fdca01f694e2ca3fb447a1acf9d19f76
> # good: [69218e47994da614e7af600bf06887750ab6657a] x86: Remap GDT
> tables in the fixmap section
> git bisect good 69218e47994da614e7af600bf06887750ab6657a
> # bad: [74c8ce958dbf0b64f198becb5d8aa93afb967438] Merge branch 'linus'
> into x86/mm, to pick up a bugfix
> git bisect bad 74c8ce958dbf0b64f198becb5d8aa93afb967438
> # bad: [45fc8757d1d2128e342b4e7ef39adedf7752faac] x86: Make the GDT
> remapping read-only on 64-bit
> git bisect bad 45fc8757d1d2128e342b4e7ef39adedf7752faac
> # 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

?

Also attached below.

Thanks,

	Ingo

=================>