Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On 03/28/2017 03:51 PM, Thomas Gleixner wrote: On Tue, 28 Mar 2017, Dmitry Safonov wrote: On 03/22/2017 01:21 AM, Thomas Gleixner wrote: On Tue, 21 Mar 2017, Dmitry Safonov wrote: v3: - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). For correctness sake, this wants to be

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On 03/28/2017 03:51 PM, Thomas Gleixner wrote: On Tue, 28 Mar 2017, Dmitry Safonov wrote: On 03/22/2017 01:21 AM, Thomas Gleixner wrote: On Tue, 21 Mar 2017, Dmitry Safonov wrote: v3: - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). For correctness sake, this wants to be

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On Tue, 28 Mar 2017, Dmitry Safonov wrote: > On 03/22/2017 01:21 AM, Thomas Gleixner wrote: > > On Tue, 21 Mar 2017, Dmitry Safonov wrote: > > > v3: > > > - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). > > > > For correctness sake, this wants to be cleared in the IA32 path as

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On Tue, 28 Mar 2017, Dmitry Safonov wrote: > On 03/22/2017 01:21 AM, Thomas Gleixner wrote: > > On Tue, 21 Mar 2017, Dmitry Safonov wrote: > > > v3: > > > - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). > > > > For correctness sake, this wants to be cleared in the IA32 path as

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On 03/22/2017 01:21 AM, Thomas Gleixner wrote: On Tue, 21 Mar 2017, Dmitry Safonov wrote: v3: - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). For correctness sake, this wants to be cleared in the IA32 path as well. It's not causing any harm, but I'll amend the patch.

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On 03/22/2017 01:21 AM, Thomas Gleixner wrote: On Tue, 21 Mar 2017, Dmitry Safonov wrote: v3: - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). For correctness sake, this wants to be cleared in the IA32 path as well. It's not causing any harm, but I'll amend the patch.

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On 03/22/2017 01:34 AM, Thomas Gleixner wrote: On Tue, 21 Mar 2017, h...@zytor.com wrote: On March 21, 2017 3:21:13 PM PDT, Thomas Gleixner wrote: On Tue, 21 Mar 2017, Dmitry Safonov wrote: v3: - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). For

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On 03/22/2017 01:34 AM, Thomas Gleixner wrote: On Tue, 21 Mar 2017, h...@zytor.com wrote: On March 21, 2017 3:21:13 PM PDT, Thomas Gleixner wrote: On Tue, 21 Mar 2017, Dmitry Safonov wrote: v3: - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). For correctness sake, this

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On Tue, 21 Mar 2017, h...@zytor.com wrote: > On March 21, 2017 3:21:13 PM PDT, Thomas Gleixner wrote: > >On Tue, 21 Mar 2017, Dmitry Safonov wrote: > >> v3: > >> - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). > > > >For correctness sake, this wants to be

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On Tue, 21 Mar 2017, h...@zytor.com wrote: > On March 21, 2017 3:21:13 PM PDT, Thomas Gleixner wrote: > >On Tue, 21 Mar 2017, Dmitry Safonov wrote: > >> v3: > >> - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). > > > >For correctness sake, this wants to be cleared in the IA32

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On March 21, 2017 3:21:13 PM PDT, Thomas Gleixner wrote: >On Tue, 21 Mar 2017, Dmitry Safonov wrote: >> v3: >> - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). > >For correctness sake, this wants to be cleared in the IA32 path as >well. It's not causing any

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On March 21, 2017 3:21:13 PM PDT, Thomas Gleixner wrote: >On Tue, 21 Mar 2017, Dmitry Safonov wrote: >> v3: >> - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). > >For correctness sake, this wants to be cleared in the IA32 path as >well. It's not causing any harm, but >

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On Tue, 21 Mar 2017, Dmitry Safonov wrote: > v3: > - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). For correctness sake, this wants to be cleared in the IA32 path as well. It's not causing any harm, but I'll amend the patch. Thanks, tglx

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On Tue, 21 Mar 2017, Dmitry Safonov wrote: > v3: > - clear x32 syscall flag during x32 -> x86-64 exec() (thanks, HPA). For correctness sake, this wants to be cleared in the IA32 path as well. It's not causing any harm, but I'll amend the patch. Thanks, tglx

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

2017-03-22 0:16 GMT+03:00 Adam Borowski : > On Tue, Mar 21, 2017 at 08:47:11PM +0300, Dmitry Safonov wrote: >> After my changes to mmap(), its code now relies on the bitness of >> performing syscall. According to that, it chooses the base of allocation: >> mmap_base for 64-bit

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

2017-03-22 0:16 GMT+03:00 Adam Borowski : > On Tue, Mar 21, 2017 at 08:47:11PM +0300, Dmitry Safonov wrote: >> After my changes to mmap(), its code now relies on the bitness of >> performing syscall. According to that, it chooses the base of allocation: >> mmap_base for 64-bit mmap() and

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On March 21, 2017 2:16:48 PM PDT, Adam Borowski wrote: >On Tue, Mar 21, 2017 at 08:47:11PM +0300, Dmitry Safonov wrote: >> After my changes to mmap(), its code now relies on the bitness of >> performing syscall. According to that, it chooses the base of >allocation: >>

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On March 21, 2017 2:16:48 PM PDT, Adam Borowski wrote: >On Tue, Mar 21, 2017 at 08:47:11PM +0300, Dmitry Safonov wrote: >> After my changes to mmap(), its code now relies on the bitness of >> performing syscall. According to that, it chooses the base of >allocation: >> mmap_base for 64-bit mmap()

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On Tue, Mar 21, 2017 at 08:47:11PM +0300, Dmitry Safonov wrote: > After my changes to mmap(), its code now relies on the bitness of > performing syscall. According to that, it chooses the base of allocation: > mmap_base for 64-bit mmap() and mmap_compat_base for 32-bit syscall. > It was done by: >

Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On Tue, Mar 21, 2017 at 08:47:11PM +0300, Dmitry Safonov wrote: > After my changes to mmap(), its code now relies on the bitness of > performing syscall. According to that, it chooses the base of allocation: > mmap_base for 64-bit mmap() and mmap_compat_base for 32-bit syscall. > It was done by: >

[PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

After my changes to mmap(), its code now relies on the bitness of performing syscall. According to that, it chooses the base of allocation: mmap_base for 64-bit mmap() and mmap_compat_base for 32-bit syscall. It was done by: commit 1b028f784e8c ("x86/mm: Introduce mmap_compat_base() for 32-bit

[PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

After my changes to mmap(), its code now relies on the bitness of performing syscall. According to that, it chooses the base of allocation: mmap_base for 64-bit mmap() and mmap_compat_base for 32-bit syscall. It was done by: commit 1b028f784e8c ("x86/mm: Introduce mmap_compat_base() for 32-bit