From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrey Vagin <avagin@openvz.org>,
LKML <linux-kernel@vger.kernel.org>,
Pavel Emelyanov <xemul@virtuozzo.com>,
Dmitry Safonov <dsafonov@virtuozzo.com>,
Andrew Morton <akpm@linuxfoundation.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [criu] 1M guard page ruined restore
Date: Wed, 21 Jun 2017 18:48:50 +0300 [thread overview]
Message-ID: <20170621154850.GE31050@uranus> (raw)
In-Reply-To: <20170621152256.GC31050@uranus>
On Wed, Jun 21, 2017 at 06:22:56PM +0300, Cyrill Gorcunov wrote:
> This start failing because
>
> | static inline int check_stack_guard_page(struct vm_area_struct *vma, unsigned long address)
>
> function get dropped off. Hugh, it is done on intent and
> userspace programs have to extend stack manually?
Sorry for noise. I forget to add 1M gap for testing.
All is fine!
next prev parent reply other threads:[~2017-06-21 16:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 7:52 [criu] 1M guard page ruined restore Cyrill Gorcunov
2017-06-20 10:23 ` Hugh Dickins
2017-06-20 10:41 ` Cyrill Gorcunov
2017-06-21 15:22 ` Cyrill Gorcunov
2017-06-21 15:48 ` Cyrill Gorcunov [this message]
2017-06-21 15:57 ` Oleg Nesterov
2017-06-21 16:04 ` Cyrill Gorcunov
2017-06-21 17:01 ` Oleg Nesterov
2017-06-21 17:15 ` Dmitry Safonov
2017-06-21 17:19 ` Dmitry Safonov
2017-06-21 17:31 ` Oleg Nesterov
2017-06-21 17:37 ` Dmitry Safonov
2017-06-21 17:52 ` Dmitry Safonov
2017-06-22 1:24 ` Hugh Dickins
2017-06-22 8:06 ` Cyrill Gorcunov
2017-06-21 17:15 ` Oleg Nesterov
2017-06-21 17:53 ` Cyrill Gorcunov
2017-06-21 17:16 ` Willy Tarreau
2017-06-22 14:23 ` Oleg Nesterov
2017-06-22 15:05 ` Cyrill Gorcunov
2017-06-20 10:51 ` Oleg Nesterov
2017-06-20 11:10 ` Cyrill Gorcunov
2017-06-20 11:55 ` Cyrill Gorcunov
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=20170621154850.GE31050@uranus \
--to=gorcunov@gmail.com \
--cc=akpm@linuxfoundation.org \
--cc=avagin@openvz.org \
--cc=dsafonov@virtuozzo.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--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 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.