From: Kentaro Takeda <takedakn@nttdata.co.jp>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Toshiharu Harada <haradats@nttdata.co.jp>
Subject: Re: [PATCH] Introduce new LSM hooks where vfsmount is available.
Date: Wed, 17 Sep 2008 17:35:35 +0900 [thread overview]
Message-ID: <48D0C157.7050406@nttdata.co.jp> (raw)
In-Reply-To: <48D080D1.5060405@schaufler-ca.com>
Casey Schaufler wrote:
> As always, the community will be eager to see the code that makes
> use of these hooks.
We are ready for submitting body of TOMOYO Linux as always. :-)
However, the largest stumbling block of merging TOMOYO Linux is the
method for calculating pathname in LSM module. This patch contains
all modifications to the existing kernel code by TOMOYO Linux (the
rest modification is within security/tomoyo).
We'd like to ask the community's approval of this approach before
review of TOMOYO Linux main module.
Regards,
next prev parent reply other threads:[~2008-09-17 8:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48C65E9D.3070106@nttdata.co.jp>
[not found] ` <5fb14edc0809090902m32431bf6yf518a457e410764d@mail.gmail.com>
[not found] ` <20080910134540.45ec1272.akpm@linux-foundation.org>
[not found] ` <48C877DE.4040402@nttdata.co.jp>
2008-09-17 2:16 ` [PATCH] Introduce new LSM hooks where vfsmount is available Kentaro Takeda
2008-09-17 4:00 ` Casey Schaufler
2008-09-17 8:35 ` Kentaro Takeda [this message]
2008-09-17 17:46 ` david
2008-09-23 6:06 ` James Morris
2008-09-23 6:12 ` david
2008-09-23 15:02 ` Stephen Smalley
2008-09-23 15:20 ` Alexey Dobriyan
2008-09-23 21:20 ` James Morris
2008-09-24 8:00 ` Kentaro Takeda
2008-09-24 13:28 ` Serge E. Hallyn
2008-09-24 21:18 ` James Morris
2008-12-17 4:24 [PATCH] introduce " Kentaro Takeda
2008-12-17 4:42 ` Al Viro
2008-12-17 4:50 ` Al Viro
2008-12-17 5:06 ` Kentaro Takeda
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=48D0C157.7050406@nttdata.co.jp \
--to=takedakn@nttdata.co.jp \
--cc=casey@schaufler-ca.com \
--cc=haradats@nttdata.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).