From: Kinsbursky Stanislav <skinsbursky@openvz.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "jmorris@namei.org" <jmorris@namei.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"criu@openvz.org" <criu@openvz.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"eparis@parisplace.org" <eparis@parisplace.org>,
"sds@tycho.nsa.gov" <sds@tycho.nsa.gov>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Pavel Emelianov <xemul@parallels.com>
Subject: Re: [CRIU] [PATCH 0/5] IPC: checkpoint/restore in userspace enhancements
Date: Tue, 24 Apr 2012 13:17:30 +0400 [thread overview]
Message-ID: <4F966FAA.1030901@openvz.org> (raw)
In-Reply-To: <20120306151954.bc50817c.akpm@linux-foundation.org>
On 07.03.2012 03:19, Andrew Morton wrote:
> On Mon, 05 Mar 2012 17:04:30 +0400
> Kinsbursky Stanislav<skinsbursky@openvz.org> wrote:
>
>> 09.02.2012 22:01, Stanislav Kinsbursky __________:
>>> This patch set aimed to provide additional functionality for all IPC objects,
>>> which is required for migration these objects by user-space checkpoint/restore
>>> utils.
>>> The main problem here was impossibility to set up object id. This patch set
>>> solves the problem in two steps:
>>> 1) Makes it possible to create new object (shared memory, semaphores set or
>>> messages queue) with ID, equal to passed key.
>>> 2) Makes it possible to change existent object key.
>> Hello, Andrew.
>> Are you going to take this patch set?
>>
> (top-posting repaired - please don't do that)
>
> I haven't forgotten about it :(. There has been little review feedback
> on this patchset and I still have overall concerns about the approach
> we've been taking to c/r development. I have a lengthy Feb 15 email
> from Pavel which I also haven't forgotten about, but I haven't got back
> to thinking about the whole topic yet, sorry. Soon...
Hi, Andrew.
Just wondering about this patch set - have you commited it yet?
Or you need something from me to do this?
--
Best regards,
Stanislav Kinsbursky
prev parent reply other threads:[~2012-04-24 9:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 18:01 Stanislav Kinsbursky
2012-02-09 18:01 ` [PATCH 1/5] ipc: "use key as id" functionality for resource get system call introduced Stanislav Kinsbursky
2012-02-09 18:01 ` [PATCH 2/5] ipc: segment key change helper introduced Stanislav Kinsbursky
2012-02-09 18:01 ` [PATCH 3/5] ipc: add new SHM_SET command for sys_shmctl() call Stanislav Kinsbursky
2012-02-09 18:01 ` [PATCH 4/5] ipc: add new MSG_SET command for sys_msgctl() call Stanislav Kinsbursky
2012-02-09 18:01 ` [PATCH 5/5] ipc: add new SEM_SET command for sys_semctl() call Stanislav Kinsbursky
2012-02-10 18:29 ` [PATCH 0/5] IPC: checkpoint/restore in userspace enhancements Casey Schaufler
2012-02-13 11:03 ` Stanislav Kinsbursky
2012-02-13 16:11 ` Serge Hallyn
2012-02-13 16:48 ` Stanislav Kinsbursky
2012-02-13 17:39 ` Casey Schaufler
2012-02-14 11:33 ` Stanislav Kinsbursky
2012-03-05 13:04 ` [CRIU] " Kinsbursky Stanislav
2012-03-06 23:19 ` Andrew Morton
2012-04-24 9:17 ` Kinsbursky Stanislav [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=4F966FAA.1030901@openvz.org \
--to=skinsbursky@openvz.org \
--cc=akpm@linux-foundation.org \
--cc=criu@openvz.org \
--cc=eparis@parisplace.org \
--cc=gorcunov@openvz.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.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
Powered by JetHome