From: Dmitry Safonov <0x7f454c46@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Dmitry Safonov <dsafonov@virtuozzo.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, X86 ML <x86@kernel.org>
Subject: Re: [RFC 1/3] x86/signal: add SA_{X32,IA32}_ABI sa_flags
Date: Mon, 25 Apr 2016 23:34:01 +0300 [thread overview]
Message-ID: <CAJwJo6b_VfE8nUueztZVWiHg4c9rBTu-BesYkRun0OUOO1j6Dg@mail.gmail.com> (raw)
In-Reply-To: <CALCETrUpEcCq-3RzV=5F7AUr0PD88yw+ezkLVndqwK4A=msqwg@mail.gmail.com>
2016-04-25 22:20 GMT+03:00 Andy Lutomirski <luto@amacapital.net>:
> On Mon, Apr 25, 2016 at 9:12 AM, Dmitry Safonov <dsafonov@virtuozzo.com> wrote:
>> Introduce new flags that defines which ABI to use on creating sigframe.
>> Those flags one may set from the userspace, or kernel will set them
>> according to syscall, which sets handler for a signal.
>> So that will drop the dependency on TIF_IA32/TIF_X32 flags on syscall deliver.
>> Those flags will be used only under CONFIG_COMPAT.
>>
>> The same way ARM uses sa_flags to differ in which mode deliver signal
>> for 26-bit applications (look at SA_THIRYTWO).
>
> Hmm. Do we want to make these user-visible at all, or should it be
> purely an in-kernel thing?
Yes, I'll rework it to not expose to userspace.
I thought about it as a bonus when did it, but yeah, it's better
not reveal a new interfaces until they really needed.
But anyway, I did it for RFC, and I don't know what's better
for hidden flag: reuse sa_flags or invent in ksig a new hidden
member only for the kernel?
next prev parent reply other threads:[~2016-04-25 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 16:12 [RFC 1/3] x86/signal: add SA_{X32,IA32}_ABI sa_flags Dmitry Safonov
2016-04-25 16:12 ` [RFC 2/3] x86/coredump: use core regs, rather that TIF_IA32 flag Dmitry Safonov
2016-04-25 16:51 ` Andy Lutomirski
2016-04-25 16:12 ` [RFC 3/3] x86/ptrace: down with test_thread_flag(TIF_IA32) Dmitry Safonov
2016-04-25 16:53 ` Andy Lutomirski
2016-04-25 17:14 ` Dmitry Safonov
2016-04-25 18:09 ` Dmitry Safonov
2016-04-25 18:13 ` Dmitry Safonov
2016-04-25 19:33 ` Andy Lutomirski
2016-04-25 20:37 ` Dmitry Safonov
2016-04-25 19:20 ` [RFC 1/3] x86/signal: add SA_{X32,IA32}_ABI sa_flags Andy Lutomirski
2016-04-25 20:34 ` Dmitry Safonov [this message]
2016-04-25 20:38 ` Andy Lutomirski
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=CAJwJo6b_VfE8nUueztZVWiHg4c9rBTu-BesYkRun0OUOO1j6Dg@mail.gmail.com \
--to=0x7f454c46@gmail.com \
--cc=dsafonov@virtuozzo.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.