From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Dmitry Safonov <dsafonov@virtuozzo.com>
Cc: Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, 0x7f454c46@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv2] ARM32: Support mremap() for sigpage/vDSO
Date: Tue, 23 May 2017 21:09:46 +0100 [thread overview]
Message-ID: <20170523200946.GG22219@n2100.armlinux.org.uk> (raw)
In-Reply-To: <bebbe3ce-12ed-419a-248a-55f41d74d9da@virtuozzo.com>
On Thu, May 18, 2017 at 02:13:29PM +0300, Dmitry Safonov wrote:
> On 04/25/2017 08:18 PM, Dmitry Safonov wrote:
> >On 04/14/2017 04:25 PM, Dmitry Safonov wrote:
> >>CRIU restores application mappings on the same place where they
> >>were before Checkpoint. That means, that we need to move vDSO
> >>and sigpage during restore on exactly the same place where
> >>they were before C/R.
> >>
> >>Make mremap() code update mm->context.{sigpage,vdso} pointers
> >>during VMA move. Sigpage is used for landing after handling
> >>a signal - if the pointer is not updated during moving, the
> >>application might crash on any signal after mremap().
> >>
> >>vDSO pointer on ARM32 is used only for setting auxv at this moment,
> >>update it during mremap() in case of future usage.
> >>
> >>Without those updates, current work of CRIU on ARM32 is not reliable.
> >>Historically, we error Checkpointing if we find vDSO page on ARM32
> >>and suggest user to disable CONFIG_VDSO.
> >>But that's not correct - it goes from x86 where signal processing
> >>is ended in vDSO blob. For arm32 it's sigpage, which is not disabled
> >>with `CONFIG_VDSO=n'.
> >>
> >>Looks like C/R was working by luck - because userspace on ARM32 at
> >>this moment always sets SA_RESTORER.
> >>
> >>Cc: linux-arm-kernel@lists.infradead.org
> >>Cc: Russell King <linux@armlinux.org.uk>
> >>Cc: Will Deacon <will.deacon@arm.com>
> >>Cc: Andy Lutomirski <luto@amacapital.net>
> >>Cc: Thomas Gleixner <tglx@linutronix.de>
> >>Cc: Cyrill Gorcunov <gorcunov@openvz.org>
> >>Cc: Pavel Emelyanov <xemul@virtuozzo.com>
> >>Cc: Christopher Covington <cov@codeaurora.org>
> >>Signed-off-by: Dmitry Safonov <dsafonov@virtuozzo.com>
> >>---
> >>v2: (buildbot) Fix (unsinged long) to (void*) cast warning.
> >>
> >> arch/arm/kernel/process.c | 8 ++++++++
> >> arch/arm/kernel/vdso.c | 18 ++++++++++++++++++
> >> arch/x86/entry/vdso/vma.c | 3 ---
> >> mm/mmap.c | 4 ++++
> >> 4 files changed, 30 insertions(+), 3 deletions(-)
> >
> >Ping?
>
> Ping?
I'm mostly happy with the ARM bits, but I can't take the patch without
acks from others because it touches other architectures/generic code.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-05-23 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 13:25 Dmitry Safonov
2017-04-25 17:18 ` Dmitry Safonov
2017-05-18 11:13 ` Dmitry Safonov
2017-05-23 20:09 ` Russell King - ARM Linux [this message]
2017-05-24 10:09 ` Dmitry Safonov
2017-05-24 16:44 ` Andy Lutomirski
2017-06-19 14:50 ` Dmitry Safonov
2017-06-19 16:10 ` Russell King - ARM Linux
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=20170523200946.GG22219@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=0x7f454c46@gmail.com \
--cc=dsafonov@virtuozzo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®