From: Ingo Molnar <mingo@kernel.org>
To: Dmitry Safonov <dsafonov@virtuozzo.com>,
Andy Lutomirski <luto@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, 0x7f454c46@gmail.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: [PATCHv4 0/6] x86: 32-bit compatible C/R on x86_64
Date: Thu, 1 Sep 2016 08:18:46 +0200 [thread overview]
Message-ID: <20160901061846.GA22552@gmail.com> (raw)
In-Reply-To: <20160831135936.2281-1-dsafonov@virtuozzo.com>
* Dmitry Safonov <dsafonov@virtuozzo.com> wrote:
> Changes from v3:
> - proper ifdefs around vdso_image_32
> - missed Reviewed-by tag
> arch/x86/entry/vdso/vma.c | 81 +++++++++++++++++++++++++++------------
> arch/x86/ia32/ia32_signal.c | 2 +-
> arch/x86/include/asm/compat.h | 8 ++--
> arch/x86/include/asm/fpu/signal.h | 6 +++
> arch/x86/include/asm/signal.h | 4 ++
> arch/x86/include/asm/vdso.h | 2 +
> arch/x86/include/uapi/asm/prctl.h | 6 +++
> arch/x86/kernel/process_64.c | 25 ++++++++++++
> arch/x86/kernel/ptrace.c | 2 +-
> arch/x86/kernel/signal.c | 20 +++++-----
> arch/x86/kernel/signal_compat.c | 34 ++++++++++++++--
> fs/binfmt_elf.c | 23 ++++-------
> kernel/signal.c | 7 ++++
> 13 files changed, 162 insertions(+), 58 deletions(-)
Ok, this series looks good to me - does anyone have any objections?
Thanks,
Ingo
--
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:[~2016-09-01 6:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 13:59 [PATCHv4 0/6] x86: 32-bit compatible C/R on x86_64 Dmitry Safonov
2016-08-31 13:59 ` [PATCHv4 1/6] x86/vdso: unmap vdso blob on vvar mapping failure Dmitry Safonov
2016-08-31 13:59 ` [PATCHv4 2/6] x86/vdso: replace calculate_addr in map_vdso() with addr Dmitry Safonov
2016-08-31 20:00 ` Andy Lutomirski
2016-08-31 13:59 ` [PATCHv4 3/6] x86/arch_prctl/vdso: add ARCH_MAP_VDSO_* Dmitry Safonov
2016-08-31 14:04 ` Dmitry Safonov
2016-08-31 14:56 ` Andy Lutomirski
2016-08-31 15:01 ` Dmitry Safonov
2016-08-31 15:08 ` Andy Lutomirski
2016-08-31 13:59 ` [PATCHv4 4/6] x86/coredump: use pr_reg size, rather that TIF_IA32 flag Dmitry Safonov
2016-08-31 13:59 ` [PATCHv4 5/6] x86/ptrace: down with test_thread_flag(TIF_IA32) Dmitry Safonov
2016-08-31 13:59 ` [PATCHv4 6/6] x86/signal: add SA_{X32,IA32}_ABI sa_flags Dmitry Safonov
2016-08-31 14:07 ` Dmitry Safonov
2016-09-01 12:27 ` Oleg Nesterov
2016-09-01 12:45 ` Cyrill Gorcunov
2016-09-01 13:47 ` Dmitry Safonov
2016-09-01 13:59 ` Cyrill Gorcunov
2016-09-01 16:56 ` Oleg Nesterov
2016-09-01 6:18 ` Ingo Molnar [this message]
2016-09-01 8:19 ` [PATCHv4 0/6] x86: 32-bit compatible C/R on x86_64 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=20160901061846.GA22552@gmail.com \
--to=mingo@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dsafonov@virtuozzo.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=viro@zeniv.linux.org.uk \
--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).