From: Andrew Morgan <morgan@kernel.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
Linux Security Modules List
<linux-security-module@vger.kernel.org>
Subject: Re: [PATCH 3/4] security: filesystem capabilities refactor kernel code
Date: Fri, 27 Jun 2008 17:29:39 -0700 [thread overview]
Message-ID: <486585F3.7080906@kernel.org> (raw)
In-Reply-To: <20080627210616.GC17415@us.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Serge E. Hallyn wrote:
| Quoting Andrew G. Morgan (morgan@kernel.org):
| More optimal kernel locking for filesystem capability support.
~From 73bb5a039e95b9d150c74feaf5824a1f761fb718 Mon Sep 17 00:00:00 2001
From: Andrew G. Morgan <morgan@kernel.org>
Date: Wed, 25 Jun 2008 23:30:44 -0700
Subject: [PATCH] Refactor filesystem capability support in main kernel.
| No changelog, so I assume this is essentially the same patch as I
| acked+tested on Jun 23.
| Acked-by: Serge Hallyn <serue@us.ibm.com>
Yes. I just broke the original patch into 1/4 and 3/4. (2/4 and 4/4 are new)
| -serge
Thanks
Andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIZYXx+bHCR3gb8jsRAjh7AKCc8hj+0e8v2ubb9wji94l0YKDamgCZAcsE
9WVJ1GGLWMOqQl4jl5LPexs=
=k/dq
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-06-28 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 8:49 [PATCH 3/4] security: filesystem capabilities refactor kernel code Andrew G. Morgan
2008-06-27 21:06 ` Serge E. Hallyn
2008-06-28 0:29 ` Andrew Morgan [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=486585F3.7080906@kernel.org \
--to=morgan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serue@us.ibm.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