All of lore.kernel.org
 help / color / mirror / Atom feed
From: Serge Hallyn <serge.hallyn@canonical.com>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"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>
Subject: Re: [PATCH 0/5] IPC: checkpoint/restore in userspace enhancements
Date: Mon, 13 Feb 2012 10:11:35 -0600	[thread overview]
Message-ID: <20120213161135.GE5009@sergelap> (raw)
In-Reply-To: <4F38EE17.7090809@parallels.com>

Quoting Stanislav Kinsbursky (skinsbursky@parallels.com):
> 10.02.2012 22:29, Casey Schaufler пишет:
> >On 2/9/2012 10:01 AM, Stanislav Kinsbursky wrote:
> >>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.
> >
> >Is there any chance you might include the LSM data as well?
> >
> 
> Sorry, but I don't understand your question.
> What is this "LSM"? Linux Shared Memory? If yes, and you mean SYSV
> IPC SHM, then where do you want to include it?

He means linux security modules.  (see include/linux/security.h)

  reply	other threads:[~2012-02-13 16:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 18:01 [PATCH 0/5] IPC: checkpoint/restore in userspace enhancements 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 [this message]
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

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=20120213161135.GE5009@sergelap \
    --to=serge.hallyn@canonical.com \
    --cc=akpm@linux-foundation.org \
    --cc=casey@schaufler-ca.com \
    --cc=criu@openvz.org \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=skinsbursky@parallels.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.