[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170125230042.GR17692@port70.net>
Date: Thu, 26 Jan 2017 00:00:46 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Cc: Andrei Vagin <avagin@...il.com>
Subject: Re: Re: Need to zero pads in msghdr
* Andrei Vagin <avagin@...il.com> [2017-01-25 11:46:44 -0800]:
> On Wed, Jan 25, 2017 at 11:40 AM, Szabolcs Nagy <nsz@...t70.net> wrote:
> > why do you need a raw syscall?
>
> We inject our code into processes which are going to be dumped:
> https://criu.org/Parasite_code
>
> And on restore we have to unmap old libc to restore process mappings.
if you static link to musl for the parasite then
i don't see why the syscalls have to be raw..
what you may worry about is process global
state that the libc takes control of
(libc internal signal handler, brk pointer,
doing things to fd 0/1/2, etc), but that you
cannot prevent with raw syscalls.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
