From: Dmitry Safonov <dsafonov@virtuozzo.com>
To: linux-kernel@vger.kernel.org
Cc: 0x7f454c46@gmail.com, luto@kernel.org, oleg@redhat.com,
tglx@linutronix.de, hpa@zytor.com, mingo@redhat.com,
linux-mm@kvack.org, x86@kernel.org, gorcunov@openvz.org,
xemul@virtuozzo.com
Subject: Re: [PATCHv3 6/6] x86/signal: add SA_{X32,IA32}_ABI sa_flags
Date: Fri, 26 Aug 2016 20:16:33 +0300 [thread overview]
Message-ID: <8ae805a7-69c0-811f-0b16-8f1130ecbc10@virtuozzo.com> (raw)
In-Reply-To: <20160826171317.3944-7-dsafonov@virtuozzo.com>
On 08/26/2016 08:13 PM, Dmitry Safonov wrote:
> Introduce new flags that defines which ABI to use on creating sigframe.
> Those flags kernel will set according to sigaction syscall ABI,
> which set handler for the signal being delivered.
>
> So that will drop the dependency on TIF_IA32/TIF_X32 flags on signal deliver.
> Those flags will be used only under CONFIG_COMPAT.
>
> Similar way ARM uses sa_flags to differ in which mode deliver signal
> for 26-bit applications (look at SA_THIRYTWO).
>
> Cc: Andy Lutomirski <luto@kernel.org>
> Cc: Oleg Nesterov <oleg@redhat.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: linux-mm@kvack.org
> Cc: x86@kernel.org
> Cc: Cyrill Gorcunov <gorcunov@openvz.org>
> Cc: Pavel Emelyanov <xemul@virtuozzo.com>
> Signed-off-by: Dmitry Safonov <dsafonov@virtuozzo.com>
Oh, accidentally missed this on patches preparation, excuses:
Reviewed-by: Andy Lutomirski <luto@kernel.org>
--
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>
prev parent reply other threads:[~2016-08-26 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 17:13 [PATCHv3 0/6] x86: 32-bit compatible C/R on x86_64 Dmitry Safonov
2016-08-26 17:13 ` [PATCHv3 1/6] x86/vdso: unmap vdso blob on vvar mapping failure Dmitry Safonov
2016-08-26 17:13 ` [PATCHv3 2/6] x86/vdso: replace calculate_addr in map_vdso() with addr Dmitry Safonov
2016-08-31 15:09 ` Andy Lutomirski
2016-08-26 17:13 ` [PATCHv3 3/6] x86/arch_prctl/vdso: add ARCH_MAP_VDSO_* Dmitry Safonov
2016-08-27 18:09 ` kbuild test robot
2016-08-29 11:12 ` Dmitry Safonov
2016-08-31 15:00 ` Andy Lutomirski
2016-08-31 15:09 ` Dmitry Safonov
2016-08-31 15:30 ` Dmitry Safonov
2016-08-31 15:42 ` Andy Lutomirski
2016-08-31 15:46 ` Dmitry Safonov
2016-08-26 17:13 ` [PATCHv3 4/6] x86/coredump: use pr_reg size, rather that TIF_IA32 flag Dmitry Safonov
2016-08-26 17:13 ` [PATCHv3 5/6] x86/ptrace: down with test_thread_flag(TIF_IA32) Dmitry Safonov
2016-08-26 17:13 ` [PATCHv3 6/6] x86/signal: add SA_{X32,IA32}_ABI sa_flags Dmitry Safonov
2016-08-26 17:16 ` Dmitry Safonov [this message]
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=8ae805a7-69c0-811f-0b16-8f1130ecbc10@virtuozzo.com \
--to=dsafonov@virtuozzo.com \
--cc=0x7f454c46@gmail.com \
--cc=gorcunov@openvz.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xemul@virtuozzo.com \
/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;
as well as URLs for NNTP newsgroup(s).