linux-kernel - Re: [PATCHv3] x86/mm: set x32 syscall bit in SET

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <26CDE83A-CDBE-4F23-91F6-05B07B461BDD@zytor.com>
Date:   Tue, 21 Mar 2017 15:25:04 -0700
From:   hpa@...or.com
To:     Thomas Gleixner <tglx@...utronix.de>,
        Dmitry Safonov <dsafonov@...tuozzo.com>
CC:     linux-kernel@...r.kernel.org, 0x7f454c46@...il.com,
        Adam Borowski <kilobyte@...band.pl>, linux-mm@...ck.org,
        Andrei Vagin <avagin@...il.com>,
        Cyrill Gorcunov <gorcunov@...nvz.org>,
        Borislav Petkov <bp@...e.de>,
        "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        x86@...nel.org, Andy Lutomirski <luto@...nel.org>,
        Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCHv3] x86/mm: set x32 syscall bit in SET_PERSONALITY()

On March 21, 2017 3:21:13 PM PDT, Thomas Gleixner <tglx@...utronix.de> 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.
>
>Thanks,
>
>	tglx

Since the i386 syscall namespace is totally separate (and different), should we simply change the system call number to the appropriate sys_execve number?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.