From: KaiGai Kohei <kaigai@kaigai.gr.jp>
To: Andrew Morgan <morgan@kernel.org>
Cc: KaiGai Kohei <kaigai@ak.jp.nec.com>,
"Serge E. Hallyn" <serue@us.ibm.com>,
jmorris@namei.org, akpm@osdl.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Exporting capability code/name pairs
Date: Wed, 02 Jan 2008 17:08:42 +0900 [thread overview]
Message-ID: <477B468A.3050702@kaigai.gr.jp> (raw)
In-Reply-To: <4777C745.8080700@kernel.org>
Andrew Morgan wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> KaiGai Kohei wrote:
>> Remaining issues:
>> - We have to mount securityfs explicitly, or use /etc/fstab.
>> It can cause a matter when we want to use this feature on
>> very early phase on boot. (like /sbin/init)
>
> I'm not altogether clear how you intend this to work.
>
> Are you saying that some future version of libcap will require that
> securityfs be mounted before it (libcap) will work?
Yes, but implementing this feature on securityfs might be not good
idea as as James said. If this feature is on procfs or sysfs, it is
not necessary to mount securityfs explicitly.
Thanks,
--
KaiGai Kohei <kaigai@kaigai.gr.jp>
next prev parent reply other threads:[~2008-01-02 8:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 3:53 [PATCH] Exporting capability code/name pairs KaiGai Kohei
2007-12-27 7:54 ` James Morris
2007-12-27 16:14 ` Serge E. Hallyn
2007-12-28 1:47 ` KaiGai Kohei
2007-12-28 6:16 ` KaiGai Kohei
2007-12-28 6:54 ` James Morris
2007-12-28 7:33 ` KaiGai Kohei
2007-12-28 9:12 ` James Morris
2008-01-02 8:04 ` KaiGai Kohei
2008-01-02 10:02 ` James Morris
2008-01-04 2:28 ` KaiGai Kohei
2007-12-28 23:07 ` Randy Dunlap
2007-12-30 16:28 ` Andrew Morgan
2008-01-02 8:08 ` KaiGai Kohei [this message]
2008-01-03 1:48 ` Andrew Morgan
2008-01-04 1:57 ` KaiGai Kohei
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=477B468A.3050702@kaigai.gr.jp \
--to=kaigai@kaigai.gr.jp \
--cc=akpm@osdl.org \
--cc=jmorris@namei.org \
--cc=kaigai@ak.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@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