From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Oren Laadan <orenl@cs.columbia.edu>
Cc: Linux Containers <containers@lists.osdl.org>,
linux-security-module@vger.kernel.org,
SELinux <selinux@tycho.nsa.gov>
Subject: [PATCH 0/4] LSM checkpoint/restart: introduction
Date: Thu, 10 Sep 2009 15:22:19 -0500 [thread overview]
Message-ID: <20090910202219.GA6778@us.ibm.com> (raw)
Following is a respin of the LSM checkpoint/restart patchset,
hopefully addressing most of the feedback I've gotten.
The patchset includes one (1/4) patch which is not directly
LSM-related, one (2/4) which implements the generic LSM c/r
support, one (3/4) implementing support for Smack, one
(4/4) implementing support for SELinux, and one (1/1)
updating the userspace program which initiates restart.
At this point I'm hoping to get some acks and get them pushed
to the c/r kernel tree, which is branch ckpt-v17-dev in
git://git.ncl.cs.columbia.edu/pub/git/linux-cr.git/. Comments
are of course appreciated. Once they sit in the tree for a bit,
I'll tackle the socket related LSM c/r.
thanks,
-serge
WARNING: multiple messages have this Message-ID (diff)
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Oren Laadan <orenl@cs.columbia.edu>
Cc: Linux Containers <containers@lists.osdl.org>,
linux-security-module@vger.kernel.org,
SELinux <selinux@tycho.nsa.gov>
Subject: [PATCH 0/4] LSM checkpoint/restart: introduction
Date: Thu, 10 Sep 2009 15:22:19 -0500 [thread overview]
Message-ID: <20090910202219.GA6778@us.ibm.com> (raw)
Following is a respin of the LSM checkpoint/restart patchset,
hopefully addressing most of the feedback I've gotten.
The patchset includes one (1/4) patch which is not directly
LSM-related, one (2/4) which implements the generic LSM c/r
support, one (3/4) implementing support for Smack, one
(4/4) implementing support for SELinux, and one (1/1)
updating the userspace program which initiates restart.
At this point I'm hoping to get some acks and get them pushed
to the c/r kernel tree, which is branch ckpt-v17-dev in
git://git.ncl.cs.columbia.edu/pub/git/linux-cr.git/. Comments
are of course appreciated. Once they sit in the tree for a bit,
I'll tackle the socket related LSM c/r.
thanks,
-serge
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2009-09-10 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 20:22 Serge E. Hallyn [this message]
2009-09-10 20:22 ` [PATCH 0/4] LSM checkpoint/restart: introduction Serge E. Hallyn
2009-09-10 20:22 ` [PATCH 1/4] cr: define ckpt_debug if CONFIG_CHECKPOINT=n Serge E. Hallyn
2009-09-10 20:22 ` Serge E. Hallyn
2009-09-10 20:23 ` [PATCH 2/4] cr: add generic LSM c/r support Serge E. Hallyn
2009-09-10 20:23 ` Serge E. Hallyn
2009-09-10 20:23 ` [PATCH 3/4] cr: add smack support to lsm c/r Serge E. Hallyn
2009-09-10 20:23 ` Serge E. Hallyn
2009-09-10 20:23 ` [PATCH 4/4] cr: add selinux support Serge E. Hallyn
2009-09-10 20:23 ` Serge E. Hallyn
2009-09-10 20:23 ` [PATCH 1/1] mktree: accept the lsm_name field in header and add -k flag Serge E. Hallyn
2009-09-10 20:23 ` Serge E. Hallyn
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=20090910202219.GA6778@us.ibm.com \
--to=serue@us.ibm.com \
--cc=containers@lists.osdl.org \
--cc=linux-security-module@vger.kernel.org \
--cc=orenl@cs.columbia.edu \
--cc=selinux@tycho.nsa.gov \
/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.