From: hpa@zytor.com
To: Andy Lutomirski <luto@amacapital.net>,
Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Dmitry Safonov <dsafonov@virtuozzo.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Adam Borowski <kilobyte@angband.pl>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrei Vagin <avagin@gmail.com>, Borislav Petkov <bp@suse.de>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
X86 ML <x86@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY()
Date: Tue, 21 Mar 2017 11:49:37 -0700 [thread overview]
Message-ID: <13EAF4BE-144F-47D6-8A38-3B6D97ACFF8A@zytor.com> (raw)
In-Reply-To: <CALCETrXoxRBTon8+jrYcbruYVUZASwgd-kzH-A96DGvT7gLXVA@mail.gmail.com>
On March 21, 2017 10:45:57 AM PDT, Andy Lutomirski <luto@amacapital.net> wrote:
>On Tue, Mar 21, 2017 at 10:17 AM, Cyrill Gorcunov <gorcunov@gmail.com>
>wrote:
>> On Tue, Mar 21, 2017 at 07:37:12PM +0300, Dmitry Safonov wrote:
>> ...
>>> diff --git a/arch/x86/kernel/process_64.c
>b/arch/x86/kernel/process_64.c
>>> index d6b784a5520d..d3d4d9abcaf8 100644
>>> --- a/arch/x86/kernel/process_64.c
>>> +++ b/arch/x86/kernel/process_64.c
>>> @@ -519,8 +519,14 @@ void set_personality_ia32(bool x32)
>>> if (current->mm)
>>> current->mm->context.ia32_compat = TIF_X32;
>>> current->personality &= ~READ_IMPLIES_EXEC;
>>> - /* in_compat_syscall() uses the presence of the x32
>>> - syscall bit flag to determine compat status */
>>> + /*
>>> + * in_compat_syscall() uses the presence of the x32
>>> + * syscall bit flag to determine compat status.
>>> + * On the bitness of syscall relies x86 mmap() code,
>>> + * so set x32 syscall bit right here to make
>>> + * in_compat_syscall() work during exec().
>>> + */
>>> + task_pt_regs(current)->orig_ax |= __X32_SYSCALL_BIT;
>>> current->thread.status &= ~TS_COMPAT;
>>
>> Hi! I must admit I didn't follow close the overall series (so can't
>> comment much here :) but I have a slightly unrelated question -- is
>> there a way to figure out if task is running in x32 mode say with
>> some ptrace or procfs sign?
>
>You should be able to figure out of a *syscall* is x32 by simply
>looking at bit 30 in the syscall number. (This is unlike i386, which
>is currently not reflected in ptrace.)
>
>Do we actually have an x32 per-task mode at all? If so, maybe we can
>just remove it on top of Dmitry's series.
We do, for things like signal delivery mostly. We have tried relying on it as little as possible, intentionally.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-03-21 18:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:37 Dmitry Safonov
2017-03-21 17:17 ` Cyrill Gorcunov
2017-03-21 17:45 ` Andy Lutomirski
2017-03-21 18:05 ` [Q] Figuring out task mode Cyrill Gorcunov
2017-03-21 23:54 ` Andy Lutomirski
2017-03-21 18:09 ` [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() Dmitry Safonov
2017-03-21 18:40 ` Cyrill Gorcunov
2017-03-21 18:51 ` hpa
2017-03-21 19:07 ` Cyrill Gorcunov
2017-03-21 19:20 ` hpa
2017-03-21 19:19 ` Dmitry Safonov
2017-03-21 19:24 ` Cyrill Gorcunov
2017-03-21 19:34 ` Dmitry Safonov
2017-03-21 19:31 ` Andy Lutomirski
2017-03-21 19:34 ` Cyrill Gorcunov
2017-03-21 19:42 ` Dmitry Safonov
2017-03-21 20:04 ` Dmitry Safonov
2017-03-21 18:49 ` hpa [this message]
2017-03-21 17:27 ` hpa
2017-03-21 17:27 ` Dmitry Safonov
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=13EAF4BE-144F-47D6-8A38-3B6D97ACFF8A@zytor.com \
--to=hpa@zytor.com \
--cc=0x7f454c46@gmail.com \
--cc=avagin@gmail.com \
--cc=bp@suse.de \
--cc=dsafonov@virtuozzo.com \
--cc=gorcunov@gmail.com \
--cc=kilobyte@angband.pl \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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